automatic import of python-impyla

3 files changed, 676 insertions, 0 deletions

diff --git a/.gitignore b/.gitignore
index e69de29..edefe9d 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/impyla-0.18.0.tar.gz
diff --git a/python-impyla.spec b/python-impyla.spec
new file mode 100644
index 0000000..699112f
--- /dev/null
+++ b/python-impyla.spec
@@ -0,0 +1,674 @@
+%global _empty_manifest_terminate_build 0
+Name:		python-impyla
+Version:	0.18.0
+Release:	1
+Summary:	Python client for the Impala distributed query engine
+License:	Apache License, Version 2.0
+URL:		https://github.com/cloudera/impyla
+Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/83/ad/c228a3063c1ae3ebdf8000fd84ba43d916520aa651194465feb92d02840e/impyla-0.18.0.tar.gz
+BuildArch:	noarch
+
+Requires:	python3-six
+Requires:	python3-bitarray
+Requires:	python3-thrift
+Requires:	python3-thrift-sasl
+Requires:	python3-kerberos
+
+%description
+# impyla
+
+Python client for HiveServer2 implementations (e.g., Impala, Hive) for
+distributed query engines.
+
+For higher-level Impala functionality, including a Pandas-like interface over
+distributed data sets, see the [Ibis project][ibis].
+
+### Features
+
+* HiveServer2 compliant; works with Impala and Hive, including nested data
+
+* Fully [DB API 2.0 (PEP 249)][pep249]-compliant Python client (similar to
+sqlite or MySQL clients) supporting Python 2.6+ and Python 3.3+.
+
+* Works with Kerberos, LDAP, SSL
+
+* [SQLAlchemy][sqlalchemy] connector
+
+* Converter to [pandas][pandas] `DataFrame`, allowing easy integration into the
+Python data stack (including [scikit-learn][sklearn] and
+[matplotlib][matplotlib]); but see the [Ibis project][ibis] for a richer
+experience
+
+### Dependencies
+
+Required:
+
+* Python 2.7+ or 3.5+
+
+* `six`, `bitarray`
+
+* `thrift==0.16.0`
+
+* `thrift_sasl==0.4.3`
+
+Optional:
+
+* `kerberos>=1.3.0` for Kerberos over HTTP support. This also requires Kerberos libraries
+   to be installed on your system - see [System Kerberos](#system-kerberos)
+
+* `pandas` for conversion to `DataFrame` objects; but see the [Ibis project][ibis] instead
+
+* `sqlalchemy` for the SQLAlchemy engine
+
+* `pytest` for running tests; `unittest2` for testing on Python 2.6
+
+
+#### System Kerberos
+
+Different systems require different packages to be installed to enable Kerberos support in
+Impyla. Some examples of how to install the packages on different distributions follow.
+
+Ubuntu:
+```bash
+apt-get install libkrb5-dev krb5-user
+```
+
+RHEL/CentOS:
+```bash
+yum install krb5-libs krb5-devel krb5-server krb5-workstation
+```
+
+### Installation
+
+Install the latest release with `pip`:
+
+```bash
+pip install impyla
+```
+
+For the latest (dev) version, install directly from the repo:
+
+```bash
+pip install git+https://github.com/cloudera/impyla.git
+```
+
+or clone the repo:
+
+```bash
+git clone https://github.com/cloudera/impyla.git
+cd impyla
+python setup.py install
+```
+
+#### Running the tests
+
+impyla uses the [pytest][pytest] toolchain, and depends on the following
+environment variables:
+
+```bash
+export IMPYLA_TEST_HOST=your.impalad.com
+export IMPYLA_TEST_PORT=21050
+export IMPYLA_TEST_AUTH_MECH=NOSASL
+```
+
+To run the maximal set of tests, run
+
+```bash
+cd path/to/impyla
+py.test --connect impala
+```
+
+Leave out the `--connect` option to skip tests for DB API compliance.
+
+
+### Usage
+
+Impyla implements the [Python DB API v2.0 (PEP 249)][pep249] database interface
+(refer to it for API details):
+
+```python
+from impala.dbapi import connect
+conn = connect(host='my.host.com', port=21050)
+cursor = conn.cursor()
+cursor.execute('SELECT * FROM mytable LIMIT 100')
+print cursor.description  # prints the result set's schema
+results = cursor.fetchall()
+```
+
+The `Cursor` object also exposes the iterator interface, which is buffered
+(controlled by `cursor.arraysize`):
+
+```python
+cursor.execute('SELECT * FROM mytable LIMIT 100')
+for row in cursor:
+    print(row)
+```
+
+Furthermore the `Cursor` object returns you information about the columns
+returned in the query. This is useful to export your data as a csv file.
+
+```python
+import csv
+
+cursor.execute('SELECT * FROM mytable LIMIT 100')
+columns = [datum[0] for datum in cursor.description]
+targetfile = '/tmp/foo.csv'
+
+with open(targetfile, 'w', newline='') as outcsv:
+    writer = csv.writer(outcsv, delimiter=',', quotechar='"', quoting=csv.QUOTE_ALL, lineterminator='\n')
+    writer.writerow(columns)
+    for row in cursor:
+        writer.writerow(row)
+```
+
+You can also get back a pandas DataFrame object
+
+```python
+from impala.util import as_pandas
+df = as_pandas(cur)
+# carry df through scikit-learn, for example
+```
+
+
+[pep249]: http://legacy.python.org/dev/peps/pep-0249/
+[pandas]: http://pandas.pydata.org/
+[sklearn]: http://scikit-learn.org/
+[matplotlib]: http://matplotlib.org/
+[pytest]: http://pytest.org/latest/
+[sqlalchemy]: http://www.sqlalchemy.org/
+[ibis]: http://www.ibis-project.org/
+
+# How do I contribute code?
+You need to first sign and return an
+[ICLA](https://github.com/cloudera/native-toolchain/blob/icla/Cloudera%20ICLA_25APR2018.pdf)
+and
+[CCLA](https://github.com/cloudera/native-toolchain/blob/icla/Cloudera%20CCLA_25APR2018.pdf)
+before we can accept and redistribute your contribution. Once these are submitted you are
+free to start contributing to impyla. Submit these to CLA@cloudera.com.
+
+## Find
+We use Github issues to track bugs for this project. Find an issue that you would like to
+work on (or file one if you have discovered a new issue!). If no-one is working on it,
+assign it to yourself only if you intend to work on it shortly.
+
+It's a good idea to discuss your intended approach on the issue. You are much more
+likely to have your patch reviewed and committed if you've already got buy-in from the
+impyla community before you start.
+
+## Fix
+Now start coding! As you are writing your patch, please keep the following things in mind:
+
+First, please include tests with your patch. If your patch adds a feature or fixes a bug
+and does not include tests, it will generally not be accepted. If you are unsure how to
+write tests for a particular component, please ask on the issue for guidance.
+
+Second, please keep your patch narrowly targeted to the problem described by the issue.
+It's better for everyone if we maintain discipline about the scope of each patch. In
+general, if you find a bug while working on a specific feature, file a issue for the bug,
+check if you can assign it to yourself and fix it independently of the feature. This helps
+us to differentiate between bug fixes and features and allows us to build stable
+maintenance releases.
+
+Finally, please write a good, clear commit message, with a short, descriptive title and
+a message that is exactly long enough to explain what the problem was, and how it was
+fixed.
+
+Please create a pull request on github with your patch.
+
+
+%package -n python3-impyla
+Summary:	Python client for the Impala distributed query engine
+Provides:	python-impyla
+BuildRequires:	python3-devel
+BuildRequires:	python3-setuptools
+BuildRequires:	python3-pip
+%description -n python3-impyla
+# impyla
+
+Python client for HiveServer2 implementations (e.g., Impala, Hive) for
+distributed query engines.
+
+For higher-level Impala functionality, including a Pandas-like interface over
+distributed data sets, see the [Ibis project][ibis].
+
+### Features
+
+* HiveServer2 compliant; works with Impala and Hive, including nested data
+
+* Fully [DB API 2.0 (PEP 249)][pep249]-compliant Python client (similar to
+sqlite or MySQL clients) supporting Python 2.6+ and Python 3.3+.
+
+* Works with Kerberos, LDAP, SSL
+
+* [SQLAlchemy][sqlalchemy] connector
+
+* Converter to [pandas][pandas] `DataFrame`, allowing easy integration into the
+Python data stack (including [scikit-learn][sklearn] and
+[matplotlib][matplotlib]); but see the [Ibis project][ibis] for a richer
+experience
+
+### Dependencies
+
+Required:
+
+* Python 2.7+ or 3.5+
+
+* `six`, `bitarray`
+
+* `thrift==0.16.0`
+
+* `thrift_sasl==0.4.3`
+
+Optional:
+
+* `kerberos>=1.3.0` for Kerberos over HTTP support. This also requires Kerberos libraries
+   to be installed on your system - see [System Kerberos](#system-kerberos)
+
+* `pandas` for conversion to `DataFrame` objects; but see the [Ibis project][ibis] instead
+
+* `sqlalchemy` for the SQLAlchemy engine
+
+* `pytest` for running tests; `unittest2` for testing on Python 2.6
+
+
+#### System Kerberos
+
+Different systems require different packages to be installed to enable Kerberos support in
+Impyla. Some examples of how to install the packages on different distributions follow.
+
+Ubuntu:
+```bash
+apt-get install libkrb5-dev krb5-user
+```
+
+RHEL/CentOS:
+```bash
+yum install krb5-libs krb5-devel krb5-server krb5-workstation
+```
+
+### Installation
+
+Install the latest release with `pip`:
+
+```bash
+pip install impyla
+```
+
+For the latest (dev) version, install directly from the repo:
+
+```bash
+pip install git+https://github.com/cloudera/impyla.git
+```
+
+or clone the repo:
+
+```bash
+git clone https://github.com/cloudera/impyla.git
+cd impyla
+python setup.py install
+```
+
+#### Running the tests
+
+impyla uses the [pytest][pytest] toolchain, and depends on the following
+environment variables:
+
+```bash
+export IMPYLA_TEST_HOST=your.impalad.com
+export IMPYLA_TEST_PORT=21050
+export IMPYLA_TEST_AUTH_MECH=NOSASL
+```
+
+To run the maximal set of tests, run
+
+```bash
+cd path/to/impyla
+py.test --connect impala
+```
+
+Leave out the `--connect` option to skip tests for DB API compliance.
+
+
+### Usage
+
+Impyla implements the [Python DB API v2.0 (PEP 249)][pep249] database interface
+(refer to it for API details):
+
+```python
+from impala.dbapi import connect
+conn = connect(host='my.host.com', port=21050)
+cursor = conn.cursor()
+cursor.execute('SELECT * FROM mytable LIMIT 100')
+print cursor.description  # prints the result set's schema
+results = cursor.fetchall()
+```
+
+The `Cursor` object also exposes the iterator interface, which is buffered
+(controlled by `cursor.arraysize`):
+
+```python
+cursor.execute('SELECT * FROM mytable LIMIT 100')
+for row in cursor:
+    print(row)
+```
+
+Furthermore the `Cursor` object returns you information about the columns
+returned in the query. This is useful to export your data as a csv file.
+
+```python
+import csv
+
+cursor.execute('SELECT * FROM mytable LIMIT 100')
+columns = [datum[0] for datum in cursor.description]
+targetfile = '/tmp/foo.csv'
+
+with open(targetfile, 'w', newline='') as outcsv:
+    writer = csv.writer(outcsv, delimiter=',', quotechar='"', quoting=csv.QUOTE_ALL, lineterminator='\n')
+    writer.writerow(columns)
+    for row in cursor:
+        writer.writerow(row)
+```
+
+You can also get back a pandas DataFrame object
+
+```python
+from impala.util import as_pandas
+df = as_pandas(cur)
+# carry df through scikit-learn, for example
+```
+
+
+[pep249]: http://legacy.python.org/dev/peps/pep-0249/
+[pandas]: http://pandas.pydata.org/
+[sklearn]: http://scikit-learn.org/
+[matplotlib]: http://matplotlib.org/
+[pytest]: http://pytest.org/latest/
+[sqlalchemy]: http://www.sqlalchemy.org/
+[ibis]: http://www.ibis-project.org/
+
+# How do I contribute code?
+You need to first sign and return an
+[ICLA](https://github.com/cloudera/native-toolchain/blob/icla/Cloudera%20ICLA_25APR2018.pdf)
+and
+[CCLA](https://github.com/cloudera/native-toolchain/blob/icla/Cloudera%20CCLA_25APR2018.pdf)
+before we can accept and redistribute your contribution. Once these are submitted you are
+free to start contributing to impyla. Submit these to CLA@cloudera.com.
+
+## Find
+We use Github issues to track bugs for this project. Find an issue that you would like to
+work on (or file one if you have discovered a new issue!). If no-one is working on it,
+assign it to yourself only if you intend to work on it shortly.
+
+It's a good idea to discuss your intended approach on the issue. You are much more
+likely to have your patch reviewed and committed if you've already got buy-in from the
+impyla community before you start.
+
+## Fix
+Now start coding! As you are writing your patch, please keep the following things in mind:
+
+First, please include tests with your patch. If your patch adds a feature or fixes a bug
+and does not include tests, it will generally not be accepted. If you are unsure how to
+write tests for a particular component, please ask on the issue for guidance.
+
+Second, please keep your patch narrowly targeted to the problem described by the issue.
+It's better for everyone if we maintain discipline about the scope of each patch. In
+general, if you find a bug while working on a specific feature, file a issue for the bug,
+check if you can assign it to yourself and fix it independently of the feature. This helps
+us to differentiate between bug fixes and features and allows us to build stable
+maintenance releases.
+
+Finally, please write a good, clear commit message, with a short, descriptive title and
+a message that is exactly long enough to explain what the problem was, and how it was
+fixed.
+
+Please create a pull request on github with your patch.
+
+
+%package help
+Summary:	Development documents and examples for impyla
+Provides:	python3-impyla-doc
+%description help
+# impyla
+
+Python client for HiveServer2 implementations (e.g., Impala, Hive) for
+distributed query engines.
+
+For higher-level Impala functionality, including a Pandas-like interface over
+distributed data sets, see the [Ibis project][ibis].
+
+### Features
+
+* HiveServer2 compliant; works with Impala and Hive, including nested data
+
+* Fully [DB API 2.0 (PEP 249)][pep249]-compliant Python client (similar to
+sqlite or MySQL clients) supporting Python 2.6+ and Python 3.3+.
+
+* Works with Kerberos, LDAP, SSL
+
+* [SQLAlchemy][sqlalchemy] connector
+
+* Converter to [pandas][pandas] `DataFrame`, allowing easy integration into the
+Python data stack (including [scikit-learn][sklearn] and
+[matplotlib][matplotlib]); but see the [Ibis project][ibis] for a richer
+experience
+
+### Dependencies
+
+Required:
+
+* Python 2.7+ or 3.5+
+
+* `six`, `bitarray`
+
+* `thrift==0.16.0`
+
+* `thrift_sasl==0.4.3`
+
+Optional:
+
+* `kerberos>=1.3.0` for Kerberos over HTTP support. This also requires Kerberos libraries
+   to be installed on your system - see [System Kerberos](#system-kerberos)
+
+* `pandas` for conversion to `DataFrame` objects; but see the [Ibis project][ibis] instead
+
+* `sqlalchemy` for the SQLAlchemy engine
+
+* `pytest` for running tests; `unittest2` for testing on Python 2.6
+
+
+#### System Kerberos
+
+Different systems require different packages to be installed to enable Kerberos support in
+Impyla. Some examples of how to install the packages on different distributions follow.
+
+Ubuntu:
+```bash
+apt-get install libkrb5-dev krb5-user
+```
+
+RHEL/CentOS:
+```bash
+yum install krb5-libs krb5-devel krb5-server krb5-workstation
+```
+
+### Installation
+
+Install the latest release with `pip`:
+
+```bash
+pip install impyla
+```
+
+For the latest (dev) version, install directly from the repo:
+
+```bash
+pip install git+https://github.com/cloudera/impyla.git
+```
+
+or clone the repo:
+
+```bash
+git clone https://github.com/cloudera/impyla.git
+cd impyla
+python setup.py install
+```
+
+#### Running the tests
+
+impyla uses the [pytest][pytest] toolchain, and depends on the following
+environment variables:
+
+```bash
+export IMPYLA_TEST_HOST=your.impalad.com
+export IMPYLA_TEST_PORT=21050
+export IMPYLA_TEST_AUTH_MECH=NOSASL
+```
+
+To run the maximal set of tests, run
+
+```bash
+cd path/to/impyla
+py.test --connect impala
+```
+
+Leave out the `--connect` option to skip tests for DB API compliance.
+
+
+### Usage
+
+Impyla implements the [Python DB API v2.0 (PEP 249)][pep249] database interface
+(refer to it for API details):
+
+```python
+from impala.dbapi import connect
+conn = connect(host='my.host.com', port=21050)
+cursor = conn.cursor()
+cursor.execute('SELECT * FROM mytable LIMIT 100')
+print cursor.description  # prints the result set's schema
+results = cursor.fetchall()
+```
+
+The `Cursor` object also exposes the iterator interface, which is buffered
+(controlled by `cursor.arraysize`):
+
+```python
+cursor.execute('SELECT * FROM mytable LIMIT 100')
+for row in cursor:
+    print(row)
+```
+
+Furthermore the `Cursor` object returns you information about the columns
+returned in the query. This is useful to export your data as a csv file.
+
+```python
+import csv
+
+cursor.execute('SELECT * FROM mytable LIMIT 100')
+columns = [datum[0] for datum in cursor.description]
+targetfile = '/tmp/foo.csv'
+
+with open(targetfile, 'w', newline='') as outcsv:
+    writer = csv.writer(outcsv, delimiter=',', quotechar='"', quoting=csv.QUOTE_ALL, lineterminator='\n')
+    writer.writerow(columns)
+    for row in cursor:
+        writer.writerow(row)
+```
+
+You can also get back a pandas DataFrame object
+
+```python
+from impala.util import as_pandas
+df = as_pandas(cur)
+# carry df through scikit-learn, for example
+```
+
+
+[pep249]: http://legacy.python.org/dev/peps/pep-0249/
+[pandas]: http://pandas.pydata.org/
+[sklearn]: http://scikit-learn.org/
+[matplotlib]: http://matplotlib.org/
+[pytest]: http://pytest.org/latest/
+[sqlalchemy]: http://www.sqlalchemy.org/
+[ibis]: http://www.ibis-project.org/
+
+# How do I contribute code?
+You need to first sign and return an
+[ICLA](https://github.com/cloudera/native-toolchain/blob/icla/Cloudera%20ICLA_25APR2018.pdf)
+and
+[CCLA](https://github.com/cloudera/native-toolchain/blob/icla/Cloudera%20CCLA_25APR2018.pdf)
+before we can accept and redistribute your contribution. Once these are submitted you are
+free to start contributing to impyla. Submit these to CLA@cloudera.com.
+
+## Find
+We use Github issues to track bugs for this project. Find an issue that you would like to
+work on (or file one if you have discovered a new issue!). If no-one is working on it,
+assign it to yourself only if you intend to work on it shortly.
+
+It's a good idea to discuss your intended approach on the issue. You are much more
+likely to have your patch reviewed and committed if you've already got buy-in from the
+impyla community before you start.
+
+## Fix
+Now start coding! As you are writing your patch, please keep the following things in mind:
+
+First, please include tests with your patch. If your patch adds a feature or fixes a bug
+and does not include tests, it will generally not be accepted. If you are unsure how to
+write tests for a particular component, please ask on the issue for guidance.
+
+Second, please keep your patch narrowly targeted to the problem described by the issue.
+It's better for everyone if we maintain discipline about the scope of each patch. In
+general, if you find a bug while working on a specific feature, file a issue for the bug,
+check if you can assign it to yourself and fix it independently of the feature. This helps
+us to differentiate between bug fixes and features and allows us to build stable
+maintenance releases.
+
+Finally, please write a good, clear commit message, with a short, descriptive title and
+a message that is exactly long enough to explain what the problem was, and how it was
+fixed.
+
+Please create a pull request on github with your patch.
+
+
+%prep
+%autosetup -n impyla-0.18.0
+
+%build
+%py3_build
+
+%install
+%py3_install
+install -d -m755 %{buildroot}/%{_pkgdocdir}
+if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
+if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
+if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
+if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
+pushd %{buildroot}
+if [ -d usr/lib ]; then
+	find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst
+fi
+if [ -d usr/lib64 ]; then
+	find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst
+fi
+if [ -d usr/bin ]; then
+	find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst
+fi
+if [ -d usr/sbin ]; then
+	find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst
+fi
+touch doclist.lst
+if [ -d usr/share/man ]; then
+	find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst
+fi
+popd
+mv %{buildroot}/filelist.lst .
+mv %{buildroot}/doclist.lst .
+
+%files -n python3-impyla -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Mon Apr 10 2023 Python_Bot <Python_Bot@openeuler.org> - 0.18.0-1
+- Package Spec generated
diff --git a/sources b/sources
new file mode 100644
index 0000000..6b889b5
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+df7ba33db694f8623540aba5a1d0b11e  impyla-0.18.0.tar.gz