[jira] [Commented] (IMPALA-7976) Add a flag to disable sync using events at a table level
[ https://issues.apache.org/jira/browse/IMPALA-7976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760482#comment-16760482 ] Vihang Karajgaonkar commented on IMPALA-7976: - Adding the first version of the patch and linking the gerrit request > Add a flag to disable sync using events at a table level > > > Key: IMPALA-7976 > URL: https://issues.apache.org/jira/browse/IMPALA-7976 > Project: IMPALA > Issue Type: Sub-task >Reporter: Vihang Karajgaonkar >Assignee: Vihang Karajgaonkar >Priority: Major > > It is possible that certain tables need not be updated by the event > mechanism. Possible use-cases could be frequently updated tables (from > multiple systems) or for tables where we don't really need latest data. We > should be able to add a flag (parameter) to the table which can be used to > skip event processing for a given table. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Work started] (IMPALA-7976) Add a flag to disable sync using events at a table level
[ https://issues.apache.org/jira/browse/IMPALA-7976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-7976 started by Vihang Karajgaonkar. --- > Add a flag to disable sync using events at a table level > > > Key: IMPALA-7976 > URL: https://issues.apache.org/jira/browse/IMPALA-7976 > Project: IMPALA > Issue Type: Sub-task >Reporter: Vihang Karajgaonkar >Assignee: Vihang Karajgaonkar >Priority: Major > > It is possible that certain tables need not be updated by the event > mechanism. Possible use-cases could be frequently updated tables (from > multiple systems) or for tables where we don't really need latest data. We > should be able to add a flag (parameter) to the table which can be used to > skip event processing for a given table. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Commented] (IMPALA-8163) Local catalog mode needs to be visible on catalogd web UI if turned on
[ https://issues.apache.org/jira/browse/IMPALA-8163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760425#comment-16760425 ] Fredy Wijaya commented on IMPALA-8163: -- [~adrian.ng] May I know what you mean by visible on the web UI? I made an update in the web UI to show if a flag is an experimental or not: https://issues.apache.org/jira/browse/IMPALA-6521 > Local catalog mode needs to be visible on catalogd web UI if turned on > --- > > Key: IMPALA-8163 > URL: https://issues.apache.org/jira/browse/IMPALA-8163 > Project: IMPALA > Issue Type: Bug >Reporter: Adrian Ng >Assignee: Anurag Mantripragada >Priority: Major > > Once local catalog mode (i.e. metadata v2) is turned on (off by default), it > needs to be visible on catalogd web UI because it is an experimental protocol > so admins need to be aware of this. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Assigned] (IMPALA-8163) Local catalog mode needs to be visible on catalogd web UI if turned on
[ https://issues.apache.org/jira/browse/IMPALA-8163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrian Ng reassigned IMPALA-8163: - Assignee: Anurag Mantripragada > Local catalog mode needs to be visible on catalogd web UI if turned on > --- > > Key: IMPALA-8163 > URL: https://issues.apache.org/jira/browse/IMPALA-8163 > Project: IMPALA > Issue Type: Bug >Reporter: Adrian Ng >Assignee: Anurag Mantripragada >Priority: Major > > Once local catalog mode (i.e. metadata v2) is turned on (off by default), it > needs to be visible on catalogd web UI because it is an experimental protocol > so admins need to be aware of this. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Created] (IMPALA-8163) Local catalog mode needs to be visible on catalogd web UI if turned on
Adrian Ng created IMPALA-8163: - Summary: Local catalog mode needs to be visible on catalogd web UI if turned on Key: IMPALA-8163 URL: https://issues.apache.org/jira/browse/IMPALA-8163 Project: IMPALA Issue Type: Bug Reporter: Adrian Ng Once local catalog mode (i.e. metadata v2) is turned on (off by default), it needs to be visible on catalogd web UI because it is an experimental protocol so admins need to be aware of this. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Assigned] (IMPALA-7935) /catalog_object end point broken in LocalCatalog mode
[
https://issues.apache.org/jira/browse/IMPALA-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath v reassigned IMPALA-7935:
-
Assignee: Anurag Mantripragada
> /catalog_object end point broken in LocalCatalog mode
> -
>
> Key: IMPALA-7935
> URL: https://issues.apache.org/jira/browse/IMPALA-7935
> Project: IMPALA
> Issue Type: Bug
> Components: Catalog
>Affects Versions: Impala 3.1.0
>Reporter: bharath v
>Assignee: Anurag Mantripragada
>Priority: Major
> Labels: observability
>
> Start Impala coordinator in LocalCatalog mode (v2)
> {code}
> start-impala-cluster.py -s 1 --impalad_args="--use_local_catalog=true"
> --catalogd_args="--catalog_topic_mode=minimal"
> {code}
> Check the following URL.
> http://:25000/catalog_object?object_type=TABLE_name=functional_text_lzo.alltypesaggmultifiles
> It says,
> {noformat}
> Error: UnsupportedOperationException: LocalCatalog.getTCatalogObject
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Commented] (IMPALA-8105) Impala Doc: Document remote file handle cache
[ https://issues.apache.org/jira/browse/IMPALA-8105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760385#comment-16760385 ] Alex Rodoni commented on IMPALA-8105: - https://gerrit.cloudera.org/#/c/12362/ > Impala Doc: Document remote file handle cache > - > > Key: IMPALA-8105 > URL: https://issues.apache.org/jira/browse/IMPALA-8105 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Labels: future_release_doc, in_32 > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Assigned] (IMPALA-7921) Hive JVM aborts during data load
[
https://issues.apache.org/jira/browse/IMPALA-7921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrian Ng reassigned IMPALA-7921:
-
Assignee: Anurag Mantripragada (was: Tianyi Wang)
> Hive JVM aborts during data load
>
>
> Key: IMPALA-7921
> URL: https://issues.apache.org/jira/browse/IMPALA-7921
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
>Affects Versions: Impala 3.0
>Reporter: Lars Volker
>Assignee: Anurag Mantripragada
>Priority: Critical
> Labels: broken-build, flaky
>
> During a core test run I observed Hive's JVM crashing. Here is the stack
> trace from the core file it left behind:
> {noformat}
> CORE: ./core.1543762524.3579.java
> BINARY: /usr/java/jdk1.8.0_144/bin/java
> Core was generated by `/usr/java/jdk1.8.0_144/bin/java -Dproc_jar -Xmx2048m
> -Dhive.log.file=hive-serve'.
> Program terminated with signal SIGABRT, Aborted.
> ...
> #0 0x7f5b72fc81f7 in raise () from /lib64/libc.so.6
> #1 0x7f5b72fc98e8 in abort () from /lib64/libc.so.6
> #2 0x7f5b728c5185 in os::abort(bool) () from
> /usr/java/jdk1.8.0_144/jre/lib/amd64/server/libjvm.so
> #3 0x7f5b72a67593 in VMError::report_and_die() () from
> /usr/java/jdk1.8.0_144/jre/lib/amd64/server/libjvm.so
> #4 0x7f5b728ca68f in JVM_handle_linux_signal () from
> /usr/java/jdk1.8.0_144/jre/lib/amd64/server/libjvm.so
> #5 0x7f5b728c0be3 in signalHandler(int, siginfo*, void*) () from
> /usr/java/jdk1.8.0_144/jre/lib/amd64/server/libjvm.so
> #6
> #7 0x080721b0 in ?? ()
> #8 0x in ?? ()
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Work started] (IMPALA-8105) Impala Doc: Document remote file handle cache
[ https://issues.apache.org/jira/browse/IMPALA-8105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-8105 started by Alex Rodoni. --- > Impala Doc: Document remote file handle cache > - > > Key: IMPALA-8105 > URL: https://issues.apache.org/jira/browse/IMPALA-8105 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Labels: future_release_doc, in_32 > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Commented] (IMPALA-7265) Cache remote file handles
[ https://issues.apache.org/jira/browse/IMPALA-7265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760373#comment-16760373 ] Joe McDonnell commented on IMPALA-7265: --- [~arodoni_cloudera] The cache_remote_file_handles parameter is merged with the default value of false. This Jira is open to track setting the default to true. > Cache remote file handles > - > > Key: IMPALA-7265 > URL: https://issues.apache.org/jira/browse/IMPALA-7265 > Project: IMPALA > Issue Type: Improvement > Components: Backend >Affects Versions: Impala 3.1.0 >Reporter: Joe McDonnell >Assignee: Joe McDonnell >Priority: Critical > > The file handle cache currently does not allow caching remote file handles. > This means that clusters that have a lot of remote reads can suffer from > overloading the NameNode. Impala should be able to cache remote file handles. > There are some open questions about remote file handles and whether they > behave differently from local file handles. In particular: > # Is there any resource constraint on the number of remote file handles > open? (e.g. do they maintain a network connection?) > # Are there any semantic differences in how remote file handles behave when > files are deleted, overwritten, or appended? > # Are there any extra failure cases for remote file handles? (i.e. if a > machine goes down or a remote file handle is left open for an extended period > of time) > The form of caching will depend on the answers, but at the very least, it > should be possible to cache a remote file handle at the level of a query so > that a Parquet file with multiple columns can share file handles. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Commented] (IMPALA-7265) Cache remote file handles
[ https://issues.apache.org/jira/browse/IMPALA-7265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760368#comment-16760368 ] Alex Rodoni commented on IMPALA-7265: - [~joemcdonnell] Could you confirm that this will be in Rel 3.2? The code is merged, but this ticket is still in progress. > Cache remote file handles > - > > Key: IMPALA-7265 > URL: https://issues.apache.org/jira/browse/IMPALA-7265 > Project: IMPALA > Issue Type: Improvement > Components: Backend >Affects Versions: Impala 3.1.0 >Reporter: Joe McDonnell >Assignee: Joe McDonnell >Priority: Critical > > The file handle cache currently does not allow caching remote file handles. > This means that clusters that have a lot of remote reads can suffer from > overloading the NameNode. Impala should be able to cache remote file handles. > There are some open questions about remote file handles and whether they > behave differently from local file handles. In particular: > # Is there any resource constraint on the number of remote file handles > open? (e.g. do they maintain a network connection?) > # Are there any semantic differences in how remote file handles behave when > files are deleted, overwritten, or appended? > # Are there any extra failure cases for remote file handles? (i.e. if a > machine goes down or a remote file handle is left open for an extended period > of time) > The form of caching will depend on the answers, but at the very least, it > should be possible to cache a remote file handle at the level of a query so > that a Parquet file with multiple columns can share file handles. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Work started] (IMPALA-8104) Impala Doc: Doc IF NOT EXISTS in ALTER TABLE
[ https://issues.apache.org/jira/browse/IMPALA-8104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-8104 started by Alex Rodoni. --- > Impala Doc: Doc IF NOT EXISTS in ALTER TABLE > > > Key: IMPALA-8104 > URL: https://issues.apache.org/jira/browse/IMPALA-8104 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Labels: future_release_doc, in_32 > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Commented] (IMPALA-8104) Impala Doc: Doc IF NOT EXISTS in ALTER TABLE
[ https://issues.apache.org/jira/browse/IMPALA-8104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760362#comment-16760362 ] Alex Rodoni commented on IMPALA-8104: - https://gerrit.cloudera.org/#/c/12361/ > Impala Doc: Doc IF NOT EXISTS in ALTER TABLE > > > Key: IMPALA-8104 > URL: https://issues.apache.org/jira/browse/IMPALA-8104 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Labels: future_release_doc, in_32 > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-7920) Impala 3.2 Doc: Doc Levenshtein edit distance built-in function
[ https://issues.apache.org/jira/browse/IMPALA-7920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7920. --- Resolution: Fixed Fix Version/s: Impala 3.2.0 > Impala 3.2 Doc: Doc Levenshtein edit distance built-in function > --- > > Key: IMPALA-7920 > URL: https://issues.apache.org/jira/browse/IMPALA-7920 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Affects Versions: Impala 3.2.0 >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Labels: future_release_doc, in_32 > Fix For: Impala 3.2.0 > > > levenshtein(string source, string target) returns int -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-2200) [Cloudera][ODBC] (10000) General error: Unexpected exception has been caught.
[ https://issues.apache.org/jira/browse/IMPALA-2200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Rahn closed IMPALA-2200. - Resolution: Information Provided > [Cloudera][ODBC] (1) General error: Unexpected exception has been caught. > - > > Key: IMPALA-2200 > URL: https://issues.apache.org/jira/browse/IMPALA-2200 > Project: IMPALA > Issue Type: Bug > Components: Clients >Affects Versions: Impala 2.2 > Environment: Server: > OS: CentOS 6.6 > CDH 5.4.4 cluster with Cloudera manager - > Version: Cloudera Express 5.4.3 (#258 built by jenkins on 20150625-2046 git: > 1139ffb081360fbbb1be8a19a87ca3c52ee4b1cf) > Impala: impalad version 2.2.0-cdh5.4.4 RELEASE (build > a13d3c6b203e79a284b509df821bffbe229e6dc3) > Client: > OS: Windows 7/8 > client app: Tableau Desktop > Latest, at the moment, Impala-ODBC driver - > http://www.cloudera.com/content/cloudera/en/downloads/connectors/impala/odbc/impala-odbc-v2-5-29.html > Tableau desktop: version 8/9 >Reporter: Boyan Bonev >Assignee: Syed A. Hashmi >Priority: Minor > Labels: impala, odbc > Attachments: SimbaImpalaODBC_driver.log > > > Hi, > We are have a CDH 5.4.4 cluster and use Impala for add-hoc data analysis. We > also use Tableau for data visualization. The Tableau connects to Impala using > your ODBC driver. We experience several issues, but most important one is > that sometimes (1 out of 10 queries) our queries fail for unknown issue. When > we retry the issues is gone till the next occurrence. There is no info in the > server and almost no info in the ODBC client log (see attachment). Actually > the the only message that the client shows is logged in the ODBC log: > Aug 10 14:02:43 ERROR 8284 Statement::SQLPrepareW: [Cloudera][ODBC] (1) > General error: Unexpected exception has been caught. > Judging by this we suspect that this might be an ODBC driver issue in the > client in the prepared statement logic. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Commented] (IMPALA-5040) User Name authentication (i.e. AuthMech=2) causes JDBC connection to get HUNG.
[
https://issues.apache.org/jira/browse/IMPALA-5040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760318#comment-16760318
]
Greg Rahn commented on IMPALA-5040:
---
Closing issue since this JDBC driver is not part of Apache Impala.
> User Name authentication (i.e. AuthMech=2) causes JDBC connection to get HUNG.
> --
>
> Key: IMPALA-5040
> URL: https://issues.apache.org/jira/browse/IMPALA-5040
> Project: IMPALA
> Issue Type: Bug
> Components: Clients
>Affects Versions: Impala 2.2.4
>Reporter: Sudarshan
>Priority: Major
> Attachments: ImpalaJDBC_driver.log, Impala_connection_0.log,
> impalad.INFO
>
>
> Creating a JDBC connection with "AuthMech=2", [jdbc_url] with Cloudera JDBC
> Driver for Impala Version 2.5.36, causes the JDBC connection to get HUNG for
> a long time. It never returns. netstat shows that a TCP connection is
> established and it remains in this state for a long time.
> {code:java}
> [root@nightly59-unsecure-2 impalad]# netstat -an | grep 21050
> tcp0 0 :::21050:::*
> LISTEN
> tcp0 0 :::172.31.113.152:21050 :::172.16.1.48:50028
> ESTABLISHED
> [root@nightly59-unsecure-2 impalad]#
> {code}
> [jdbc_url]
> jdbc:impala://nightly59-unsecure-2.gce.cloudera.com:21050/default;AuthMech=2;REQUEST_POOL=sudarshan_pool;UID=sudarshan;LogLevel=6;LogPath=/tmp/IMPALA_TEST
> Entire source code is as follows.
> {code:java}
> import java.sql.Connection;
> import java.sql.DriverManager;
> import java.sql.ResultSet;
> import java.sql.Statement;
> public class SampleCode_Impala_Unsecure {
> public static final String JDBC_4_DRIVER =
> "com.cloudera.impala.jdbc4.Driver";
> public static final String DRIVER_CLASS = JDBC_4_DRIVER;
> public static final String CONNECTION_URL =
> "jdbc:impala://nightly59-unsecure-2.gce.cloudera.com:21050/default;AuthMech=2;REQUEST_POOL=sudarshan_pool;UID=sudarshan;LogLevel=6;LogPath=/tmp/IMPALA_TEST";
>public static void main(String[] args) throws Exception{
> Class.forName(DRIVER_CLASS);
> Connection connection = DriverManager.getConnection(CONNECTION_URL);
> Statement st = connection.createStatement();
> ResultSet rs = st.executeQuery("select 'hello' ");
> while (rs.next()) {
> System.out.println(rs.getString(1));
> }
> rs.close();
> st.close();
> connection.close();
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Commented] (IMPALA-7920) Impala 3.2 Doc: Doc Levenshtein edit distance built-in function
[ https://issues.apache.org/jira/browse/IMPALA-7920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760319#comment-16760319 ] Alex Rodoni commented on IMPALA-7920: - https://gerrit.cloudera.org/#/c/12357/ > Impala 3.2 Doc: Doc Levenshtein edit distance built-in function > --- > > Key: IMPALA-7920 > URL: https://issues.apache.org/jira/browse/IMPALA-7920 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Affects Versions: Impala 3.2.0 >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Labels: future_release_doc, in_32 > > levenshtein(string source, string target) returns int -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-5040) User Name authentication (i.e. AuthMech=2) causes JDBC connection to get HUNG.
[
https://issues.apache.org/jira/browse/IMPALA-5040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Rahn closed IMPALA-5040.
-
Resolution: Information Provided
> User Name authentication (i.e. AuthMech=2) causes JDBC connection to get HUNG.
> --
>
> Key: IMPALA-5040
> URL: https://issues.apache.org/jira/browse/IMPALA-5040
> Project: IMPALA
> Issue Type: Bug
> Components: Clients
>Affects Versions: Impala 2.2.4
>Reporter: Sudarshan
>Priority: Major
> Attachments: ImpalaJDBC_driver.log, Impala_connection_0.log,
> impalad.INFO
>
>
> Creating a JDBC connection with "AuthMech=2", [jdbc_url] with Cloudera JDBC
> Driver for Impala Version 2.5.36, causes the JDBC connection to get HUNG for
> a long time. It never returns. netstat shows that a TCP connection is
> established and it remains in this state for a long time.
> {code:java}
> [root@nightly59-unsecure-2 impalad]# netstat -an | grep 21050
> tcp0 0 :::21050:::*
> LISTEN
> tcp0 0 :::172.31.113.152:21050 :::172.16.1.48:50028
> ESTABLISHED
> [root@nightly59-unsecure-2 impalad]#
> {code}
> [jdbc_url]
> jdbc:impala://nightly59-unsecure-2.gce.cloudera.com:21050/default;AuthMech=2;REQUEST_POOL=sudarshan_pool;UID=sudarshan;LogLevel=6;LogPath=/tmp/IMPALA_TEST
> Entire source code is as follows.
> {code:java}
> import java.sql.Connection;
> import java.sql.DriverManager;
> import java.sql.ResultSet;
> import java.sql.Statement;
> public class SampleCode_Impala_Unsecure {
> public static final String JDBC_4_DRIVER =
> "com.cloudera.impala.jdbc4.Driver";
> public static final String DRIVER_CLASS = JDBC_4_DRIVER;
> public static final String CONNECTION_URL =
> "jdbc:impala://nightly59-unsecure-2.gce.cloudera.com:21050/default;AuthMech=2;REQUEST_POOL=sudarshan_pool;UID=sudarshan;LogLevel=6;LogPath=/tmp/IMPALA_TEST";
>public static void main(String[] args) throws Exception{
> Class.forName(DRIVER_CLASS);
> Connection connection = DriverManager.getConnection(CONNECTION_URL);
> Statement st = connection.createStatement();
> ResultSet rs = st.executeQuery("select 'hello' ");
> while (rs.next()) {
> System.out.println(rs.getString(1));
> }
> rs.close();
> st.close();
> connection.close();
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Work started] (IMPALA-7920) Impala 3.2 Doc: Doc Levenshtein edit distance built-in function
[ https://issues.apache.org/jira/browse/IMPALA-7920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-7920 started by Alex Rodoni. --- > Impala 3.2 Doc: Doc Levenshtein edit distance built-in function > --- > > Key: IMPALA-7920 > URL: https://issues.apache.org/jira/browse/IMPALA-7920 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Affects Versions: Impala 3.2.0 >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Labels: future_release_doc, in_32 > > levenshtein(string source, string target) returns int -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Created] (IMPALA-8162) Add memory reserved and memory admitted per backend to the /backends debug page
Bikramjeet Vig created IMPALA-8162: -- Summary: Add memory reserved and memory admitted per backend to the /backends debug page Key: IMPALA-8162 URL: https://issues.apache.org/jira/browse/IMPALA-8162 Project: IMPALA Issue Type: Improvement Reporter: Bikramjeet Vig Assignee: Bikramjeet Vig -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Commented] (IMPALA-8161) Impala Doc: Document the supported Date and Time patterns
[ https://issues.apache.org/jira/browse/IMPALA-8161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760258#comment-16760258 ] Alex Rodoni commented on IMPALA-8161: - [~gaborkaszab] > Impala Doc: Document the supported Date and Time patterns > - > > Key: IMPALA-8161 > URL: https://issues.apache.org/jira/browse/IMPALA-8161 > Project: IMPALA > Issue Type: Task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Labels: future_release_doc, in_32 > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Created] (IMPALA-8161) Impala Doc: Document the supported Date and Time patterns
Alex Rodoni created IMPALA-8161: --- Summary: Impala Doc: Document the supported Date and Time patterns Key: IMPALA-8161 URL: https://issues.apache.org/jira/browse/IMPALA-8161 Project: IMPALA Issue Type: Task Components: Docs Reporter: Alex Rodoni Assignee: Alex Rodoni -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-8161) Impala Doc: Document the supported Date and Time patterns
[ https://issues.apache.org/jira/browse/IMPALA-8161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni updated IMPALA-8161: Labels: future_release_doc in_32 (was: ) > Impala Doc: Document the supported Date and Time patterns > - > > Key: IMPALA-8161 > URL: https://issues.apache.org/jira/browse/IMPALA-8161 > Project: IMPALA > Issue Type: Task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Labels: future_release_doc, in_32 > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-8160) Impala Doc: Doc CAST(... AS ... FORMAT )
[ https://issues.apache.org/jira/browse/IMPALA-8160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni updated IMPALA-8160: Labels: future_release_doc in_32 (was: future_release_doc) > Impala Doc: Doc CAST(... AS ... FORMAT ) > -- > > Key: IMPALA-8160 > URL: https://issues.apache.org/jira/browse/IMPALA-8160 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Labels: future_release_doc, in_32 > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Commented] (IMPALA-4018) Add support for SQL:2016 datetime templates/patterns/masks to CAST(... AS ... FORMAT )
[
https://issues.apache.org/jira/browse/IMPALA-4018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760232#comment-16760232
]
Alex Rodoni commented on IMPALA-4018:
-
[~gaborkaszab] Is this targeted for 3.2 release?
> Add support for SQL:2016 datetime templates/patterns/masks to CAST(... AS ...
> FORMAT )
>
>
> Key: IMPALA-4018
> URL: https://issues.apache.org/jira/browse/IMPALA-4018
> Project: IMPALA
> Issue Type: New Feature
> Components: Frontend
>Affects Versions: Impala 2.2.4
>Reporter: Greg Rahn
>Assignee: Gabor Kaszab
>Priority: Critical
> Labels: ansi-sql, compatibility, sql-language
>
> *Summary*
> The format masks/templates for currently are implemented using the [Java
> SimpleDateFormat
> patterns|http://docs.oracle.com/javase/8/docs/api/java/text/SimpleDateFormat.html],
> and although this is what Hive has implemented, it is not what most standard
> SQL systems implement. For example see
> [Vertica|https://my.vertica.com/docs/7.2.x/HTML/Content/Authoring/SQLReferenceManual/Functions/Formatting/TemplatePatternsForDateTimeFormatting.htm],
>
> [Netezza|http://www.ibm.com/support/knowledgecenter/SSULQD_7.2.1/com.ibm.nz.dbu.doc/r_dbuser_ntz_sql_extns_templ_patterns_date_time_conv.html],
>
> [Oracle|https://docs.oracle.com/database/121/SQLRF/sql_elements004.htm#SQLRF00212],
> and
> [PostgreSQL|https://www.postgresql.org/docs/9.5/static/functions-formatting.html#FUNCTIONS-FORMATTING-DATETIME-TABLE].
>
> *Examples of incompatibilities*
> {noformat}
> -- PostgreSQL/Netezza/Vertica/Oracle
> select to_timestamp('May 15, 2015 12:00:00', 'mon dd, hh:mi:ss');
> -- Impala
> select to_timestamp('May 15, 2015 12:00:00', 'MMM dd, HH:mm:ss');
> -- PostgreSQL/Netezza/Vertica/Oracle
> select to_timestamp('2015-02-14 20:19:07','-mm-dd hh24:mi:ss');
> -- Impala
> select to_timestamp('2015-02-14 20:19:07','-MM-dd HH:mm:ss');
> -- Vertica/Oracle
> select to_timestamp('2015-02-14 20:19:07.123456','-mm-dd hh24:mi:ss.ff');
> -- Impala
> select to_timestamp('2015-02-14 20:19:07.123456','-MM-dd
> HH:mm:ss.SS');
> {noformat}
> *Considerations*
> Because this is a change in default behavior for to_timestamp(), if possible,
> having a feature flag to revert to the legacy Java SimpleDateFormat patterns
> should be strongly considered. This would allow users to chose the behavior
> they desire and scope it to a session if need be.
> SQL:2016 defines the following datetime templates
> {noformat}
> ::=
> { }...
> ::=
>
> |
> ::=
>
> |
> |
> |
> |
> |
> |
> |
> |
> |
> |
> |
> |
> |
> ::=
>
> |
> |
> |
> |
> |
> |
> |
> ::=
> | YYY | YY | Y
> ::=
> | RR
> ::=
> MM
> ::=
> DD
> ::=
> DDD
> ::=
> HH | HH12
> ::=
> HH24
> ::=
> MI
> ::=
> SS
> ::=
> S
> ::=
> FF1 | FF2 | FF3 | FF4 | FF5 | FF6 | FF7 | FF8 | FF9
> ::=
> A.M. | P.M.
> ::=
> TZH
> ::=
> TZM
> {noformat}
> SQL:2016 also introduced the FORMAT clause for CAST which is the standard way
> to do string <> datetime conversions
> {noformat}
> ::=
> CAST
>AS
> [ FORMAT ]
>
> ::=
>
> |
> ::=
>
> |
> ::=
>
> {noformat}
> For example:
> {noformat}
> CAST( AS [FORMAT ])
> CAST( AS [FORMAT ])
> cast(dt as string format 'DD-MM-')
> cast('01-05-2017' as date format 'DD-MM-')
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Created] (IMPALA-8160) Impala Doc: Doc CAST(... AS ... FORMAT )
Alex Rodoni created IMPALA-8160: --- Summary: Impala Doc: Doc CAST(... AS ... FORMAT ) Key: IMPALA-8160 URL: https://issues.apache.org/jira/browse/IMPALA-8160 Project: IMPALA Issue Type: Sub-task Components: Docs Reporter: Alex Rodoni Assignee: Alex Rodoni -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Resolved] (IMPALA-8092) Add a debug page to provide better observability for admission control
[ https://issues.apache.org/jira/browse/IMPALA-8092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig resolved IMPALA-8092. Resolution: Fixed Fix Version/s: Impala 3.2.0 > Add a debug page to provide better observability for admission control > -- > > Key: IMPALA-8092 > URL: https://issues.apache.org/jira/browse/IMPALA-8092 > Project: IMPALA > Issue Type: Improvement >Reporter: Bikramjeet Vig >Assignee: Bikramjeet Vig >Priority: Critical > Labels: admission-control, observability > Fix For: Impala 3.2.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-8159) TAcceptQueueServer: Caught TException: invalid sasl status
[
https://issues.apache.org/jira/browse/IMPALA-8159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinjie Zhang updated IMPALA-8159:
-
Environment:
python: 3.6.6
impyla: 0.14.1
thrift-sasl: https://github.com/yimian/thrift_sasl.git
impala: 2.11.0 from cdh5.14.2-1.cdh5.14.2.p0.3
os: CentOS Linux release 7.2.1511 (Core)
was:
python: 3.6.6
impyla: 0.14.1
thrift-sasl: https://github.com/yimian/thrift_sasl.git
impala: 2.11.0 from cdh5.14.2-1.cdh5.14.2.p0.3
> TAcceptQueueServer: Caught TException: invalid sasl status
> --
>
> Key: IMPALA-8159
> URL: https://issues.apache.org/jira/browse/IMPALA-8159
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
>Affects Versions: Impala 2.11.0
> Environment: python: 3.6.6
> impyla: 0.14.1
> thrift-sasl: https://github.com/yimian/thrift_sasl.git
> impala: 2.11.0 from cdh5.14.2-1.cdh5.14.2.p0.3
> os: CentOS Linux release 7.2.1511 (Core)
>Reporter: Jinjie Zhang
>Priority: Critical
>
> I enable ldap user authentication for impalad. I run the following code to
> test impalad stability, and I find when I run ten thousand times, the
> following error will occur two times in impalad.INFO log file.
> test code:
>
> {code:java}
> import impala.dbapi
> test_conf =
> { 'host': '172.16.24.xx', 'port': 21050, 'user': '', 'password': 'x' }
> def test_impala(conf):
> conn = impala.dbapi.connect(**conf)
> conn.close()
>
> N = 1
> for i in range(N):
> test_impala(test_conf){code}
>
> error info:
> {code:java}
> I0204 15:41:40.600821 168276 thrift-util.cc:123] TAcceptQueueServer: Caught
> TException: invalid sasl status
> I0204 15:46:40.600451 168276 thrift-util.cc:123] TAcceptQueueServer: Caught
> TException: EAGAIN (timed out)
> I0204 15:46:40.609858 168276 authentication.cc:268] Trying simple LDAP bind
> for: uid=,dc=
> I0204 15:46:40.729262 168276 authentication.cc:280] LDAP bind successful
> I0204 15:46:40.729287 168276 authentication.cc:478] Successfully
> authenticated client user ""{code}
> When this error occurs, the connect request will hang for serveral minutes,
> and all subsequent connect request including request from hue will hang too.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Commented] (IMPALA-4337) Wrap long lines in explain plans
[ https://issues.apache.org/jira/browse/IMPALA-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16759879#comment-16759879 ] Balazs Jeszenszky commented on IMPALA-4337: --- I don't think we should do this - text editors can wrap as needed, but if Impala wraps the text, there's no way to easily unwrap it. It'd make it more difficult to eyeball plans with long predicate lists. > Wrap long lines in explain plans > > > Key: IMPALA-4337 > URL: https://issues.apache.org/jira/browse/IMPALA-4337 > Project: IMPALA > Issue Type: Improvement > Components: Frontend >Affects Versions: Impala 2.8.0 >Reporter: Henry Robinson >Priority: Minor > Labels: newbie, ramp-up > > Explain plans can have very long lines, particularly when printing lists of > expressions. It should be possible to wrap, and still correctly indent, those > lines. > This is trickier than it sounds because they have to be wrapped in the > context of their place in the plan (i.e. with appropriate prefixes etc). It's > a good opportunity to split out explain plan generation from presentation, > centralizing the logic so that this kind of change is easy to make. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Commented] (IMPALA-7843) MT_DOP should be configurable per subquery
[ https://issues.apache.org/jira/browse/IMPALA-7843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16759838#comment-16759838 ] Jon Apgar commented on IMPALA-7843: --- Thanks I will definitely try it out and give feedback as I have it! > MT_DOP should be configurable per subquery > -- > > Key: IMPALA-7843 > URL: https://issues.apache.org/jira/browse/IMPALA-7843 > Project: IMPALA > Issue Type: Improvement >Reporter: Jon Apgar >Priority: Major > > MT_DOP > 0 will cause queries with JOIN statements to fail, however the > *subqueries* within the main query _might_ otherwise have been able to run > successfully with MT_DOP > 0. > A use-case for subqueries may be to limit the size of complex joins or > eliminate redundant aggregation in the outer query, By allowing MT_DOP > 0 on > subqueries you could significantly speed up the entire query. > MT_DOP is not the only session variable which may be effectively configured > per subquery. Perhaps there should be a way of specifying applicable > variables within the select statement of a query. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-8159) TAcceptQueueServer: Caught TException: invalid sasl status
[
https://issues.apache.org/jira/browse/IMPALA-8159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinjie Zhang updated IMPALA-8159:
-
Environment:
python: 3.6.6
impyla: 0.14.1
thrift-sasl: https://github.com/yimian/thrift_sasl.git
impala: 2.11.0 from cdh5.14.2-1.cdh5.14.2.p0.3
was:
python: 3.6.6
impyla: 0.14.1
thrift-sasl: https://github.com/cloudera/thrift_sasl.git
impala: 2.11.0 from cdh5.14.2-1.cdh5.14.2.p0.3
> TAcceptQueueServer: Caught TException: invalid sasl status
> --
>
> Key: IMPALA-8159
> URL: https://issues.apache.org/jira/browse/IMPALA-8159
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
>Affects Versions: Impala 2.11.0
> Environment: python: 3.6.6
> impyla: 0.14.1
> thrift-sasl: https://github.com/yimian/thrift_sasl.git
> impala: 2.11.0 from cdh5.14.2-1.cdh5.14.2.p0.3
>Reporter: Jinjie Zhang
>Priority: Critical
>
> I enable ldap user authentication for impalad. I run the following code to
> test impalad stability, and I find when I run ten thousand times, the
> following error will occur two times in impalad.INFO log file.
> test code:
>
> {code:java}
> import impala.dbapi
> test_conf =
> { 'host': '172.16.24.xx', 'port': 21050, 'user': '', 'password': 'x' }
> def test_impala(conf):
> conn = impala.dbapi.connect(**conf)
> conn.close()
>
> N = 1
> for i in range(N):
> test_impala(test_conf){code}
>
> error info:
> {code:java}
> I0204 15:41:40.600821 168276 thrift-util.cc:123] TAcceptQueueServer: Caught
> TException: invalid sasl status
> I0204 15:46:40.600451 168276 thrift-util.cc:123] TAcceptQueueServer: Caught
> TException: EAGAIN (timed out)
> I0204 15:46:40.609858 168276 authentication.cc:268] Trying simple LDAP bind
> for: uid=,dc=
> I0204 15:46:40.729262 168276 authentication.cc:280] LDAP bind successful
> I0204 15:46:40.729287 168276 authentication.cc:478] Successfully
> authenticated client user ""{code}
> When this error occurs, the connect request will hang for serveral minutes,
> and all subsequent connect request including request from hue will hang too.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-8159) TAcceptQueueServer: Caught TException: invalid sasl status
[
https://issues.apache.org/jira/browse/IMPALA-8159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinjie Zhang updated IMPALA-8159:
-
Priority: Critical (was: Major)
> TAcceptQueueServer: Caught TException: invalid sasl status
> --
>
> Key: IMPALA-8159
> URL: https://issues.apache.org/jira/browse/IMPALA-8159
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
>Affects Versions: Impala 2.11.0
> Environment: python: 3.6.6
> impyla: 0.14.1
> thrift-sasl: https://github.com/cloudera/thrift_sasl.git
> impala: 2.11.0 from cdh5.14.2-1.cdh5.14.2.p0.3
>Reporter: Jinjie Zhang
>Priority: Critical
>
> I enable ldap user authentication for impalad. I run the following code to
> test impalad stability, and I find when I run ten thousand times, the
> following error will occur two times in impalad.INFO log file.
> test code:
>
> {code:java}
> import impala.dbapi
> test_conf =
> { 'host': '172.16.24.xx', 'port': 21050, 'user': '', 'password': 'x' }
> def test_impala(conf):
> conn = impala.dbapi.connect(**conf)
> conn.close()
>
> N = 1
> for i in range(N):
> test_impala(test_conf){code}
>
> error info:
> {code:java}
> I0204 15:41:40.600821 168276 thrift-util.cc:123] TAcceptQueueServer: Caught
> TException: invalid sasl status
> I0204 15:46:40.600451 168276 thrift-util.cc:123] TAcceptQueueServer: Caught
> TException: EAGAIN (timed out)
> I0204 15:46:40.609858 168276 authentication.cc:268] Trying simple LDAP bind
> for: uid=,dc=
> I0204 15:46:40.729262 168276 authentication.cc:280] LDAP bind successful
> I0204 15:46:40.729287 168276 authentication.cc:478] Successfully
> authenticated client user ""{code}
> When this error occurs, the connect request will hang for serveral minutes,
> and all subsequent connect request including request from hue will hang too.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-8159) TAcceptQueueServer: Caught TException: invalid sasl status
[
https://issues.apache.org/jira/browse/IMPALA-8159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinjie Zhang updated IMPALA-8159:
-
Description:
I enable ldap user authentication for impalad. I run the following code to test
impalad stability, and I find when I run ten thousand times, the following
error will occur two times in impalad.INFO log file.
test code:
{code:java}
import impala.dbapi
test_conf =
{ 'host': '172.16.24.xx', 'port': 21050, 'user': '', 'password': 'x' }
def test_impala(conf):
conn = impala.dbapi.connect(**conf)
conn.close()
N = 1
for i in range(N):
test_impala(test_conf){code}
error info:
{code:java}
I0204 15:41:40.600821 168276 thrift-util.cc:123] TAcceptQueueServer: Caught
TException: invalid sasl status{code}
When this error occurs, the connect request will hang for one minute or two
minutes, and all subsequent connect request including request from hue will
hang too.
was:
I enable ldap user authentication for impalad. I run the following code to test
impalad stability, and I find when I run ten thousand times, the following
error will occur two times in impalad.INFO log file.
test code:
import impala.dbapi
test_conf =
{ 'host': '172.16.24.xx', 'port': 21050, 'user': '', 'password': 'x' }
def test_impala(conf):
conn = impala.dbapi.connect(**conf)
conn.close()
N = 1
for i in range(N):
test_impala(test_conf)
error info:
```
I0204 15:41:40.600821 168276 thrift-util.cc:123] TAcceptQueueServer: Caught
TException: invalid sasl status
```
When this error occurs, the connect request will hang for one minute or two
minutes, and all subsequent connect request including request from hue will
hang too.
> TAcceptQueueServer: Caught TException: invalid sasl status
> --
>
> Key: IMPALA-8159
> URL: https://issues.apache.org/jira/browse/IMPALA-8159
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
>Affects Versions: Impala 2.11.0
> Environment: python: 3.6.6
> impyla: 0.14.1
> thrift-sasl: https://github.com/cloudera/thrift_sasl.git
> impala: 2.11.0 from cdh5.14.2-1.cdh5.14.2.p0.3
>Reporter: Jinjie Zhang
>Priority: Major
>
> I enable ldap user authentication for impalad. I run the following code to
> test impalad stability, and I find when I run ten thousand times, the
> following error will occur two times in impalad.INFO log file.
> test code:
>
> {code:java}
> import impala.dbapi
> test_conf =
> { 'host': '172.16.24.xx', 'port': 21050, 'user': '', 'password': 'x' }
> def test_impala(conf):
> conn = impala.dbapi.connect(**conf)
> conn.close()
>
> N = 1
> for i in range(N):
> test_impala(test_conf){code}
>
> error info:
> {code:java}
> I0204 15:41:40.600821 168276 thrift-util.cc:123] TAcceptQueueServer: Caught
> TException: invalid sasl status{code}
> When this error occurs, the connect request will hang for one minute or two
> minutes, and all subsequent connect request including request from hue will
> hang too.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-8159) TAcceptQueueServer: Caught TException: invalid sasl status
[
https://issues.apache.org/jira/browse/IMPALA-8159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinjie Zhang updated IMPALA-8159:
-
Description:
I enable ldap user authentication for impalad. I run the following code to test
impalad stability, and I find when I run ten thousand times, the following
error will occur two times in impalad.INFO log file.
test code:
{code:java}
import impala.dbapi
test_conf =
{ 'host': '172.16.24.xx', 'port': 21050, 'user': '', 'password': 'x' }
def test_impala(conf):
conn = impala.dbapi.connect(**conf)
conn.close()
N = 1
for i in range(N):
test_impala(test_conf){code}
error info:
{code:java}
I0204 15:41:40.600821 168276 thrift-util.cc:123] TAcceptQueueServer: Caught
TException: invalid sasl status
I0204 15:46:40.600451 168276 thrift-util.cc:123] TAcceptQueueServer: Caught
TException: EAGAIN (timed out)
I0204 15:46:40.609858 168276 authentication.cc:268] Trying simple LDAP bind
for: uid=,dc=
I0204 15:46:40.729262 168276 authentication.cc:280] LDAP bind successful
I0204 15:46:40.729287 168276 authentication.cc:478] Successfully authenticated
client user ""{code}
When this error occurs, the connect request will hang for serveral minutes, and
all subsequent connect request including request from hue will hang too.
was:
I enable ldap user authentication for impalad. I run the following code to test
impalad stability, and I find when I run ten thousand times, the following
error will occur two times in impalad.INFO log file.
test code:
{code:java}
import impala.dbapi
test_conf =
{ 'host': '172.16.24.xx', 'port': 21050, 'user': '', 'password': 'x' }
def test_impala(conf):
conn = impala.dbapi.connect(**conf)
conn.close()
N = 1
for i in range(N):
test_impala(test_conf){code}
error info:
{code:java}
I0204 15:41:40.600821 168276 thrift-util.cc:123] TAcceptQueueServer: Caught
TException: invalid sasl status
I0204 15:46:40.600451 168276 thrift-util.cc:123] TAcceptQueueServer: Caught
TException: EAGAIN (timed out)
I0204 15:46:40.609858 168276 authentication.cc:268] Trying simple LDAP bind
for: uid=xxx,dc=
I0204 15:46:40.729262 168276 authentication.cc:280] LDAP bind successful
I0204 15:46:40.729287 168276 authentication.cc:478] Successfully authenticated
client user ""{code}
When this error occurs, the connect request will hang for serveral minutes, and
all subsequent connect request including request from hue will hang too.
> TAcceptQueueServer: Caught TException: invalid sasl status
> --
>
> Key: IMPALA-8159
> URL: https://issues.apache.org/jira/browse/IMPALA-8159
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
>Affects Versions: Impala 2.11.0
> Environment: python: 3.6.6
> impyla: 0.14.1
> thrift-sasl: https://github.com/cloudera/thrift_sasl.git
> impala: 2.11.0 from cdh5.14.2-1.cdh5.14.2.p0.3
>Reporter: Jinjie Zhang
>Priority: Major
>
> I enable ldap user authentication for impalad. I run the following code to
> test impalad stability, and I find when I run ten thousand times, the
> following error will occur two times in impalad.INFO log file.
> test code:
>
> {code:java}
> import impala.dbapi
> test_conf =
> { 'host': '172.16.24.xx', 'port': 21050, 'user': '', 'password': 'x' }
> def test_impala(conf):
> conn = impala.dbapi.connect(**conf)
> conn.close()
>
> N = 1
> for i in range(N):
> test_impala(test_conf){code}
>
> error info:
> {code:java}
> I0204 15:41:40.600821 168276 thrift-util.cc:123] TAcceptQueueServer: Caught
> TException: invalid sasl status
> I0204 15:46:40.600451 168276 thrift-util.cc:123] TAcceptQueueServer: Caught
> TException: EAGAIN (timed out)
> I0204 15:46:40.609858 168276 authentication.cc:268] Trying simple LDAP bind
> for: uid=,dc=
> I0204 15:46:40.729262 168276 authentication.cc:280] LDAP bind successful
> I0204 15:46:40.729287 168276 authentication.cc:478] Successfully
> authenticated client user ""{code}
> When this error occurs, the connect request will hang for serveral minutes,
> and all subsequent connect request including request from hue will hang too.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-8159) TAcceptQueueServer: Caught TException: invalid sasl status
[
https://issues.apache.org/jira/browse/IMPALA-8159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinjie Zhang updated IMPALA-8159:
-
Description:
I enable ldap user authentication for impalad. I run the following code to test
impalad stability, and I find when I run ten thousand times, the following
error will occur two times in impalad.INFO log file.
test code:
{code:java}
import impala.dbapi
test_conf =
{ 'host': '172.16.24.xx', 'port': 21050, 'user': '', 'password': 'x' }
def test_impala(conf):
conn = impala.dbapi.connect(**conf)
conn.close()
N = 1
for i in range(N):
test_impala(test_conf){code}
error info:
{code:java}
I0204 15:41:40.600821 168276 thrift-util.cc:123] TAcceptQueueServer: Caught
TException: invalid sasl status
I0204 15:46:40.600451 168276 thrift-util.cc:123] TAcceptQueueServer: Caught
TException: EAGAIN (timed out)
I0204 15:46:40.609858 168276 authentication.cc:268] Trying simple LDAP bind
for: uid=xxx,dc=
I0204 15:46:40.729262 168276 authentication.cc:280] LDAP bind successful
I0204 15:46:40.729287 168276 authentication.cc:478] Successfully authenticated
client user ""{code}
When this error occurs, the connect request will hang for serveral minutes, and
all subsequent connect request including request from hue will hang too.
was:
I enable ldap user authentication for impalad. I run the following code to test
impalad stability, and I find when I run ten thousand times, the following
error will occur two times in impalad.INFO log file.
test code:
{code:java}
import impala.dbapi
test_conf =
{ 'host': '172.16.24.xx', 'port': 21050, 'user': '', 'password': 'x' }
def test_impala(conf):
conn = impala.dbapi.connect(**conf)
conn.close()
N = 1
for i in range(N):
test_impala(test_conf){code}
error info:
{code:java}
I0204 15:41:40.600821 168276 thrift-util.cc:123] TAcceptQueueServer: Caught
TException: invalid sasl status{code}
When this error occurs, the connect request will hang for one minute or two
minutes, and all subsequent connect request including request from hue will
hang too.
> TAcceptQueueServer: Caught TException: invalid sasl status
> --
>
> Key: IMPALA-8159
> URL: https://issues.apache.org/jira/browse/IMPALA-8159
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
>Affects Versions: Impala 2.11.0
> Environment: python: 3.6.6
> impyla: 0.14.1
> thrift-sasl: https://github.com/cloudera/thrift_sasl.git
> impala: 2.11.0 from cdh5.14.2-1.cdh5.14.2.p0.3
>Reporter: Jinjie Zhang
>Priority: Major
>
> I enable ldap user authentication for impalad. I run the following code to
> test impalad stability, and I find when I run ten thousand times, the
> following error will occur two times in impalad.INFO log file.
> test code:
>
> {code:java}
> import impala.dbapi
> test_conf =
> { 'host': '172.16.24.xx', 'port': 21050, 'user': '', 'password': 'x' }
> def test_impala(conf):
> conn = impala.dbapi.connect(**conf)
> conn.close()
>
> N = 1
> for i in range(N):
> test_impala(test_conf){code}
>
> error info:
> {code:java}
> I0204 15:41:40.600821 168276 thrift-util.cc:123] TAcceptQueueServer: Caught
> TException: invalid sasl status
> I0204 15:46:40.600451 168276 thrift-util.cc:123] TAcceptQueueServer: Caught
> TException: EAGAIN (timed out)
> I0204 15:46:40.609858 168276 authentication.cc:268] Trying simple LDAP bind
> for: uid=xxx,dc=
> I0204 15:46:40.729262 168276 authentication.cc:280] LDAP bind successful
> I0204 15:46:40.729287 168276 authentication.cc:478] Successfully
> authenticated client user ""{code}
> When this error occurs, the connect request will hang for serveral minutes,
> and all subsequent connect request including request from hue will hang too.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-8159) TAcceptQueueServer: Caught TException: invalid sasl status
[
https://issues.apache.org/jira/browse/IMPALA-8159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinjie Zhang updated IMPALA-8159:
-
Environment:
python: 3.6.6
impyla: 0.14.1
thrift-sasl: https://github.com/cloudera/thrift_sasl.git
impala: 2.11.0 from cdh5.14.2-1.cdh5.14.2.p0.3
was:
python: 3.6.6
impyla: 0.14.1
thrift-sasl: https://github.com/cloudera/thrift_sasl.git
impala: 2.11.0 from cdh5.14.2-1.cdh5.14.2.p0.3
> TAcceptQueueServer: Caught TException: invalid sasl status
> --
>
> Key: IMPALA-8159
> URL: https://issues.apache.org/jira/browse/IMPALA-8159
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
>Affects Versions: Impala 2.11.0
> Environment: python: 3.6.6
> impyla: 0.14.1
> thrift-sasl: https://github.com/cloudera/thrift_sasl.git
> impala: 2.11.0 from cdh5.14.2-1.cdh5.14.2.p0.3
>Reporter: Jinjie Zhang
>Priority: Major
>
> I enable ldap user authentication for impalad. I run the following code to
> test impalad stability, and I find when I run ten thousand times, the
> following error will occur two times in impalad.INFO log file.
> test code:
>
> {code:java}
> import impala.dbapi
> test_conf =
> { 'host': '172.16.24.xx', 'port': 21050, 'user': '', 'password': 'x' }
> def test_impala(conf):
> conn = impala.dbapi.connect(**conf)
> conn.close()
>
> N = 1
> for i in range(N):
> test_impala(test_conf){code}
>
> error info:
> {code:java}
> I0204 15:41:40.600821 168276 thrift-util.cc:123] TAcceptQueueServer: Caught
> TException: invalid sasl status{code}
> When this error occurs, the connect request will hang for one minute or two
> minutes, and all subsequent connect request including request from hue will
> hang too.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-8159) TAcceptQueueServer: Caught TException: invalid sasl status
[
https://issues.apache.org/jira/browse/IMPALA-8159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinjie Zhang updated IMPALA-8159:
-
Description:
I enable ldap user authentication for impalad. I run the following code to test
impalad stability, and I find when I run ten thousand times, the following
error will occur two times in impalad.INFO log file.
test code:
import impala.dbapi
test_conf =
{ 'host': '172.16.24.xx', 'port': 21050, 'user': '', 'password': 'x' }
def test_impala(conf):
conn = impala.dbapi.connect(**conf)
conn.close()
N = 1
for i in range(N):
test_impala(test_conf)
error info:
```
I0204 15:41:40.600821 168276 thrift-util.cc:123] TAcceptQueueServer: Caught
TException: invalid sasl status
```
When this error occurs, the connect request will hang for one minute or two
minutes, and all subsequent connect request including request from hue will
hang too.
was:
I enable ldap user authentication for impalad. I run the following code to test
impalad stability, and I find when I run ten thousand times, the following
error will occur two times in impalad.INFO log file.
test code:
```python
import impala.dbapi
test_conf = {
'host': '172.16.24.xx',
'port': 21050,
'user': '',
'password': 'x'
}
def test_impala(conf):
conn = impala.dbapi.connect(**conf)
conn.close()
N = 1
for i in range(N):
test_impala(test_conf)
```
error info:
```
I0204 15:41:40.600821 168276 thrift-util.cc:123] TAcceptQueueServer: Caught
TException: invalid sasl status
```
When this error occurs, the connect request will hang for one minute or two
minutes, and all subsequent connect request including request from hue will
hang too.
> TAcceptQueueServer: Caught TException: invalid sasl status
> --
>
> Key: IMPALA-8159
> URL: https://issues.apache.org/jira/browse/IMPALA-8159
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
>Affects Versions: Impala 2.11.0
> Environment: python: 3.6.6
> impyla: 0.14.1
> thrift-sasl: https://github.com/cloudera/thrift_sasl.git
> impala: 2.11.0 from cdh5.14.2-1.cdh5.14.2.p0.3
>Reporter: Jinjie Zhang
>Priority: Major
>
> I enable ldap user authentication for impalad. I run the following code to
> test impalad stability, and I find when I run ten thousand times, the
> following error will occur two times in impalad.INFO log file.
> test code:
>
> import impala.dbapi
> test_conf =
> { 'host': '172.16.24.xx', 'port': 21050, 'user': '', 'password': 'x' }
> def test_impala(conf):
> conn = impala.dbapi.connect(**conf)
> conn.close()
>
> N = 1
> for i in range(N):
> test_impala(test_conf)
>
> error info:
> ```
> I0204 15:41:40.600821 168276 thrift-util.cc:123] TAcceptQueueServer: Caught
> TException: invalid sasl status
> ```
> When this error occurs, the connect request will hang for one minute or two
> minutes, and all subsequent connect request including request from hue will
> hang too.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Created] (IMPALA-8159) TAcceptQueueServer: Caught TException: invalid sasl status
Jinjie Zhang created IMPALA-8159:
Summary: TAcceptQueueServer: Caught TException: invalid sasl status
Key: IMPALA-8159
URL: https://issues.apache.org/jira/browse/IMPALA-8159
Project: IMPALA
Issue Type: Bug
Components: Backend
Affects Versions: Impala 2.11.0
Environment: python: 3.6.6
impyla: 0.14.1
thrift-sasl: https://github.com/cloudera/thrift_sasl.git
impala: 2.11.0 from cdh5.14.2-1.cdh5.14.2.p0.3
Reporter: Jinjie Zhang
I enable ldap user authentication for impalad. I run the following code to test
impalad stability, and I find when I run ten thousand times, the following
error will occur two times in impalad.INFO log file.
test code:
```python
import impala.dbapi
test_conf = {
'host': '172.16.24.xx',
'port': 21050,
'user': '',
'password': 'x'
}
def test_impala(conf):
conn = impala.dbapi.connect(**conf)
conn.close()
N = 1
for i in range(N):
test_impala(test_conf)
```
error info:
```
I0204 15:41:40.600821 168276 thrift-util.cc:123] TAcceptQueueServer: Caught
TException: invalid sasl status
```
When this error occurs, the connect request will hang for one minute or two
minutes, and all subsequent connect request including request from hue will
hang too.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
