[jira] [Commented] (IMPALA-7388) JNI THROW_IF_ERROR macros use local scope variables which likely conflict
[
https://issues.apache.org/jira/browse/IMPALA-7388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16579252#comment-16579252
]
ASF subversion and git services commented on IMPALA-7388:
-
Commit ea615d1d8026dbe1cda3f5c2b048d210b2df435b in impala's branch
refs/heads/master from [~tlipcon]
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=ea615d1 ]
IMPALA-7388. Fix issues in and optimize various Status macros
Prior to this patch, the JNI THROW_IF macros used a variable 'status' in
local scope to hold the result of the statement whose status is to be
checked. This could cause problems if there is another variable 'status'
in the external scope, as the inner scope would shadow the outer. For
example:
Status status = foo();
THROW_IF_ERROR(status, ...);
... would actually end up resulting in a macro expansion like:
do {
Status status = status;
...
} while (false);
Suprisingly, such code is legal C++ and ends up calling the Status copy
constructor with an uninitialized version of itself as the argument. gcc
doesn't seem to emit a warning for this construct, though clang does
emit "variable 'status' is uninitialized when used within its own
initialization".
If such code is emitted, we'll get undefined behavior and most likely
not end up throwing an error even if status is not OK.
The fix is simple: use a less-likely-to-conflict variable name _status
in the macro. This also fixes other macros that previously used
__status__ to use _status to align with the fact that __*__ style
keywords are reserved by the C++ standard.
Additionally, this patch changes some other similar macros to use const
references instead of creating new variables. On the surface, it might
look wrong to assign a const reference to a temporary such as the result
of a function call. However, C++ explicitly allows this and ensures that
the lifetime of the temporary is extended to the lifetime of the
captured reference, making it safe[1]. This acts as a small optimization
since the RETURN_IF_ERROR macros won't call their copy-constructor an
extra time.
[1]
https://herbsutter.com/2008/01/01/gotw-88-a-candidate-for-the-most-important-const/
Change-Id: I3d62c99bbd83cc290f5992077258af156eaa6330
Reviewed-on: http://gerrit.cloudera.org:8080/11153
Tested-by: Impala Public Jenkins
Reviewed-by: Todd Lipcon
> JNI THROW_IF_ERROR macros use local scope variables which likely conflict
> -
>
> Key: IMPALA-7388
> URL: https://issues.apache.org/jira/browse/IMPALA-7388
> Project: IMPALA
> Issue Type: Bug
>Reporter: Todd Lipcon
>Assignee: Todd Lipcon
>Priority: Major
> Fix For: Impala 3.1.0
>
>
> The THROW_IF_ERROR macros all use a locally scoped variable "status". If
> they're called with a pattern like:
> {code:java}
> Status status = foo();
> THROW_IF_ERROR(status, ...){code}
>
> then the status variable inside the macro ends up being assigned to itself
> instead of the outer-scope variable. This makes it not throw or return, which
> is quite surprising.
--
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-7403) AnalyticEvalNode does not manage BufferedTupleStream memory correctly
[
https://issues.apache.org/jira/browse/IMPALA-7403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16579251#comment-16579251
]
ASF subversion and git services commented on IMPALA-7403:
-
Commit 884fcf81b8f0df949ee615c6b99694c01500da08 in impala's branch
refs/heads/master from [~tarmstr...@cloudera.com]
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=884fcf8 ]
Analytic mem mgmt cleanup
Following on from IMPALA-7403, clean up some of memory management
in AnalyticEvalNode.
Remove an unnecessary MemPool and avoid reallocating tuples
unnecessarily in Reset(). Also switch to inline initialization
of members.
Testing:
Ran exhaustive tests
Change-Id: Id16beb2d0b9d4315f52dd45203649252c0eb06b0
Reviewed-on: http://gerrit.cloudera.org:8080/11203
Reviewed-by: Impala Public Jenkins
Tested-by: Impala Public Jenkins
> AnalyticEvalNode does not manage BufferedTupleStream memory correctly
> -
>
> Key: IMPALA-7403
> URL: https://issues.apache.org/jira/browse/IMPALA-7403
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
>Affects Versions: Impala 2.5.0, Impala 2.6.0, Impala 2.7.0, Impala 2.8.0,
> Impala 2.9.0, Impala 2.10.0, Impala 2.11.0, Impala 3.0, Impala 2.12.0, Impala
> 3.1.0
>Reporter: Michael Brown
>Assignee: Tim Armstrong
>Priority: Blocker
> Labels: correctness, crash, query_generator
> Fix For: Impala 3.1.0
>
>
> The query generator has discovered a crash. I took one of the crashing
> queries and simplified it down as far as I could go. I searched for existing
> bugs with the same dcheck and didn't strictly see anything but I know there
> are other bugs right now and this may end up being a dupe.
> {noformat}
> reservation-tracker.cc:428] Check failed: used_reservation_ +
> child_reservations_ <= reservation_ (6291456 vs. 4194304)
> {noformat}
> {noformat}
> #6 0x0437961e in google::LogMessageFatal::~LogMessageFatal() ()
> #7 0x020636c6 in impala::ReservationTracker::CheckConsistency()
> const (this=0xe08da58) at
> /home/mikeb/Impala/be/src/runtime/bufferpool/reservation-tracker.cc:428
> #8 0x02062888 in
> impala::ReservationTracker::TransferReservationTo(impala::ReservationTracker*,
> long) (this=0xe08da58, other=0x11cae530, bytes=2097152) at
> /home/mikeb/Impala/be/src/runtime/bufferpool/reservation-tracker.cc:358
> #9 0x02057b10 in
> impala::BufferPool::ClientHandle::SaveReservation(impala::BufferPool::SubReservation*,
> long) (this=0xbf26190, dst=0xcfd40e8, bytes=2097152) at
> /home/mikeb/Impala/be/src/runtime/bufferpool/buffer-pool.cc:347
> #10 0x0318f209 in impala::BufferedTupleStream::NextReadPage()
> (this=0xcfd4000) at
> /home/mikeb/Impala/be/src/runtime/buffered-tuple-stream.cc:541
> #11 0x03195037 in impala::BufferedTupleStream::GetNextInternal false>(impala::RowBatch*, bool*, std::vector std::allocator >*) (this=0xcfd4000, batch=0x7efff313bc90,
> eos=0x7efff313c12f, flat_rows=0x0)
> at /home/mikeb/Impala/be/src/runtime/buffered-tuple-stream.cc:727
> #12 0x03192bf1 in
> impala::BufferedTupleStream::GetNextInternal(impala::RowBatch*, bool*,
> std::vector >*)
> (this=0xcfd4000, batch=0x7efff313bc90, eos=0x7efff313c12f, flat_rows=0x0)
> at /home/mikeb/Impala/be/src/runtime/buffered-tuple-stream.cc:698
> #13 0x0319035a in
> impala::BufferedTupleStream::GetNext(impala::RowBatch*, bool*)
> (this=0xcfd4000, batch=0x7efff313bc90, eos=0x7efff313c12f) at
> /home/mikeb/Impala/be/src/runtime/buffered-tuple-stream.cc:684
> #14 0x02e8ca0b in
> impala::AnalyticEvalNode::GetNextOutputBatch(impala::RuntimeState*,
> impala::RowBatch*, bool*) (this=0xbf26000, state=0xe575d40,
> output_batch=0xb98a5a0, eos=0x7efff313c12f)
> at /home/mikeb/Impala/be/src/exec/analytic-eval-node.cc:719
> #15 0x02e8dfe7 in
> impala::AnalyticEvalNode::GetNext(impala::RuntimeState*, impala::RowBatch*,
> bool*) (this=0xbf26000, state=0xe575d40, row_batch=0xb98a5a0, eos=0xbf27fd8)
> at /home/mikeb/Impala/be/src/exec/analytic-eval-node.cc:789
> #16 0x02e8b36a in
> impala::AnalyticEvalNode::ProcessChildBatches(impala::RuntimeState*)
> (this=0xbf27c00, state=0xe575d40) at
> /home/mikeb/Impala/be/src/exec/analytic-eval-node.cc:602
> #17 0x02e8df37 in
> impala::AnalyticEvalNode::GetNext(impala::RuntimeState*, impala::RowBatch*,
> bool*) (this=0xbf27c00, state=0xe575d40, row_batch=0xe904e40,
> eos=0x7efff313c5cf) at
> /home/mikeb/Impala/be/src/exec/analytic-eval-node.cc:786
> #18 0x01df28b8 in impala::FragmentInstanceState::ExecInternal()
> (this=0xbf39a00) at
> /home/mikeb/Impala/be/src/runtime/fragment-instance-state.cc:286
> #19 0x01defd35 in impala::FragmentInstanceState::Exec()
>
[jira] [Resolved] (IMPALA-7388) JNI THROW_IF_ERROR macros use local scope variables which likely conflict
[
https://issues.apache.org/jira/browse/IMPALA-7388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon resolved IMPALA-7388.
-
Resolution: Fixed
Fix Version/s: Impala 3.1.0
> JNI THROW_IF_ERROR macros use local scope variables which likely conflict
> -
>
> Key: IMPALA-7388
> URL: https://issues.apache.org/jira/browse/IMPALA-7388
> Project: IMPALA
> Issue Type: Bug
>Reporter: Todd Lipcon
>Assignee: Todd Lipcon
>Priority: Major
> Fix For: Impala 3.1.0
>
>
> The THROW_IF_ERROR macros all use a locally scoped variable "status". If
> they're called with a pattern like:
> {code:java}
> Status status = foo();
> THROW_IF_ERROR(status, ...){code}
>
> then the status variable inside the macro ends up being assigned to itself
> instead of the outer-scope variable. This makes it not throw or return, which
> is quite surprising.
--
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-7388) JNI THROW_IF_ERROR macros use local scope variables which likely conflict
[
https://issues.apache.org/jira/browse/IMPALA-7388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon resolved IMPALA-7388.
-
Resolution: Fixed
Fix Version/s: Impala 3.1.0
> JNI THROW_IF_ERROR macros use local scope variables which likely conflict
> -
>
> Key: IMPALA-7388
> URL: https://issues.apache.org/jira/browse/IMPALA-7388
> Project: IMPALA
> Issue Type: Bug
>Reporter: Todd Lipcon
>Assignee: Todd Lipcon
>Priority: Major
> Fix For: Impala 3.1.0
>
>
> The THROW_IF_ERROR macros all use a locally scoped variable "status". If
> they're called with a pattern like:
> {code:java}
> Status status = foo();
> THROW_IF_ERROR(status, ...){code}
>
> then the status variable inside the macro ends up being assigned to itself
> instead of the outer-scope variable. This makes it not throw or return, which
> is quite surprising.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IMPALA-7423) NoSuchMethodError when starting Sentry in the minicluster
[
https://issues.apache.org/jira/browse/IMPALA-7423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fredy Wijaya resolved IMPALA-7423.
--
Resolution: Fixed
Fix Version/s: Impala 3.1.0
> NoSuchMethodError when starting Sentry in the minicluster
> -
>
> Key: IMPALA-7423
> URL: https://issues.apache.org/jira/browse/IMPALA-7423
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
>Affects Versions: Impala 3.0
>Reporter: Fredy Wijaya
>Assignee: Fredy Wijaya
>Priority: Major
> Labels: flaky-build
> Fix For: Impala 3.1.0
>
>
> {noformat}
> ERROR StatusLogger No log4j2 configuration file found. Using default
> configuration: logging only errors to the console. Set system property
> 'org.apache.logging.log4j.simplelog.StatusLogger.level' to TRACE to show
> Log4j2 internal initialization logging.
> Exception in thread "main" java.lang.NoSuchMethodError:
> org.apache.sentry.api.service.thrift.SentryPolicyServiceClientDefaultImpl.(Lorg/apache/hadoop/conf/Configuration;Lsentry/org/apache/sentry/core/common/transport/SentryTransportPool;)V
> at
> org.apache.sentry.service.thrift.SentryServiceClientFactory.create(SentryServiceClientFactory.java:90)
> at
> org.apache.sentry.service.thrift.SentryServiceClientFactory.create(SentryServiceClientFactory.java:68)
> at
> org.apache.impala.util.SentryPolicyService$SentryServiceClient.createClient(SentryPolicyService.java:91)
> at
> org.apache.impala.util.SentryPolicyService$SentryServiceClient.(SentryPolicyService.java:64)
> at
> org.apache.impala.util.SentryPolicyService.listAllRoles(SentryPolicyService.java:395)
> at
> org.apache.impala.testutil.SentryServicePinger.main(SentryServicePinger.java:81)
> Error in /home/impdev/Impala/testdata/bin/run-sentry-service.sh at line 39:
> "$JAVA" -cp $CLASSPATH org.apache.impala.testutil.SentryServicePinger \
> Error in /home/impdev/Impala/testdata/bin/run-all.sh at line 61: tee
> ${IMPALA_CLUSTER_LOGS_DIR}/run-sentry-service.log
> {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] [Resolved] (IMPALA-7423) NoSuchMethodError when starting Sentry in the minicluster
[
https://issues.apache.org/jira/browse/IMPALA-7423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fredy Wijaya resolved IMPALA-7423.
--
Resolution: Fixed
Fix Version/s: Impala 3.1.0
> NoSuchMethodError when starting Sentry in the minicluster
> -
>
> Key: IMPALA-7423
> URL: https://issues.apache.org/jira/browse/IMPALA-7423
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
>Affects Versions: Impala 3.0
>Reporter: Fredy Wijaya
>Assignee: Fredy Wijaya
>Priority: Major
> Labels: flaky-build
> Fix For: Impala 3.1.0
>
>
> {noformat}
> ERROR StatusLogger No log4j2 configuration file found. Using default
> configuration: logging only errors to the console. Set system property
> 'org.apache.logging.log4j.simplelog.StatusLogger.level' to TRACE to show
> Log4j2 internal initialization logging.
> Exception in thread "main" java.lang.NoSuchMethodError:
> org.apache.sentry.api.service.thrift.SentryPolicyServiceClientDefaultImpl.(Lorg/apache/hadoop/conf/Configuration;Lsentry/org/apache/sentry/core/common/transport/SentryTransportPool;)V
> at
> org.apache.sentry.service.thrift.SentryServiceClientFactory.create(SentryServiceClientFactory.java:90)
> at
> org.apache.sentry.service.thrift.SentryServiceClientFactory.create(SentryServiceClientFactory.java:68)
> at
> org.apache.impala.util.SentryPolicyService$SentryServiceClient.createClient(SentryPolicyService.java:91)
> at
> org.apache.impala.util.SentryPolicyService$SentryServiceClient.(SentryPolicyService.java:64)
> at
> org.apache.impala.util.SentryPolicyService.listAllRoles(SentryPolicyService.java:395)
> at
> org.apache.impala.testutil.SentryServicePinger.main(SentryServicePinger.java:81)
> Error in /home/impdev/Impala/testdata/bin/run-sentry-service.sh at line 39:
> "$JAVA" -cp $CLASSPATH org.apache.impala.testutil.SentryServicePinger \
> Error in /home/impdev/Impala/testdata/bin/run-all.sh at line 61: tee
> ${IMPALA_CLUSTER_LOGS_DIR}/run-sentry-service.log
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IMPALA-7347) Assertion Failure - test_show_create_table
[
https://issues.apache.org/jira/browse/IMPALA-7347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tianyi Wang resolved IMPALA-7347.
-
Resolution: Fixed
> Assertion Failure - test_show_create_table
> ---
>
> Key: IMPALA-7347
> URL: https://issues.apache.org/jira/browse/IMPALA-7347
> Project: IMPALA
> Issue Type: Bug
>Affects Versions: Impala 3.1.0
>Reporter: nithya
>Assignee: Tianyi Wang
>Priority: Blocker
> Labels: build-failure
> Fix For: Impala 3.1.0
>
>
> test_show_create_table in metadata/test_show_create_table.py is failing with
> the following assertion error
> {noformat}
> metadata/test_show_create_table.py:58: in test_show_create_table
> unique_database)
> metadata/test_show_create_table.py:106: in __run_show_create_table_test_case
> self.__compare_result(expected_result, create_table_result)
> metadata/test_show_create_table.py:134: in __compare_result
> assert expected_tbl_props == actual_tbl_props
> E assert {} == {'numFilesErasureCoded': '0'}
> E Right contains more items:
> E {'numFilesErasureCoded': '0'}
> E Use -v to get the full diff
> {noformat}
>
> It appears that table property "numFilesErasureCoded" is showing up in table
> properties.
> Either the test needs updating or a bug.
>
> {code}
> h3. Error Message
> metadata/test_show_create_table.py:58: in test_show_create_table
> unique_database) metadata/test_show_create_table.py:106: in
> __run_show_create_table_test_case self.__compare_result(expected_result,
> create_table_result) metadata/test_show_create_table.py:134: in
> __compare_result assert expected_tbl_props == actual_tbl_props E assert {} ==
> \{'numFilesErasureCoded': '0'} E Right contains more items: E
> \{'numFilesErasureCoded': '0'} E Use -v to get the full diff
> {code}
>
> ---
> {code}
> h3. Standard Error
> -- connecting to: localhost:21000 SET sync_ddl=False; -- executing against
> localhost:21000 DROP DATABASE IF EXISTS `test_show_create_table_f1598d0b`
> CASCADE; SET sync_ddl=False; -- executing against localhost:21000 CREATE
> DATABASE `test_show_create_table_f1598d0b`; MainThread: Created database
> "test_show_create_table_f1598d0b" for test ID
> "metadata/test_show_create_table.py::TestShowCreateTable::()::test_show_create_table[table_format:
> text/none]" -- executing against localhost:21000 CREATE TABLE
> test_show_create_table_f1598d0b.test1 ( id INT ) STORED AS TEXTFILE; --
> executing against localhost:21000 show create table
> test_show_create_table_f1598d0b.test1; -- executing against localhost:21000
> drop table test_show_create_table_f1598d0b.test1; -- executing against
> localhost:21000 CREATE TABLE test_show_create_table_f1598d0b.test1 (id INT)
> STORED AS TEXTFILE LOCATION
> 'hdfs://localhost:20500/test-warehouse/test_show_create_table_f1598d0b.db/test1';
> -- executing against localhost:21000 show create table
> test_show_create_table_f1598d0b.test1; -- executing against localhost:21000
> drop table test_show_create_table_f1598d0b.test1; -- executing against
> localhost:21000 CREATE TABLE test_show_create_table_f1598d0b.test2 ( year
> INT, month INT, id INT COMMENT 'Add a comment', bool_col BOOLEAN, tinyint_col
> TINYINT, smallint_col SMALLINT, int_col INT, bigint_col BIGINT, float_col
> FLOAT, double_col DOUBLE, date_string_col STRING, string_col STRING,
> timestamp_col TIMESTAMP ) STORED AS TEXTFILE; -- executing against
> localhost:21000 show create table test_show_create_table_f1598d0b.test2; --
> executing against localhost:21000 drop table
> test_show_create_table_f1598d0b.test2; -- executing against localhost:21000
> CREATE TABLE test_show_create_table_f1598d0b.test2 (year INT, month INT, id
> INT COMMENT 'Add a comment', bool_col BOOLEAN, tinyint_col TINYINT,
> smallint_col SMALLINT, int_col INT, bigint_col BIGINT, float_col FLOAT,
> double_col DOUBLE, date_string_col STRING, string_col STRING, timestamp_col
> TIMESTAMP) STORED AS TEXTFILE LOCATION
> 'hdfs://localhost:20500/test-warehouse/test_show_create_table_f1598d0b.db/test2';
> -- executing against localhost:21000 show create table
> test_show_create_table_f1598d0b.test2; -- executing against localhost:21000
> drop table test_show_create_table_f1598d0b.test2; -- executing against
> localhost:21000 CREATE TABLE test_show_create_table_f1598d0b.test3 ( year
> INT, month INT, id INT COMMENT 'Add a comment', bool_col BOOLEAN, tinyint_col
> TINYINT, smallint_col SMALLINT, int_col INT, bigint_col BIGINT, float_col
> FLOAT, double_col DOUBLE, date_string_col STRING, string_col STRING,
> timestamp_col TIMESTAMP ) PARTITIONED BY ( x INT, y INT, a BOOLEAN ) COMMENT
> 'This is a test' STORED AS TEXTFILE; -- executing against localhost:21000
> show create table
[jira] [Resolved] (IMPALA-7347) Assertion Failure - test_show_create_table
[
https://issues.apache.org/jira/browse/IMPALA-7347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tianyi Wang resolved IMPALA-7347.
-
Resolution: Fixed
> Assertion Failure - test_show_create_table
> ---
>
> Key: IMPALA-7347
> URL: https://issues.apache.org/jira/browse/IMPALA-7347
> Project: IMPALA
> Issue Type: Bug
>Affects Versions: Impala 3.1.0
>Reporter: nithya
>Assignee: Tianyi Wang
>Priority: Blocker
> Labels: build-failure
> Fix For: Impala 3.1.0
>
>
> test_show_create_table in metadata/test_show_create_table.py is failing with
> the following assertion error
> {noformat}
> metadata/test_show_create_table.py:58: in test_show_create_table
> unique_database)
> metadata/test_show_create_table.py:106: in __run_show_create_table_test_case
> self.__compare_result(expected_result, create_table_result)
> metadata/test_show_create_table.py:134: in __compare_result
> assert expected_tbl_props == actual_tbl_props
> E assert {} == {'numFilesErasureCoded': '0'}
> E Right contains more items:
> E {'numFilesErasureCoded': '0'}
> E Use -v to get the full diff
> {noformat}
>
> It appears that table property "numFilesErasureCoded" is showing up in table
> properties.
> Either the test needs updating or a bug.
>
> {code}
> h3. Error Message
> metadata/test_show_create_table.py:58: in test_show_create_table
> unique_database) metadata/test_show_create_table.py:106: in
> __run_show_create_table_test_case self.__compare_result(expected_result,
> create_table_result) metadata/test_show_create_table.py:134: in
> __compare_result assert expected_tbl_props == actual_tbl_props E assert {} ==
> \{'numFilesErasureCoded': '0'} E Right contains more items: E
> \{'numFilesErasureCoded': '0'} E Use -v to get the full diff
> {code}
>
> ---
> {code}
> h3. Standard Error
> -- connecting to: localhost:21000 SET sync_ddl=False; -- executing against
> localhost:21000 DROP DATABASE IF EXISTS `test_show_create_table_f1598d0b`
> CASCADE; SET sync_ddl=False; -- executing against localhost:21000 CREATE
> DATABASE `test_show_create_table_f1598d0b`; MainThread: Created database
> "test_show_create_table_f1598d0b" for test ID
> "metadata/test_show_create_table.py::TestShowCreateTable::()::test_show_create_table[table_format:
> text/none]" -- executing against localhost:21000 CREATE TABLE
> test_show_create_table_f1598d0b.test1 ( id INT ) STORED AS TEXTFILE; --
> executing against localhost:21000 show create table
> test_show_create_table_f1598d0b.test1; -- executing against localhost:21000
> drop table test_show_create_table_f1598d0b.test1; -- executing against
> localhost:21000 CREATE TABLE test_show_create_table_f1598d0b.test1 (id INT)
> STORED AS TEXTFILE LOCATION
> 'hdfs://localhost:20500/test-warehouse/test_show_create_table_f1598d0b.db/test1';
> -- executing against localhost:21000 show create table
> test_show_create_table_f1598d0b.test1; -- executing against localhost:21000
> drop table test_show_create_table_f1598d0b.test1; -- executing against
> localhost:21000 CREATE TABLE test_show_create_table_f1598d0b.test2 ( year
> INT, month INT, id INT COMMENT 'Add a comment', bool_col BOOLEAN, tinyint_col
> TINYINT, smallint_col SMALLINT, int_col INT, bigint_col BIGINT, float_col
> FLOAT, double_col DOUBLE, date_string_col STRING, string_col STRING,
> timestamp_col TIMESTAMP ) STORED AS TEXTFILE; -- executing against
> localhost:21000 show create table test_show_create_table_f1598d0b.test2; --
> executing against localhost:21000 drop table
> test_show_create_table_f1598d0b.test2; -- executing against localhost:21000
> CREATE TABLE test_show_create_table_f1598d0b.test2 (year INT, month INT, id
> INT COMMENT 'Add a comment', bool_col BOOLEAN, tinyint_col TINYINT,
> smallint_col SMALLINT, int_col INT, bigint_col BIGINT, float_col FLOAT,
> double_col DOUBLE, date_string_col STRING, string_col STRING, timestamp_col
> TIMESTAMP) STORED AS TEXTFILE LOCATION
> 'hdfs://localhost:20500/test-warehouse/test_show_create_table_f1598d0b.db/test2';
> -- executing against localhost:21000 show create table
> test_show_create_table_f1598d0b.test2; -- executing against localhost:21000
> drop table test_show_create_table_f1598d0b.test2; -- executing against
> localhost:21000 CREATE TABLE test_show_create_table_f1598d0b.test3 ( year
> INT, month INT, id INT COMMENT 'Add a comment', bool_col BOOLEAN, tinyint_col
> TINYINT, smallint_col SMALLINT, int_col INT, bigint_col BIGINT, float_col
> FLOAT, double_col DOUBLE, date_string_col STRING, string_col STRING,
> timestamp_col TIMESTAMP ) PARTITIONED BY ( x INT, y INT, a BOOLEAN ) COMMENT
> 'This is a test' STORED AS TEXTFILE; -- executing against localhost:21000
> show create table
[jira] [Resolved] (IMPALA-7419) NullPointerException in SimplifyConditionalsRule
[
https://issues.apache.org/jira/browse/IMPALA-7419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Tauber-Marshall resolved IMPALA-7419.
Resolution: Fixed
Fix Version/s: Impala 3.1.0
> NullPointerException in SimplifyConditionalsRule
>
>
> Key: IMPALA-7419
> URL: https://issues.apache.org/jira/browse/IMPALA-7419
> Project: IMPALA
> Issue Type: Bug
> Components: Frontend
>Affects Versions: Impala 3.1.0
>Reporter: Thomas Tauber-Marshall
>Assignee: Thomas Tauber-Marshall
>Priority: Critical
> Fix For: Impala 3.1.0
>
>
> Found by the query generator:
> {noformat}
> SELECT
> COALESCE((-311) * (NULL), MIN(DISTINCT tinyint_col), 42)
> FROM functional.alltypes
> {noformat}
> {noformat}
> java.lang.NullPointerException
> at
> com.google.common.base.Preconditions.checkNotNull(Preconditions.java:187)
> at
> org.apache.impala.analysis.FunctionCallExpr.isAggregateFunction(FunctionCallExpr.java:238)
>
> at org.apache.impala.analysis.Expr$1.apply(Expr.java:100)
> at org.apache.impala.analysis.Expr$1.apply(Expr.java:97)
> at org.apache.impala.common.TreeNode.contains(TreeNode.java:162)
> at
> org.apache.impala.rewrite.SimplifyConditionalsRule.apply(SimplifyConditionalsRule.java:84)
>
> at
> org.apache.impala.rewrite.ExprRewriter.applyRuleBottomUp(ExprRewriter.java:85)
>
> at
> org.apache.impala.rewrite.ExprRewriter.applyRuleRepeatedly(ExprRewriter.java:71)
>
> at
> org.apache.impala.rewrite.ExprRewriter.rewrite(ExprRewriter.java:55)
> at
> org.apache.impala.analysis.SelectList.rewriteExprs(SelectList.java:97)
> at
> org.apache.impala.analysis.SelectStmt.rewriteExprs(SelectStmt.java:892)
> at
> org.apache.impala.analysis.AnalysisContext.analyze(AnalysisContext.java:446)
> at
> org.apache.impala.analysis.AnalysisContext.analyzeAndAuthorize(AnalysisContext.java:408)
>
> at
> org.apache.impala.service.Frontend.createExecRequest(Frontend.java:1035)
> at
> org.apache.impala.service.JniFrontend.createExecRequest(JniFrontend.java:165)
> {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] [Resolved] (IMPALA-7419) NullPointerException in SimplifyConditionalsRule
[
https://issues.apache.org/jira/browse/IMPALA-7419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Tauber-Marshall resolved IMPALA-7419.
Resolution: Fixed
Fix Version/s: Impala 3.1.0
> NullPointerException in SimplifyConditionalsRule
>
>
> Key: IMPALA-7419
> URL: https://issues.apache.org/jira/browse/IMPALA-7419
> Project: IMPALA
> Issue Type: Bug
> Components: Frontend
>Affects Versions: Impala 3.1.0
>Reporter: Thomas Tauber-Marshall
>Assignee: Thomas Tauber-Marshall
>Priority: Critical
> Fix For: Impala 3.1.0
>
>
> Found by the query generator:
> {noformat}
> SELECT
> COALESCE((-311) * (NULL), MIN(DISTINCT tinyint_col), 42)
> FROM functional.alltypes
> {noformat}
> {noformat}
> java.lang.NullPointerException
> at
> com.google.common.base.Preconditions.checkNotNull(Preconditions.java:187)
> at
> org.apache.impala.analysis.FunctionCallExpr.isAggregateFunction(FunctionCallExpr.java:238)
>
> at org.apache.impala.analysis.Expr$1.apply(Expr.java:100)
> at org.apache.impala.analysis.Expr$1.apply(Expr.java:97)
> at org.apache.impala.common.TreeNode.contains(TreeNode.java:162)
> at
> org.apache.impala.rewrite.SimplifyConditionalsRule.apply(SimplifyConditionalsRule.java:84)
>
> at
> org.apache.impala.rewrite.ExprRewriter.applyRuleBottomUp(ExprRewriter.java:85)
>
> at
> org.apache.impala.rewrite.ExprRewriter.applyRuleRepeatedly(ExprRewriter.java:71)
>
> at
> org.apache.impala.rewrite.ExprRewriter.rewrite(ExprRewriter.java:55)
> at
> org.apache.impala.analysis.SelectList.rewriteExprs(SelectList.java:97)
> at
> org.apache.impala.analysis.SelectStmt.rewriteExprs(SelectStmt.java:892)
> at
> org.apache.impala.analysis.AnalysisContext.analyze(AnalysisContext.java:446)
> at
> org.apache.impala.analysis.AnalysisContext.analyzeAndAuthorize(AnalysisContext.java:408)
>
> at
> org.apache.impala.service.Frontend.createExecRequest(Frontend.java:1035)
> at
> org.apache.impala.service.JniFrontend.createExecRequest(JniFrontend.java:165)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IMPALA-7418) test_udf_errors - returns Cancelled instead of actual error
[
https://issues.apache.org/jira/browse/IMPALA-7418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16579116#comment-16579116
]
ASF subversion and git services commented on IMPALA-7418:
-
Commit 2e5df138aaf4354fd4ada69b627842c34fef2e05 in impala's branch
refs/heads/master from poojanilangekar
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=2e5df13 ]
IMPALA-7335/IMPALA-7418: Add logs to HdfsScanNode to debug the issues
IMPALA-7335 and IMPALA-7418 are failing some builds on jenkins.
However, there is no deterministic method to reproduce them
locally and hence it is difficult to figure out the cause of the
failure. From the existing logs, it appears that the status
generated by HdfsScanNode::ProcessSplit() is lost. This log
would help determine the condition when the failures occur.
Change-Id: I68698c90031edc6ee8c31e9ce3d52dade9d8f6f1
Reviewed-on: http://gerrit.cloudera.org:8080/11174
Reviewed-by: Bikramjeet Vig
Tested-by: Impala Public Jenkins
> test_udf_errors - returns Cancelled instead of actual error
> ---
>
> Key: IMPALA-7418
> URL: https://issues.apache.org/jira/browse/IMPALA-7418
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
>Affects Versions: Impala 3.1.0
>Reporter: Tim Armstrong
>Assignee: Pooja Nilangekar
>Priority: Blocker
> Labels: broken-build
>
> {noformat}
> query_test.test_udfs.TestUdfExecution.test_udf_errors[exec_option:
> {'disable_codegen_rows_threshold': 0, 'disable_codegen': True,
> 'exec_single_node_rows_threshold': 0, 'enable_expr_rewrites': True} |
> table_format: text/none] (from pytest)
> Failing for the past 1 build (Since Failed#2925 )
> Took 19 sec.
> add description
> Error Message
> query_test/test_udfs.py:415: in test_udf_errors
> self.run_test_case('QueryTest/udf-errors', vector, use_db=unique_database)
> common/impala_test_suite.py:412: in run_test_case
> self.__verify_exceptions(test_section['CATCH'], str(e), use_db)
> common/impala_test_suite.py:290: in __verify_exceptions (expected_str,
> actual_str) E AssertionError: Unexpected exception string. Expected:
> BadExpr2 prepare error E Not found in actual: ImpalaBeeswaxException: Query
> aborted:Cancelled
> Stacktrace
> query_test/test_udfs.py:415: in test_udf_errors
> self.run_test_case('QueryTest/udf-errors', vector, use_db=unique_database)
> common/impala_test_suite.py:412: in run_test_case
> self.__verify_exceptions(test_section['CATCH'], str(e), use_db)
> common/impala_test_suite.py:290: in __verify_exceptions
> (expected_str, actual_str)
> E AssertionError: Unexpected exception string. Expected: BadExpr2 prepare
> error
> E Not found in actual: ImpalaBeeswaxException: Query aborted:Cancelled
> Standard Error
> SET sync_ddl=False;
> -- executing against localhost:21000
> DROP DATABASE IF EXISTS `test_udf_errors_be4e0293` CASCADE;
> MainThread: Started query bd4790b45c20640d:9c62ffba
> SET sync_ddl=False;
> -- executing against localhost:21000
> CREATE DATABASE `test_udf_errors_be4e0293`;
> MainThread: Started query 474595a3ecba67bd:7a14c84
> MainThread: Created database "test_udf_errors_be4e0293" for test ID
> "query_test/test_udfs.py::TestUdfExecution::()::test_udf_errors[exec_option:
> {'disable_codegen_rows_threshold': 0, 'disable_codegen': True,
> 'exec_single_node_rows_threshold': 0, 'enable_expr_rewrites': True} |
> table_format: text/none]"
> -- executing against localhost:21000
> use test_udf_errors_be4e0293;
> MainThread: Started query 264b0cd09d289c09:cc5dafed
> SET disable_codegen_rows_threshold=0;
> SET disable_codegen=True;
> SET exec_single_node_rows_threshold=0;
> SET enable_expr_rewrites=True;
> -- executing against localhost:21000
> create function if not exists hive_pi() returns double
> location '/test-warehouse/hive-exec.jar'
> symbol='org.apache.hadoop.hive.ql.udf.UDFPI';
> MainThread: Started query ba41ccb6f020becd:db23209f
> -- executing against localhost:21000
> create function if not exists foo() returns double
> location '/test-warehouse/not-a-real-file.so'
> symbol='FnDoesNotExist';
> -- executing against localhost:21000
> create function if not exists foo() returns double
> location '/test-warehouse/not-a-real-file.so'
> symbol='FnDoesNotExist';
> -- executing against localhost:21000
> create function if not exists foo (string, string) returns string location
> '/test-warehouse/test_udf_errors_be4e0293_bad_udf.ll' symbol='MyAwesomeUdf';
> -- executing against localhost:21000
> create function if not exists twenty_args(int, int, int, int, int, int,
> int, int, int, int, int, int, int, int, int, int, int, int, int, int)
> returns int
> location '/test-warehouse/libTestUdfs.so'
> symbol='TwentyArgs';
> MainThread: Started query
[jira] [Commented] (IMPALA-7419) NullPointerException in SimplifyConditionalsRule
[
https://issues.apache.org/jira/browse/IMPALA-7419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16579117#comment-16579117
]
ASF subversion and git services commented on IMPALA-7419:
-
Commit b07a65a67afe1ee69f0f8983293671a98aaa04bd in impala's branch
refs/heads/master from [~twmarshall]
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=b07a65a ]
IMPALA-7419: Fix NullPointerException in SimplifyConditionalsRule
In SimplifyConditionalsRule, when simplifying a 'coalesce' where the
result is another coalesce with some children removed, we create a new
Expr for the new coalesce but previously were not analyzing the new
Expr.
This causes problems if the simplified Expr contains an aggregate
function, as we check to make sure the simplification didn't eliminate
any aggregates and the check expects the Expr to be analyzed.
The solution is to analyze the new Expr before performing the check
for aggregates.
Testing:
- Added a FE test to ExprRewriteRulesTest
Change-Id: I5d066b48c2824cc09ce21260ad06b3d50b14c54a
Reviewed-on: http://gerrit.cloudera.org:8080/11179
Reviewed-by: Impala Public Jenkins
Tested-by: Impala Public Jenkins
> NullPointerException in SimplifyConditionalsRule
>
>
> Key: IMPALA-7419
> URL: https://issues.apache.org/jira/browse/IMPALA-7419
> Project: IMPALA
> Issue Type: Bug
> Components: Frontend
>Affects Versions: Impala 3.1.0
>Reporter: Thomas Tauber-Marshall
>Assignee: Thomas Tauber-Marshall
>Priority: Critical
>
> Found by the query generator:
> {noformat}
> SELECT
> COALESCE((-311) * (NULL), MIN(DISTINCT tinyint_col), 42)
> FROM functional.alltypes
> {noformat}
> {noformat}
> java.lang.NullPointerException
> at
> com.google.common.base.Preconditions.checkNotNull(Preconditions.java:187)
> at
> org.apache.impala.analysis.FunctionCallExpr.isAggregateFunction(FunctionCallExpr.java:238)
>
> at org.apache.impala.analysis.Expr$1.apply(Expr.java:100)
> at org.apache.impala.analysis.Expr$1.apply(Expr.java:97)
> at org.apache.impala.common.TreeNode.contains(TreeNode.java:162)
> at
> org.apache.impala.rewrite.SimplifyConditionalsRule.apply(SimplifyConditionalsRule.java:84)
>
> at
> org.apache.impala.rewrite.ExprRewriter.applyRuleBottomUp(ExprRewriter.java:85)
>
> at
> org.apache.impala.rewrite.ExprRewriter.applyRuleRepeatedly(ExprRewriter.java:71)
>
> at
> org.apache.impala.rewrite.ExprRewriter.rewrite(ExprRewriter.java:55)
> at
> org.apache.impala.analysis.SelectList.rewriteExprs(SelectList.java:97)
> at
> org.apache.impala.analysis.SelectStmt.rewriteExprs(SelectStmt.java:892)
> at
> org.apache.impala.analysis.AnalysisContext.analyze(AnalysisContext.java:446)
> at
> org.apache.impala.analysis.AnalysisContext.analyzeAndAuthorize(AnalysisContext.java:408)
>
> at
> org.apache.impala.service.Frontend.createExecRequest(Frontend.java:1035)
> at
> org.apache.impala.service.JniFrontend.createExecRequest(JniFrontend.java:165)
> {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-7347) Assertion Failure - test_show_create_table
[
https://issues.apache.org/jira/browse/IMPALA-7347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16579112#comment-16579112
]
ASF subversion and git services commented on IMPALA-7347:
-
Commit 3cb784310f16547be850228cdf03cfc115721857 in impala's branch
refs/heads/master from [~tianyiwang]
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=3cb7843 ]
IMPALA-7347: Ignore numFilesErasureCoded in TestShowCreateTable
This table properties only exist for HDFS tables. To get the test work
on local tables, it needs to be ignored.
Change-Id: Icc8494fb91c4777cee662a97f750486aa8e79a8e
Reviewed-on: http://gerrit.cloudera.org:8080/11192
Reviewed-by: Impala Public Jenkins
Tested-by: Impala Public Jenkins
> Assertion Failure - test_show_create_table
> ---
>
> Key: IMPALA-7347
> URL: https://issues.apache.org/jira/browse/IMPALA-7347
> Project: IMPALA
> Issue Type: Bug
>Affects Versions: Impala 3.1.0
>Reporter: nithya
>Assignee: Tianyi Wang
>Priority: Blocker
> Labels: build-failure
> Fix For: Impala 3.1.0
>
>
> test_show_create_table in metadata/test_show_create_table.py is failing with
> the following assertion error
> {noformat}
> metadata/test_show_create_table.py:58: in test_show_create_table
> unique_database)
> metadata/test_show_create_table.py:106: in __run_show_create_table_test_case
> self.__compare_result(expected_result, create_table_result)
> metadata/test_show_create_table.py:134: in __compare_result
> assert expected_tbl_props == actual_tbl_props
> E assert {} == {'numFilesErasureCoded': '0'}
> E Right contains more items:
> E {'numFilesErasureCoded': '0'}
> E Use -v to get the full diff
> {noformat}
>
> It appears that table property "numFilesErasureCoded" is showing up in table
> properties.
> Either the test needs updating or a bug.
>
> {code}
> h3. Error Message
> metadata/test_show_create_table.py:58: in test_show_create_table
> unique_database) metadata/test_show_create_table.py:106: in
> __run_show_create_table_test_case self.__compare_result(expected_result,
> create_table_result) metadata/test_show_create_table.py:134: in
> __compare_result assert expected_tbl_props == actual_tbl_props E assert {} ==
> \{'numFilesErasureCoded': '0'} E Right contains more items: E
> \{'numFilesErasureCoded': '0'} E Use -v to get the full diff
> {code}
>
> ---
> {code}
> h3. Standard Error
> -- connecting to: localhost:21000 SET sync_ddl=False; -- executing against
> localhost:21000 DROP DATABASE IF EXISTS `test_show_create_table_f1598d0b`
> CASCADE; SET sync_ddl=False; -- executing against localhost:21000 CREATE
> DATABASE `test_show_create_table_f1598d0b`; MainThread: Created database
> "test_show_create_table_f1598d0b" for test ID
> "metadata/test_show_create_table.py::TestShowCreateTable::()::test_show_create_table[table_format:
> text/none]" -- executing against localhost:21000 CREATE TABLE
> test_show_create_table_f1598d0b.test1 ( id INT ) STORED AS TEXTFILE; --
> executing against localhost:21000 show create table
> test_show_create_table_f1598d0b.test1; -- executing against localhost:21000
> drop table test_show_create_table_f1598d0b.test1; -- executing against
> localhost:21000 CREATE TABLE test_show_create_table_f1598d0b.test1 (id INT)
> STORED AS TEXTFILE LOCATION
> 'hdfs://localhost:20500/test-warehouse/test_show_create_table_f1598d0b.db/test1';
> -- executing against localhost:21000 show create table
> test_show_create_table_f1598d0b.test1; -- executing against localhost:21000
> drop table test_show_create_table_f1598d0b.test1; -- executing against
> localhost:21000 CREATE TABLE test_show_create_table_f1598d0b.test2 ( year
> INT, month INT, id INT COMMENT 'Add a comment', bool_col BOOLEAN, tinyint_col
> TINYINT, smallint_col SMALLINT, int_col INT, bigint_col BIGINT, float_col
> FLOAT, double_col DOUBLE, date_string_col STRING, string_col STRING,
> timestamp_col TIMESTAMP ) STORED AS TEXTFILE; -- executing against
> localhost:21000 show create table test_show_create_table_f1598d0b.test2; --
> executing against localhost:21000 drop table
> test_show_create_table_f1598d0b.test2; -- executing against localhost:21000
> CREATE TABLE test_show_create_table_f1598d0b.test2 (year INT, month INT, id
> INT COMMENT 'Add a comment', bool_col BOOLEAN, tinyint_col TINYINT,
> smallint_col SMALLINT, int_col INT, bigint_col BIGINT, float_col FLOAT,
> double_col DOUBLE, date_string_col STRING, string_col STRING, timestamp_col
> TIMESTAMP) STORED AS TEXTFILE LOCATION
> 'hdfs://localhost:20500/test-warehouse/test_show_create_table_f1598d0b.db/test2';
> -- executing against localhost:21000 show create table
> test_show_create_table_f1598d0b.test2; -- executing against localhost:21000
> drop table
[jira] [Commented] (IMPALA-7418) test_udf_errors - returns Cancelled instead of actual error
[
https://issues.apache.org/jira/browse/IMPALA-7418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16579114#comment-16579114
]
ASF subversion and git services commented on IMPALA-7418:
-
Commit 2e5df138aaf4354fd4ada69b627842c34fef2e05 in impala's branch
refs/heads/master from poojanilangekar
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=2e5df13 ]
IMPALA-7335/IMPALA-7418: Add logs to HdfsScanNode to debug the issues
IMPALA-7335 and IMPALA-7418 are failing some builds on jenkins.
However, there is no deterministic method to reproduce them
locally and hence it is difficult to figure out the cause of the
failure. From the existing logs, it appears that the status
generated by HdfsScanNode::ProcessSplit() is lost. This log
would help determine the condition when the failures occur.
Change-Id: I68698c90031edc6ee8c31e9ce3d52dade9d8f6f1
Reviewed-on: http://gerrit.cloudera.org:8080/11174
Reviewed-by: Bikramjeet Vig
Tested-by: Impala Public Jenkins
> test_udf_errors - returns Cancelled instead of actual error
> ---
>
> Key: IMPALA-7418
> URL: https://issues.apache.org/jira/browse/IMPALA-7418
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
>Affects Versions: Impala 3.1.0
>Reporter: Tim Armstrong
>Assignee: Pooja Nilangekar
>Priority: Blocker
> Labels: broken-build
>
> {noformat}
> query_test.test_udfs.TestUdfExecution.test_udf_errors[exec_option:
> {'disable_codegen_rows_threshold': 0, 'disable_codegen': True,
> 'exec_single_node_rows_threshold': 0, 'enable_expr_rewrites': True} |
> table_format: text/none] (from pytest)
> Failing for the past 1 build (Since Failed#2925 )
> Took 19 sec.
> add description
> Error Message
> query_test/test_udfs.py:415: in test_udf_errors
> self.run_test_case('QueryTest/udf-errors', vector, use_db=unique_database)
> common/impala_test_suite.py:412: in run_test_case
> self.__verify_exceptions(test_section['CATCH'], str(e), use_db)
> common/impala_test_suite.py:290: in __verify_exceptions (expected_str,
> actual_str) E AssertionError: Unexpected exception string. Expected:
> BadExpr2 prepare error E Not found in actual: ImpalaBeeswaxException: Query
> aborted:Cancelled
> Stacktrace
> query_test/test_udfs.py:415: in test_udf_errors
> self.run_test_case('QueryTest/udf-errors', vector, use_db=unique_database)
> common/impala_test_suite.py:412: in run_test_case
> self.__verify_exceptions(test_section['CATCH'], str(e), use_db)
> common/impala_test_suite.py:290: in __verify_exceptions
> (expected_str, actual_str)
> E AssertionError: Unexpected exception string. Expected: BadExpr2 prepare
> error
> E Not found in actual: ImpalaBeeswaxException: Query aborted:Cancelled
> Standard Error
> SET sync_ddl=False;
> -- executing against localhost:21000
> DROP DATABASE IF EXISTS `test_udf_errors_be4e0293` CASCADE;
> MainThread: Started query bd4790b45c20640d:9c62ffba
> SET sync_ddl=False;
> -- executing against localhost:21000
> CREATE DATABASE `test_udf_errors_be4e0293`;
> MainThread: Started query 474595a3ecba67bd:7a14c84
> MainThread: Created database "test_udf_errors_be4e0293" for test ID
> "query_test/test_udfs.py::TestUdfExecution::()::test_udf_errors[exec_option:
> {'disable_codegen_rows_threshold': 0, 'disable_codegen': True,
> 'exec_single_node_rows_threshold': 0, 'enable_expr_rewrites': True} |
> table_format: text/none]"
> -- executing against localhost:21000
> use test_udf_errors_be4e0293;
> MainThread: Started query 264b0cd09d289c09:cc5dafed
> SET disable_codegen_rows_threshold=0;
> SET disable_codegen=True;
> SET exec_single_node_rows_threshold=0;
> SET enable_expr_rewrites=True;
> -- executing against localhost:21000
> create function if not exists hive_pi() returns double
> location '/test-warehouse/hive-exec.jar'
> symbol='org.apache.hadoop.hive.ql.udf.UDFPI';
> MainThread: Started query ba41ccb6f020becd:db23209f
> -- executing against localhost:21000
> create function if not exists foo() returns double
> location '/test-warehouse/not-a-real-file.so'
> symbol='FnDoesNotExist';
> -- executing against localhost:21000
> create function if not exists foo() returns double
> location '/test-warehouse/not-a-real-file.so'
> symbol='FnDoesNotExist';
> -- executing against localhost:21000
> create function if not exists foo (string, string) returns string location
> '/test-warehouse/test_udf_errors_be4e0293_bad_udf.ll' symbol='MyAwesomeUdf';
> -- executing against localhost:21000
> create function if not exists twenty_args(int, int, int, int, int, int,
> int, int, int, int, int, int, int, int, int, int, int, int, int, int)
> returns int
> location '/test-warehouse/libTestUdfs.so'
> symbol='TwentyArgs';
> MainThread: Started query
[jira] [Commented] (IMPALA-7335) Assertion Failure - test_corrupt_files
[
https://issues.apache.org/jira/browse/IMPALA-7335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16579113#comment-16579113
]
ASF subversion and git services commented on IMPALA-7335:
-
Commit 2e5df138aaf4354fd4ada69b627842c34fef2e05 in impala's branch
refs/heads/master from poojanilangekar
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=2e5df13 ]
IMPALA-7335/IMPALA-7418: Add logs to HdfsScanNode to debug the issues
IMPALA-7335 and IMPALA-7418 are failing some builds on jenkins.
However, there is no deterministic method to reproduce them
locally and hence it is difficult to figure out the cause of the
failure. From the existing logs, it appears that the status
generated by HdfsScanNode::ProcessSplit() is lost. This log
would help determine the condition when the failures occur.
Change-Id: I68698c90031edc6ee8c31e9ce3d52dade9d8f6f1
Reviewed-on: http://gerrit.cloudera.org:8080/11174
Reviewed-by: Bikramjeet Vig
Tested-by: Impala Public Jenkins
> Assertion Failure - test_corrupt_files
> --
>
> Key: IMPALA-7335
> URL: https://issues.apache.org/jira/browse/IMPALA-7335
> Project: IMPALA
> Issue Type: Bug
>Affects Versions: Impala 3.1.0
>Reporter: nithya
>Assignee: Pooja Nilangekar
>Priority: Critical
> Labels: broken-build
>
> test_corrupt_files fails
>
> query_test.test_scanners.TestParquet.test_corrupt_files[exec_option:
> \\{'batch_size': 0, 'num_nodes': 0, 'disable_codegen_rows_threshold': 0,
> 'disable_codegen': False, 'abort_on_error': 1, 'debug_action': None,
> 'exec_single_node_rows_threshold': 0} | table_format: parquet/none] (from
> pytest)
>
> {code:java}
> Error Message
> query_test/test_scanners.py:300: in test_corrupt_files
> self.run_test_case('QueryTest/parquet-abort-on-error', vector)
> common/impala_test_suite.py:420: in run_test_case assert False, "Expected
> exception: %s" % expected_str E AssertionError: Expected exception: Column
> metadata states there are 11 values, but read 10 values from column id.
> STACKTRACE
> query_test/test_scanners.py:300: in test_corrupt_files
> self.run_test_case('QueryTest/parquet-abort-on-error', vector)
> common/impala_test_suite.py:420: in run_test_case
> assert False, "Expected exception: %s" % expected_str
> E AssertionError: Expected exception: Column metadata states there are 11
> values, but read 10 values from column id.
> Standard Error
> -- executing against localhost:21000
> use functional_parquet;
> SET batch_size=0;
> SET num_nodes=0;
> SET disable_codegen_rows_threshold=0;
> SET disable_codegen=False;
> SET abort_on_error=0;
> SET exec_single_node_rows_threshold=0;
> -- executing against localhost:21000
> set num_nodes=1;
> -- executing against localhost:21000
> set num_scanner_threads=1;
> -- executing against localhost:21000
> select id, cnt from bad_column_metadata t, (select count(*) cnt from
> t.int_array) v;
> -- executing against localhost:21000
> SET NUM_NODES="0";
> -- executing against localhost:21000
> SET NUM_SCANNER_THREADS="0";
> -- executing against localhost:21000
> set num_nodes=1;
> -- executing against localhost:21000
> set num_scanner_threads=1;
> -- executing against localhost:21000
> select id from bad_column_metadata;
> -- executing against localhost:21000
> SET NUM_NODES="0";
> -- executing against localhost:21000
> SET NUM_SCANNER_THREADS="0";
> -- executing against localhost:21000
> SELECT * from bad_parquet_strings_negative_len;
> -- executing against localhost:21000
> SELECT * from bad_parquet_strings_out_of_bounds;
> -- executing against localhost:21000
> use functional_parquet;
> SET batch_size=0;
> SET num_nodes=0;
> SET disable_codegen_rows_threshold=0;
> SET disable_codegen=False;
> SET abort_on_error=1;
> SET exec_single_node_rows_threshold=0;
> -- executing against localhost:21000
> set num_nodes=1;
> -- executing against localhost:21000
> set num_scanner_threads=1;
> -- executing against localhost:21000
> select id, cnt from bad_column_metadata t, (select count(*) cnt from
> t.int_array) v;
> -- executing against localhost:21000
> SET NUM_NODES="0";
> -- executing against localhost:21000
> SET NUM_SCANNER_THREADS="0";
> -- executing against localhost:21000
> set num_nodes=1;
> -- executing against localhost:21000
> set num_scanner_threads=1;
> -- executing against localhost:21000
> select id from bad_column_metadata;
> -- executing against localhost:21000
> SET NUM_NODES="0";
> -- executing against localhost:21000
> SET NUM_SCANNER_THREADS="0";
> {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-7335) Assertion Failure - test_corrupt_files
[
https://issues.apache.org/jira/browse/IMPALA-7335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16579115#comment-16579115
]
ASF subversion and git services commented on IMPALA-7335:
-
Commit 2e5df138aaf4354fd4ada69b627842c34fef2e05 in impala's branch
refs/heads/master from poojanilangekar
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=2e5df13 ]
IMPALA-7335/IMPALA-7418: Add logs to HdfsScanNode to debug the issues
IMPALA-7335 and IMPALA-7418 are failing some builds on jenkins.
However, there is no deterministic method to reproduce them
locally and hence it is difficult to figure out the cause of the
failure. From the existing logs, it appears that the status
generated by HdfsScanNode::ProcessSplit() is lost. This log
would help determine the condition when the failures occur.
Change-Id: I68698c90031edc6ee8c31e9ce3d52dade9d8f6f1
Reviewed-on: http://gerrit.cloudera.org:8080/11174
Reviewed-by: Bikramjeet Vig
Tested-by: Impala Public Jenkins
> Assertion Failure - test_corrupt_files
> --
>
> Key: IMPALA-7335
> URL: https://issues.apache.org/jira/browse/IMPALA-7335
> Project: IMPALA
> Issue Type: Bug
>Affects Versions: Impala 3.1.0
>Reporter: nithya
>Assignee: Pooja Nilangekar
>Priority: Critical
> Labels: broken-build
>
> test_corrupt_files fails
>
> query_test.test_scanners.TestParquet.test_corrupt_files[exec_option:
> \\{'batch_size': 0, 'num_nodes': 0, 'disable_codegen_rows_threshold': 0,
> 'disable_codegen': False, 'abort_on_error': 1, 'debug_action': None,
> 'exec_single_node_rows_threshold': 0} | table_format: parquet/none] (from
> pytest)
>
> {code:java}
> Error Message
> query_test/test_scanners.py:300: in test_corrupt_files
> self.run_test_case('QueryTest/parquet-abort-on-error', vector)
> common/impala_test_suite.py:420: in run_test_case assert False, "Expected
> exception: %s" % expected_str E AssertionError: Expected exception: Column
> metadata states there are 11 values, but read 10 values from column id.
> STACKTRACE
> query_test/test_scanners.py:300: in test_corrupt_files
> self.run_test_case('QueryTest/parquet-abort-on-error', vector)
> common/impala_test_suite.py:420: in run_test_case
> assert False, "Expected exception: %s" % expected_str
> E AssertionError: Expected exception: Column metadata states there are 11
> values, but read 10 values from column id.
> Standard Error
> -- executing against localhost:21000
> use functional_parquet;
> SET batch_size=0;
> SET num_nodes=0;
> SET disable_codegen_rows_threshold=0;
> SET disable_codegen=False;
> SET abort_on_error=0;
> SET exec_single_node_rows_threshold=0;
> -- executing against localhost:21000
> set num_nodes=1;
> -- executing against localhost:21000
> set num_scanner_threads=1;
> -- executing against localhost:21000
> select id, cnt from bad_column_metadata t, (select count(*) cnt from
> t.int_array) v;
> -- executing against localhost:21000
> SET NUM_NODES="0";
> -- executing against localhost:21000
> SET NUM_SCANNER_THREADS="0";
> -- executing against localhost:21000
> set num_nodes=1;
> -- executing against localhost:21000
> set num_scanner_threads=1;
> -- executing against localhost:21000
> select id from bad_column_metadata;
> -- executing against localhost:21000
> SET NUM_NODES="0";
> -- executing against localhost:21000
> SET NUM_SCANNER_THREADS="0";
> -- executing against localhost:21000
> SELECT * from bad_parquet_strings_negative_len;
> -- executing against localhost:21000
> SELECT * from bad_parquet_strings_out_of_bounds;
> -- executing against localhost:21000
> use functional_parquet;
> SET batch_size=0;
> SET num_nodes=0;
> SET disable_codegen_rows_threshold=0;
> SET disable_codegen=False;
> SET abort_on_error=1;
> SET exec_single_node_rows_threshold=0;
> -- executing against localhost:21000
> set num_nodes=1;
> -- executing against localhost:21000
> set num_scanner_threads=1;
> -- executing against localhost:21000
> select id, cnt from bad_column_metadata t, (select count(*) cnt from
> t.int_array) v;
> -- executing against localhost:21000
> SET NUM_NODES="0";
> -- executing against localhost:21000
> SET NUM_SCANNER_THREADS="0";
> -- executing against localhost:21000
> set num_nodes=1;
> -- executing against localhost:21000
> set num_scanner_threads=1;
> -- executing against localhost:21000
> select id from bad_column_metadata;
> -- executing against localhost:21000
> SET NUM_NODES="0";
> -- executing against localhost:21000
> SET NUM_SCANNER_THREADS="0";
> {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-7422) Crash in QueryState::PublishFilter() fragment_map_.count(params.dst_fragment_idx) == 1 (0 vs. 1)
[
https://issues.apache.org/jira/browse/IMPALA-7422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16579083#comment-16579083
]
Michael Ho commented on IMPALA-7422:
Most likely the race is between {{QueryState::Init()}} and
{{QueryState::PublishFilter()}}. In particular, there is a window between when
the query state has been created and when {{QueryState::Init()}} finishes. If
{{QueryState::PublishFilter()}} sneaks in within this window,
{{qs->instances_prepared_barrier_}} and {{qs->instances_finished_barrier_}} may
not have been initialized yet.
{noformat}
Status QueryExecMgr::StartQuery(const TExecQueryFInstancesParams& params) {
TUniqueId query_id = params.query_ctx.query_id;
VLOG_QUERY << "StartQueryFInstances() query_id=" << PrintId(query_id)
<< " coord=" <<
TNetworkAddressToString(params.query_ctx.coord_address);
bool dummy;
QueryState* qs = GetOrCreateQueryState(params.query_ctx, ); <<--- a
window between this line and next line
Status status = qs->Init(params);
if (!status.ok()) {
qs->ReleaseExecResourceRefcount(); // Release refcnt acquired in Init().
ReleaseQueryState(qs);
return status;
}
...
}
{noformat}
> Crash in QueryState::PublishFilter()
> fragment_map_.count(params.dst_fragment_idx) == 1 (0 vs. 1)
>
>
> Key: IMPALA-7422
> URL: https://issues.apache.org/jira/browse/IMPALA-7422
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
>Affects Versions: Impala 3.1.0
>Reporter: Tim Armstrong
>Assignee: Michael Ho
>Priority: Blocker
> Labels: broken-build, crash
> Attachments:
> impalad.impala-ec2-centos74-m5-4xlarge-ondemand-17c2.vpc.cloudera.com.jenkins.log.ERROR.20180809-162257.28028.gz,
>
> impalad.impala-ec2-centos74-m5-4xlarge-ondemand-17c2.vpc.cloudera.com.jenkins.log.FATAL.20180809-201036.28028.gz,
>
> impalad.impala-ec2-centos74-m5-4xlarge-ondemand-17c2.vpc.cloudera.com.jenkins.log.INFO.20180809-162257.28028.gz,
>
> impalad.impala-ec2-centos74-m5-4xlarge-ondemand-17c2.vpc.cloudera.com.jenkins.log.WARNING.20180809-162257.28028.gz
>
>
> Ran into this running core tests on one of my patches.
> {noformat}
> query-state.cc:506] Check failed:
> fragment_map_.count(params.dst_fragment_idx) == 1 (0 vs. 1)
> *** Check failure stack trace: ***
> @ 0x4387b8c
> @ 0x4389431
> @ 0x4387566
> @ 0x438ab2d
> @ 0x1e0ba94
> @ 0x1f3d097
> @ 0x303fe61
> @ 0x303ddef
> @ 0x18fa28f
> @ 0x1d0d1b8
> @ 0x1d054b8
> @ 0x1d06bde
> @ 0x1d06a74
> @ 0x1d067c0
> @ 0x1d066d3
> @ 0x1c2d3c1
> @ 0x2041992
> @ 0x2049a6a
> @ 0x204998e
> @ 0x2049951
> @ 0x32b31d9
> @ 0x7fb7d61a2e24
> @ 0x7fb7d5ed034c
> {noformat}
> {noformat}
> 20:10:21 [gw0] PASSED
> query_test/test_runtime_filters.py::TestMinMaxFilters::test_min_max_filters[exec_option:
> {'batch_size': 0, 'num_nodes': 0, 'disable_codegen_rows_threshold': 0,
> 'disable_codegen': False, 'abort_on_error': 1, 'debug_action': None,
> 'exec_single_node_rows_threshold': 0} | table_format: kudu/none]
> 20:10:29
> query_test/test_runtime_filters.py::TestMinMaxFilters::test_large_strings
> 20:10:29 [gw0] PASSED
> query_test/test_runtime_filters.py::TestMinMaxFilters::test_large_strings
> 20:10:30
> query_test/test_runtime_filters.py::TestRuntimeRowFilters::test_row_filters[exec_option:
> {'batch_size': 0, 'num_nodes': 0, 'disable_codegen_rows_threshold': 0,
> 'disable_codegen': True, 'abort_on_error': 1, 'debug_action': None,
> 'exec_single_node_rows_threshold': 0} | table_format: parquet/none]
> 20:10:30 [gw3] PASSED
> query_test/test_runtime_filters.py::TestBloomFilters::test_bloom_filters[exec_option:
> {'batch_size': 0, 'num_nodes': 0, 'disable_codegen_rows_threshold': 0,
> 'disable_codegen': False, 'abort_on_error': 1, 'debug_action': None,
> 'exec_single_node_rows_threshold': 0} | table_format: seq/def/record]
> 20:10:32
> query_test/test_runtime_filters.py::TestBloomFilters::test_bloom_filters[exec_option:
> {'batch_size': 0, 'num_nodes': 0, 'disable_codegen_rows_threshold': 0,
> 'disable_codegen': True, 'abort_on_error': 1, 'debug_action': None,
> 'exec_single_node_rows_threshold': 0} | table_format: seq/def/record]
> 20:10:32 [gw4] PASSED
> query_test/test_queries.py::TestQueries::test_subquery[exec_option:
> {'disable_codegen_rows_threshold': 0, 'disable_codegen': True,
> 'abort_on_error': 1, 'debug_action': None, 'exec_single_node_rows_threshold':
> '100', 'batch_size': 0, 'num_nodes': 0} | table_format:
[jira] [Commented] (IMPALA-5937) Docs are missing some query options
[ https://issues.apache.org/jira/browse/IMPALA-5937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16579070#comment-16579070 ] Alex Rodoni commented on IMPALA-5937: - [https://gerrit.cloudera.org/#/c/11206/] for enable_expr_rewrites > Docs are missing some query options > --- > > Key: IMPALA-5937 > URL: https://issues.apache.org/jira/browse/IMPALA-5937 > Project: IMPALA > Issue Type: Bug > Components: Docs >Reporter: Philip Zeyliger >Assignee: Alex Rodoni >Priority: Major > > I noticed that the following options show up in "SET" in impala-shell but > don't have corresponding documentation entries. I know BUFFER_POOL_LIMIT is > mentioned in IMPALA-5655. > --BUFFER_POOL_LIMIT-- > -DECIMAL_V2- > -DEFAULT_SPILLABLE_BUFFER_SIZE- > -DISABLE_CODEGEN_ROWS_THRESHOLD- > ENABLE_EXPR_REWRITES > -MAX_ROW_SIZE- > -MIN_SPILLABLE_BUFFER_SIZE- > -PARQUET_ARRAY_RESOLUTION- > PARQUET_DICTIONARY_FILTERING > PARQUET_READ_STATISTICS > -STRICT_MODE /Dev option that Greg and Tim recommended not to doc- -- 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-5937) Docs are missing some query options
[ https://issues.apache.org/jira/browse/IMPALA-5937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-5937 started by Alex Rodoni. --- > Docs are missing some query options > --- > > Key: IMPALA-5937 > URL: https://issues.apache.org/jira/browse/IMPALA-5937 > Project: IMPALA > Issue Type: Bug > Components: Docs >Reporter: Philip Zeyliger >Assignee: Alex Rodoni >Priority: Major > > I noticed that the following options show up in "SET" in impala-shell but > don't have corresponding documentation entries. I know BUFFER_POOL_LIMIT is > mentioned in IMPALA-5655. > --BUFFER_POOL_LIMIT-- > -DECIMAL_V2- > -DEFAULT_SPILLABLE_BUFFER_SIZE- > -DISABLE_CODEGEN_ROWS_THRESHOLD- > ENABLE_EXPR_REWRITES > -MAX_ROW_SIZE- > -MIN_SPILLABLE_BUFFER_SIZE- > -PARQUET_ARRAY_RESOLUTION- > PARQUET_DICTIONARY_FILTERING > PARQUET_READ_STATISTICS > -STRICT_MODE /Dev option that Greg and Tim recommended not to doc- -- 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-6782) Impala Doc: Reformat the functions docs that use dlentrys to use concepts
[ https://issues.apache.org/jira/browse/IMPALA-6782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-6782. --- Resolution: Later > Impala Doc: Reformat the functions docs that use dlentrys to use concepts > - > > Key: IMPALA-6782 > URL: https://issues.apache.org/jira/browse/IMPALA-6782 > Project: IMPALA > Issue Type: Improvement > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IMPALA-6782) Impala Doc: Reformat the functions docs that use dlentrys to use concepts
[ https://issues.apache.org/jira/browse/IMPALA-6782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-6782. --- Resolution: Later > Impala Doc: Reformat the functions docs that use dlentrys to use concepts > - > > Key: IMPALA-6782 > URL: https://issues.apache.org/jira/browse/IMPALA-6782 > Project: IMPALA > Issue Type: Improvement > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > -- 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-7434) Impala 2.12 Doc: Kudu's kinit does not support auth_to_local rules with Heimdal kerberos
[ https://issues.apache.org/jira/browse/IMPALA-7434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni updated IMPALA-7434: Labels: future_release_doc (was: ) > Impala 2.12 Doc: Kudu's kinit does not support auth_to_local rules with > Heimdal kerberos > > > Key: IMPALA-7434 > URL: https://issues.apache.org/jira/browse/IMPALA-7434 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Labels: future_release_doc > Fix For: Impala 3.0, Impala 2.12.0 > > > https://gerrit.cloudera.org/#/c/11204/ -- 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-7435) Re-enable --thread_creation_fault_injection for ClientRequestState
Tim Armstrong created IMPALA-7435: - Summary: Re-enable --thread_creation_fault_injection for ClientRequestState Key: IMPALA-7435 URL: https://issues.apache.org/jira/browse/IMPALA-7435 Project: IMPALA Issue Type: Bug Components: Backend Reporter: Tim Armstrong IMPALA-7396 disabled thread creation fault injection in one place. We should re-enable it. -- 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-7435) Re-enable --thread_creation_fault_injection for ClientRequestState
Tim Armstrong created IMPALA-7435: - Summary: Re-enable --thread_creation_fault_injection for ClientRequestState Key: IMPALA-7435 URL: https://issues.apache.org/jira/browse/IMPALA-7435 Project: IMPALA Issue Type: Bug Components: Backend Reporter: Tim Armstrong IMPALA-7396 disabled thread creation fault injection in one place. We should re-enable it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IMPALA-6836) Impala Doc: Refactor Query Profile doc
[ https://issues.apache.org/jira/browse/IMPALA-6836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16579038#comment-16579038 ] Alex Rodoni commented on IMPALA-6836: - [~tarmstr...@cloudera.com] [~lv] Do you know where I can get a few good profile examples to use in the Query Profile doc to highlight red flags? https://impala.apache.org/docs/build3x/html/topics/impala_explain_plan.html > Impala Doc: Refactor Query Profile doc > -- > > Key: IMPALA-6836 > URL: https://issues.apache.org/jira/browse/IMPALA-6836 > Project: IMPALA > Issue Type: Task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > > From [~tarmstr...@cloudera.com]: > The common use case for the profiles seems to be drilling down on "why is my > query slow?". It seems like guiding readers through a few common examples > might be more useful than the current approach. -- 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-7402) DCHECK failed min_bytes_to_write <= dirty_unpinned_pages_ in buffer-pool
[
https://issues.apache.org/jira/browse/IMPALA-7402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16579013#comment-16579013
]
Tim Armstrong commented on IMPALA-7402:
---
[~vukercegovac] there have been some infra issues with archiving of cores so I
don't believe it got saved.
> DCHECK failed min_bytes_to_write <= dirty_unpinned_pages_ in buffer-pool
>
>
> Key: IMPALA-7402
> URL: https://issues.apache.org/jira/browse/IMPALA-7402
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
>Affects Versions: Impala 3.1.0
>Reporter: Vuk Ercegovac
>Assignee: Tim Armstrong
>Priority: Blocker
> Labels: broken-build
>
> One of the impalad's crashed with the following DCHECK failure:
> {noformat}
> F0806 01:26:21.905500 5101 buffer-pool.cc:645] Check failed:
> min_bytes_to_write <= dirty_unpinned_pages_.bytes() (8192 vs. 0)
> Here is the backtrace:{noformat}
> {noformat}
> #0 0x003af1e328e5 in raise () from /lib64/libc.so.6
> #1 0x003af1e340c5 in abort () from /lib64/libc.so.6
> #2 0x0437f454 in google::DumpStackTraceAndExit() ()
> #3 0x04375ead in google::LogMessage::Fail() ()
> #4 0x04377752 in google::LogMessage::SendToLog() ()
> #5 0x04375887 in google::LogMessage::Flush() ()
> #6 0x04378e4e in google::LogMessageFatal::~LogMessageFatal() ()
> #7 0x0205ad16 in impala::BufferPool::Client::WriteDirtyPagesAsync
> (this=0x17d03f0e0, min_bytes_to_write=8192) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/repos/Impala/be/src/runtime/bufferpool/buffer-pool.cc:645
>
> #8 0x0205a835 in impala::BufferPool::Client::CleanPages
> (this=0x17d03f0e0, client_lock=0x7f324cb12220, len=8192) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/repos/Impala/be/src/runtime/bufferpool/buffer-pool.cc:625
>
> #9 0x0205a646 in impala::BufferPool::Client::DecreaseReservationTo
> (this=0x17d03f0e0, max_decrease=8192, target_bytes=8192) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/repos/Impala/be/src/runtime/bufferpool/buffer-pool.cc:609
>
> #10 0x02057583 in
> impala::BufferPool::ClientHandle::DecreaseReservationTo (this=0x181c0a990,
> max_decrease=8192, target_bytes=8192) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/repos/Impala/be/src/runtime/bufferpool/buffer-pool.cc:319
>
> #11 0x020d9419 in
> impala::HdfsScanNode::ReturnReservationFromScannerThread (this=0x181c0a800,
> lock=..., bytes=8192) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/repos/Impala/be/src/exec/hdfs-scan-node.cc:194
>
> #12 0x020da485 in impala::HdfsScanNode::ScannerThread
> (this=0x181c0a800, first_thread=false, scanner_thread_reservation=8192) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/repos/Impala/be/src/exec/hdfs-scan-node.cc:367
>
> #13 0x020d96b0 in impala::HdfsScanNodeoperator()(void)
> const (__closure=0x7f324cb12b88) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/repos/Impala/be/src/exec/hdfs-scan-node.cc:261
>
> #14 0x020db6d6 in
> boost::detail::function::void_function_obj_invoker0,
> void>::invoke(boost::detail::function::function_buffer &)
> (function_obj_ptr=...) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/Impala-Toolchain/boost-1.57.0-p3/include/boost/function/function_template.hpp:153
> ...
> {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-7402) DCHECK failed min_bytes_to_write <= dirty_unpinned_pages_ in buffer-pool
[
https://issues.apache.org/jira/browse/IMPALA-7402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16579008#comment-16579008
]
Vuk Ercegovac commented on IMPALA-7402:
---
I didn't grab the core but since it happened last week some time, it should
still be archived, right?
> DCHECK failed min_bytes_to_write <= dirty_unpinned_pages_ in buffer-pool
>
>
> Key: IMPALA-7402
> URL: https://issues.apache.org/jira/browse/IMPALA-7402
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
>Affects Versions: Impala 3.1.0
>Reporter: Vuk Ercegovac
>Assignee: Tim Armstrong
>Priority: Blocker
> Labels: broken-build
>
> One of the impalad's crashed with the following DCHECK failure:
> {noformat}
> F0806 01:26:21.905500 5101 buffer-pool.cc:645] Check failed:
> min_bytes_to_write <= dirty_unpinned_pages_.bytes() (8192 vs. 0)
> Here is the backtrace:{noformat}
> {noformat}
> #0 0x003af1e328e5 in raise () from /lib64/libc.so.6
> #1 0x003af1e340c5 in abort () from /lib64/libc.so.6
> #2 0x0437f454 in google::DumpStackTraceAndExit() ()
> #3 0x04375ead in google::LogMessage::Fail() ()
> #4 0x04377752 in google::LogMessage::SendToLog() ()
> #5 0x04375887 in google::LogMessage::Flush() ()
> #6 0x04378e4e in google::LogMessageFatal::~LogMessageFatal() ()
> #7 0x0205ad16 in impala::BufferPool::Client::WriteDirtyPagesAsync
> (this=0x17d03f0e0, min_bytes_to_write=8192) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/repos/Impala/be/src/runtime/bufferpool/buffer-pool.cc:645
>
> #8 0x0205a835 in impala::BufferPool::Client::CleanPages
> (this=0x17d03f0e0, client_lock=0x7f324cb12220, len=8192) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/repos/Impala/be/src/runtime/bufferpool/buffer-pool.cc:625
>
> #9 0x0205a646 in impala::BufferPool::Client::DecreaseReservationTo
> (this=0x17d03f0e0, max_decrease=8192, target_bytes=8192) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/repos/Impala/be/src/runtime/bufferpool/buffer-pool.cc:609
>
> #10 0x02057583 in
> impala::BufferPool::ClientHandle::DecreaseReservationTo (this=0x181c0a990,
> max_decrease=8192, target_bytes=8192) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/repos/Impala/be/src/runtime/bufferpool/buffer-pool.cc:319
>
> #11 0x020d9419 in
> impala::HdfsScanNode::ReturnReservationFromScannerThread (this=0x181c0a800,
> lock=..., bytes=8192) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/repos/Impala/be/src/exec/hdfs-scan-node.cc:194
>
> #12 0x020da485 in impala::HdfsScanNode::ScannerThread
> (this=0x181c0a800, first_thread=false, scanner_thread_reservation=8192) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/repos/Impala/be/src/exec/hdfs-scan-node.cc:367
>
> #13 0x020d96b0 in impala::HdfsScanNodeoperator()(void)
> const (__closure=0x7f324cb12b88) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/repos/Impala/be/src/exec/hdfs-scan-node.cc:261
>
> #14 0x020db6d6 in
> boost::detail::function::void_function_obj_invoker0,
> void>::invoke(boost::detail::function::function_buffer &)
> (function_obj_ptr=...) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/Impala-Toolchain/boost-1.57.0-p3/include/boost/function/function_template.hpp:153
> ...
> {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] [Updated] (IMPALA-7434) Impala 2.12 Doc: Kudu's kinit does not support auth_to_local rules with Heimdal kerberos
[ https://issues.apache.org/jira/browse/IMPALA-7434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni updated IMPALA-7434: Description: https://gerrit.cloudera.org/#/c/11204/ > Impala 2.12 Doc: Kudu's kinit does not support auth_to_local rules with > Heimdal kerberos > > > Key: IMPALA-7434 > URL: https://issues.apache.org/jira/browse/IMPALA-7434 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.0, Impala 2.12.0 > > > https://gerrit.cloudera.org/#/c/11204/ -- 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-7402) DCHECK failed min_bytes_to_write <= dirty_unpinned_pages_ in buffer-pool
[
https://issues.apache.org/jira/browse/IMPALA-7402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16578985#comment-16578985
]
Tim Armstrong commented on IMPALA-7402:
---
My best guess is that there's something wonky with the lifecycle of the
HdfsScanner or ScannerContext. The code doing cleanup of the two has evolved
more than been designed so it's not clear what the expectations are about who
calls HdfsScanner::Close() and/or ScannerContext::ReleaseCompletedResources()
and/or ScanRange::Cancel(). I suspect there's some code path where we miss
calling one of those.
> DCHECK failed min_bytes_to_write <= dirty_unpinned_pages_ in buffer-pool
>
>
> Key: IMPALA-7402
> URL: https://issues.apache.org/jira/browse/IMPALA-7402
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
>Affects Versions: Impala 3.1.0
>Reporter: Vuk Ercegovac
>Assignee: Tim Armstrong
>Priority: Blocker
> Labels: broken-build
>
> One of the impalad's crashed with the following DCHECK failure:
> {noformat}
> F0806 01:26:21.905500 5101 buffer-pool.cc:645] Check failed:
> min_bytes_to_write <= dirty_unpinned_pages_.bytes() (8192 vs. 0)
> Here is the backtrace:{noformat}
> {noformat}
> #0 0x003af1e328e5 in raise () from /lib64/libc.so.6
> #1 0x003af1e340c5 in abort () from /lib64/libc.so.6
> #2 0x0437f454 in google::DumpStackTraceAndExit() ()
> #3 0x04375ead in google::LogMessage::Fail() ()
> #4 0x04377752 in google::LogMessage::SendToLog() ()
> #5 0x04375887 in google::LogMessage::Flush() ()
> #6 0x04378e4e in google::LogMessageFatal::~LogMessageFatal() ()
> #7 0x0205ad16 in impala::BufferPool::Client::WriteDirtyPagesAsync
> (this=0x17d03f0e0, min_bytes_to_write=8192) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/repos/Impala/be/src/runtime/bufferpool/buffer-pool.cc:645
>
> #8 0x0205a835 in impala::BufferPool::Client::CleanPages
> (this=0x17d03f0e0, client_lock=0x7f324cb12220, len=8192) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/repos/Impala/be/src/runtime/bufferpool/buffer-pool.cc:625
>
> #9 0x0205a646 in impala::BufferPool::Client::DecreaseReservationTo
> (this=0x17d03f0e0, max_decrease=8192, target_bytes=8192) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/repos/Impala/be/src/runtime/bufferpool/buffer-pool.cc:609
>
> #10 0x02057583 in
> impala::BufferPool::ClientHandle::DecreaseReservationTo (this=0x181c0a990,
> max_decrease=8192, target_bytes=8192) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/repos/Impala/be/src/runtime/bufferpool/buffer-pool.cc:319
>
> #11 0x020d9419 in
> impala::HdfsScanNode::ReturnReservationFromScannerThread (this=0x181c0a800,
> lock=..., bytes=8192) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/repos/Impala/be/src/exec/hdfs-scan-node.cc:194
>
> #12 0x020da485 in impala::HdfsScanNode::ScannerThread
> (this=0x181c0a800, first_thread=false, scanner_thread_reservation=8192) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/repos/Impala/be/src/exec/hdfs-scan-node.cc:367
>
> #13 0x020d96b0 in impala::HdfsScanNodeoperator()(void)
> const (__closure=0x7f324cb12b88) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/repos/Impala/be/src/exec/hdfs-scan-node.cc:261
>
> #14 0x020db6d6 in
> boost::detail::function::void_function_obj_invoker0,
> void>::invoke(boost::detail::function::function_buffer &)
> (function_obj_ptr=...) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/Impala-Toolchain/boost-1.57.0-p3/include/boost/function/function_template.hpp:153
> ...
> {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-7402) DCHECK failed min_bytes_to_write <= dirty_unpinned_pages_ in buffer-pool
[
https://issues.apache.org/jira/browse/IMPALA-7402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16578973#comment-16578973
]
Tim Armstrong commented on IMPALA-7402:
---
This is proving to be very difficult to reproduce or debug without a core.
> DCHECK failed min_bytes_to_write <= dirty_unpinned_pages_ in buffer-pool
>
>
> Key: IMPALA-7402
> URL: https://issues.apache.org/jira/browse/IMPALA-7402
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
>Affects Versions: Impala 3.1.0
>Reporter: Vuk Ercegovac
>Assignee: Tim Armstrong
>Priority: Blocker
> Labels: broken-build
>
> One of the impalad's crashed with the following DCHECK failure:
> {noformat}
> F0806 01:26:21.905500 5101 buffer-pool.cc:645] Check failed:
> min_bytes_to_write <= dirty_unpinned_pages_.bytes() (8192 vs. 0)
> Here is the backtrace:{noformat}
> {noformat}
> #0 0x003af1e328e5 in raise () from /lib64/libc.so.6
> #1 0x003af1e340c5 in abort () from /lib64/libc.so.6
> #2 0x0437f454 in google::DumpStackTraceAndExit() ()
> #3 0x04375ead in google::LogMessage::Fail() ()
> #4 0x04377752 in google::LogMessage::SendToLog() ()
> #5 0x04375887 in google::LogMessage::Flush() ()
> #6 0x04378e4e in google::LogMessageFatal::~LogMessageFatal() ()
> #7 0x0205ad16 in impala::BufferPool::Client::WriteDirtyPagesAsync
> (this=0x17d03f0e0, min_bytes_to_write=8192) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/repos/Impala/be/src/runtime/bufferpool/buffer-pool.cc:645
>
> #8 0x0205a835 in impala::BufferPool::Client::CleanPages
> (this=0x17d03f0e0, client_lock=0x7f324cb12220, len=8192) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/repos/Impala/be/src/runtime/bufferpool/buffer-pool.cc:625
>
> #9 0x0205a646 in impala::BufferPool::Client::DecreaseReservationTo
> (this=0x17d03f0e0, max_decrease=8192, target_bytes=8192) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/repos/Impala/be/src/runtime/bufferpool/buffer-pool.cc:609
>
> #10 0x02057583 in
> impala::BufferPool::ClientHandle::DecreaseReservationTo (this=0x181c0a990,
> max_decrease=8192, target_bytes=8192) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/repos/Impala/be/src/runtime/bufferpool/buffer-pool.cc:319
>
> #11 0x020d9419 in
> impala::HdfsScanNode::ReturnReservationFromScannerThread (this=0x181c0a800,
> lock=..., bytes=8192) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/repos/Impala/be/src/exec/hdfs-scan-node.cc:194
>
> #12 0x020da485 in impala::HdfsScanNode::ScannerThread
> (this=0x181c0a800, first_thread=false, scanner_thread_reservation=8192) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/repos/Impala/be/src/exec/hdfs-scan-node.cc:367
>
> #13 0x020d96b0 in impala::HdfsScanNodeoperator()(void)
> const (__closure=0x7f324cb12b88) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/repos/Impala/be/src/exec/hdfs-scan-node.cc:261
>
> #14 0x020db6d6 in
> boost::detail::function::void_function_obj_invoker0,
> void>::invoke(boost::detail::function::function_buffer &)
> (function_obj_ptr=...) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/Impala-Toolchain/boost-1.57.0-p3/include/boost/function/function_template.hpp:153
> ...
> {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-7402) DCHECK failed min_bytes_to_write <= dirty_unpinned_pages_ in buffer-pool
[
https://issues.apache.org/jira/browse/IMPALA-7402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on IMPALA-7402 started by Tim Armstrong.
-
> DCHECK failed min_bytes_to_write <= dirty_unpinned_pages_ in buffer-pool
>
>
> Key: IMPALA-7402
> URL: https://issues.apache.org/jira/browse/IMPALA-7402
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
>Affects Versions: Impala 3.1.0
>Reporter: Vuk Ercegovac
>Assignee: Tim Armstrong
>Priority: Blocker
> Labels: broken-build
>
> One of the impalad's crashed with the following DCHECK failure:
> {noformat}
> F0806 01:26:21.905500 5101 buffer-pool.cc:645] Check failed:
> min_bytes_to_write <= dirty_unpinned_pages_.bytes() (8192 vs. 0)
> Here is the backtrace:{noformat}
> {noformat}
> #0 0x003af1e328e5 in raise () from /lib64/libc.so.6
> #1 0x003af1e340c5 in abort () from /lib64/libc.so.6
> #2 0x0437f454 in google::DumpStackTraceAndExit() ()
> #3 0x04375ead in google::LogMessage::Fail() ()
> #4 0x04377752 in google::LogMessage::SendToLog() ()
> #5 0x04375887 in google::LogMessage::Flush() ()
> #6 0x04378e4e in google::LogMessageFatal::~LogMessageFatal() ()
> #7 0x0205ad16 in impala::BufferPool::Client::WriteDirtyPagesAsync
> (this=0x17d03f0e0, min_bytes_to_write=8192) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/repos/Impala/be/src/runtime/bufferpool/buffer-pool.cc:645
>
> #8 0x0205a835 in impala::BufferPool::Client::CleanPages
> (this=0x17d03f0e0, client_lock=0x7f324cb12220, len=8192) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/repos/Impala/be/src/runtime/bufferpool/buffer-pool.cc:625
>
> #9 0x0205a646 in impala::BufferPool::Client::DecreaseReservationTo
> (this=0x17d03f0e0, max_decrease=8192, target_bytes=8192) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/repos/Impala/be/src/runtime/bufferpool/buffer-pool.cc:609
>
> #10 0x02057583 in
> impala::BufferPool::ClientHandle::DecreaseReservationTo (this=0x181c0a990,
> max_decrease=8192, target_bytes=8192) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/repos/Impala/be/src/runtime/bufferpool/buffer-pool.cc:319
>
> #11 0x020d9419 in
> impala::HdfsScanNode::ReturnReservationFromScannerThread (this=0x181c0a800,
> lock=..., bytes=8192) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/repos/Impala/be/src/exec/hdfs-scan-node.cc:194
>
> #12 0x020da485 in impala::HdfsScanNode::ScannerThread
> (this=0x181c0a800, first_thread=false, scanner_thread_reservation=8192) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/repos/Impala/be/src/exec/hdfs-scan-node.cc:367
>
> #13 0x020d96b0 in impala::HdfsScanNodeoperator()(void)
> const (__closure=0x7f324cb12b88) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/repos/Impala/be/src/exec/hdfs-scan-node.cc:261
>
> #14 0x020db6d6 in
> boost::detail::function::void_function_obj_invoker0,
> void>::invoke(boost::detail::function::function_buffer &)
> (function_obj_ptr=...) at
> /data/jenkins/workspace/impala-cdh6.x-exhaustive-centos6/Impala-Toolchain/boost-1.57.0-p3/include/boost/function/function_template.hpp:153
> ...
> {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-7434) Impala 2.12 Doc: Kudu's kinit does not support auth_to_local rules with Heimdal kerberos
[ https://issues.apache.org/jira/browse/IMPALA-7434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-7434 started by Alex Rodoni. --- > Impala 2.12 Doc: Kudu's kinit does not support auth_to_local rules with > Heimdal kerberos > > > Key: IMPALA-7434 > URL: https://issues.apache.org/jira/browse/IMPALA-7434 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Fix For: Impala 3.0, Impala 2.12.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] [Created] (IMPALA-7434) Impala 2.12 Doc: Kudu's kinit does not support auth_to_local rules with Heimdal kerberos
Alex Rodoni created IMPALA-7434: --- Summary: Impala 2.12 Doc: Kudu's kinit does not support auth_to_local rules with Heimdal kerberos Key: IMPALA-7434 URL: https://issues.apache.org/jira/browse/IMPALA-7434 Project: IMPALA Issue Type: Sub-task Components: Docs Reporter: Alex Rodoni Assignee: Alex Rodoni Fix For: Impala 2.12.0, Impala 3.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] [Created] (IMPALA-7434) Impala 2.12 Doc: Kudu's kinit does not support auth_to_local rules with Heimdal kerberos
Alex Rodoni created IMPALA-7434: --- Summary: Impala 2.12 Doc: Kudu's kinit does not support auth_to_local rules with Heimdal kerberos Key: IMPALA-7434 URL: https://issues.apache.org/jira/browse/IMPALA-7434 Project: IMPALA Issue Type: Sub-task Components: Docs Reporter: Alex Rodoni Assignee: Alex Rodoni Fix For: Impala 2.12.0, Impala 3.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IMPALA-7433) Reduce volume of -v=1 logs on executors
Tim Armstrong created IMPALA-7433: - Summary: Reduce volume of -v=1 logs on executors Key: IMPALA-7433 URL: https://issues.apache.org/jira/browse/IMPALA-7433 Project: IMPALA Issue Type: Bug Components: Backend Affects Versions: Impala 3.1.0 Reporter: Tim Armstrong Assignee: Tim Armstrong We're currently logging a lot of things per query on executors that is redundant or unnecessary, e.g.: * ExecQueryFInstances() and StartQueryFInstances() are both logged but are redundant * Some random low-level details are logged, e.g. "Max row batch queue size for scan node '0' in fragment instance '940cdcd50664a51:368ab669001e': 180" I think we should cut back the logging at -v=1, which is the default log level most deployments run at: * Do log key finstance lifecycle events that are useful to understand what finstances are running and if/when failures occurred * Don't log things redundantly * Don't log lower-level events that occur in the normal flow of query execution (e.g. memory limits, queue lengths). These things have limited diagnostic value and should be in the profile, if anywhere -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IMPALA-7433) Reduce volume of -v=1 logs on executors
Tim Armstrong created IMPALA-7433: - Summary: Reduce volume of -v=1 logs on executors Key: IMPALA-7433 URL: https://issues.apache.org/jira/browse/IMPALA-7433 Project: IMPALA Issue Type: Bug Components: Backend Affects Versions: Impala 3.1.0 Reporter: Tim Armstrong Assignee: Tim Armstrong We're currently logging a lot of things per query on executors that is redundant or unnecessary, e.g.: * ExecQueryFInstances() and StartQueryFInstances() are both logged but are redundant * Some random low-level details are logged, e.g. "Max row batch queue size for scan node '0' in fragment instance '940cdcd50664a51:368ab669001e': 180" I think we should cut back the logging at -v=1, which is the default log level most deployments run at: * Do log key finstance lifecycle events that are useful to understand what finstances are running and if/when failures occurred * Don't log things redundantly * Don't log lower-level events that occur in the normal flow of query execution (e.g. memory limits, queue lengths). These things have limited diagnostic value and should be in the profile, if anywhere -- 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-7432) Impala 3.1 Doc: Add logged_in_user alias for effective_user
Alex Rodoni created IMPALA-7432: --- Summary: Impala 3.1 Doc: Add logged_in_user alias for effective_user Key: IMPALA-7432 URL: https://issues.apache.org/jira/browse/IMPALA-7432 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)
[jira] [Created] (IMPALA-7432) Impala 3.1 Doc: Add logged_in_user alias for effective_user
Alex Rodoni created IMPALA-7432: --- Summary: Impala 3.1 Doc: Add logged_in_user alias for effective_user Key: IMPALA-7432 URL: https://issues.apache.org/jira/browse/IMPALA-7432 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] [Created] (IMPALA-7431) Impala 3.1 Doc: Make METASTORE_DB configurable and default to escaped $IMPALA_HOME
Alex Rodoni created IMPALA-7431: --- Summary: Impala 3.1 Doc: Make METASTORE_DB configurable and default to escaped $IMPALA_HOME Key: IMPALA-7431 URL: https://issues.apache.org/jira/browse/IMPALA-7431 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] [Created] (IMPALA-7431) Impala 3.1 Doc: Make METASTORE_DB configurable and default to escaped $IMPALA_HOME
Alex Rodoni created IMPALA-7431: --- Summary: Impala 3.1 Doc: Make METASTORE_DB configurable and default to escaped $IMPALA_HOME Key: IMPALA-7431 URL: https://issues.apache.org/jira/browse/IMPALA-7431 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)
[jira] [Resolved] (IMPALA-7383) Make METASTORE_DB configurable and default to escaped $IMPALA_HOME
[ https://issues.apache.org/jira/browse/IMPALA-7383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tianyi Wang resolved IMPALA-7383. - Resolution: Fixed Fix Version/s: Impala 3.1.0 > Make METASTORE_DB configurable and default to escaped $IMPALA_HOME > -- > > Key: IMPALA-7383 > URL: https://issues.apache.org/jira/browse/IMPALA-7383 > Project: IMPALA > Issue Type: Improvement >Affects Versions: Impala 3.1.0 >Reporter: Tianyi Wang >Assignee: Tianyi Wang >Priority: Trivial > Labels: infrastructure > Fix For: Impala 3.1.0 > > > Some developers keep multiple impala repos on their disk. Isolating > METASTORE_DB may help with switching between those repos without needing to > reload the data. -- 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-7383) Make METASTORE_DB configurable and default to escaped $IMPALA_HOME
[ https://issues.apache.org/jira/browse/IMPALA-7383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tianyi Wang resolved IMPALA-7383. - Resolution: Fixed Fix Version/s: Impala 3.1.0 > Make METASTORE_DB configurable and default to escaped $IMPALA_HOME > -- > > Key: IMPALA-7383 > URL: https://issues.apache.org/jira/browse/IMPALA-7383 > Project: IMPALA > Issue Type: Improvement >Affects Versions: Impala 3.1.0 >Reporter: Tianyi Wang >Assignee: Tianyi Wang >Priority: Trivial > Labels: infrastructure > Fix For: Impala 3.1.0 > > > Some developers keep multiple impala repos on their disk. Isolating > METASTORE_DB may help with switching between those repos without needing to > reload the data. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IMPALA-7430) Remove the log added to HdfsScanNode::ScannerThread
[ https://issues.apache.org/jira/browse/IMPALA-7430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar updated IMPALA-7430: - Description: Logs were added to the HdfsScanNode in order to debug IMPALA-7335 and IMPALA-7418. These need to be removed once the cause of these bugs is established and we find a way to reproduce it locally. (was: Logs were added to the HdfsScanNode in order to debug IMPALA-7135 and IMPALA-7418. These need to be removed once the cause of these bugs is established and we find a way to reproduce it locally. ) > Remove the log added to HdfsScanNode::ScannerThread > --- > > Key: IMPALA-7430 > URL: https://issues.apache.org/jira/browse/IMPALA-7430 > Project: IMPALA > Issue Type: Task >Reporter: Pooja Nilangekar >Assignee: Pooja Nilangekar >Priority: Blocker > > Logs were added to the HdfsScanNode in order to debug IMPALA-7335 and > IMPALA-7418. These need to be removed once the cause of these bugs is > established and we find a way to reproduce it locally. -- 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-7430) Remove the log added to HdfsScanNode::ScannerThread
Pooja Nilangekar created IMPALA-7430: Summary: Remove the log added to HdfsScanNode::ScannerThread Key: IMPALA-7430 URL: https://issues.apache.org/jira/browse/IMPALA-7430 Project: IMPALA Issue Type: Task Reporter: Pooja Nilangekar Assignee: Pooja Nilangekar Logs were added to the HdfsScanNode in order to debug IMPALA-7135 and IMPALA-7418. These need to be removed once the cause of these bugs is established and we find a way to reproduce it locally. -- 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-7429) We should print the HBase scan ID when scans fail
Lars Volker created IMPALA-7429:
---
Summary: We should print the HBase scan ID when scans fail
Key: IMPALA-7429
URL: https://issues.apache.org/jira/browse/IMPALA-7429
Project: IMPALA
Issue Type: Improvement
Components: Backend
Affects Versions: Impala 3.1.0
Reporter: Lars Volker
When HBase scans fail we should print the HBase-side scan ID to make debugging
easier. For example:
{noformat}
host.domain.com INFOAugust 13, 2018 9:38 AM cc:412
Instance completed. instance_id=f44dde40610b7609:6ceda0220007 #in-flight=8
status=GENERAL: IOException: Failed to get result within timeout,
timeout=6ms <-- INCLUDE ID IN THIS LINE
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IMPALA-7429) We should print the HBase scan ID when scans fail
[
https://issues.apache.org/jira/browse/IMPALA-7429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Volker updated IMPALA-7429:
Description:
When HBase scans fail we should print the HBase-side scan ID to make debugging
easier. For example:
{noformat}
host.domain.com INFOAugust 13, 2018 9:38 AM cc:412
Instance completed. instance_id=f44dde40610b7609:6ceda0220007 #in-flight=8
status=GENERAL: IOException: Failed to get result within timeout,
timeout=6ms <-- INCLUDE ID IN THIS LINE
{noformat}
We should probably also add the scan ID in the HBASE_SCAN_NODE fragment
instance in the profile.
was:
When HBase scans fail we should print the HBase-side scan ID to make debugging
easier. For example:
{noformat}
host.domain.com INFOAugust 13, 2018 9:38 AM cc:412
Instance completed. instance_id=f44dde40610b7609:6ceda0220007 #in-flight=8
status=GENERAL: IOException: Failed to get result within timeout,
timeout=6ms <-- INCLUDE ID IN THIS LINE
{noformat}
> We should print the HBase scan ID when scans fail
> -
>
> Key: IMPALA-7429
> URL: https://issues.apache.org/jira/browse/IMPALA-7429
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
>Affects Versions: Impala 3.1.0
>Reporter: Lars Volker
>Priority: Major
> Labels: supportability
>
> When HBase scans fail we should print the HBase-side scan ID to make
> debugging easier. For example:
> {noformat}
> host.domain.com INFOAugust 13, 2018 9:38 AM cc:412
> Instance completed. instance_id=f44dde40610b7609:6ceda0220007
> #in-flight=8 status=GENERAL: IOException: Failed to get result within
> timeout, timeout=6ms <-- INCLUDE ID IN THIS LINE
> {noformat}
> We should probably also add the scan ID in the HBASE_SCAN_NODE fragment
> instance in the profile.
--
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-7429) We should print the HBase scan ID when scans fail
Lars Volker created IMPALA-7429:
---
Summary: We should print the HBase scan ID when scans fail
Key: IMPALA-7429
URL: https://issues.apache.org/jira/browse/IMPALA-7429
Project: IMPALA
Issue Type: Improvement
Components: Backend
Affects Versions: Impala 3.1.0
Reporter: Lars Volker
When HBase scans fail we should print the HBase-side scan ID to make debugging
easier. For example:
{noformat}
host.domain.com INFOAugust 13, 2018 9:38 AM cc:412
Instance completed. instance_id=f44dde40610b7609:6ceda0220007 #in-flight=8
status=GENERAL: IOException: Failed to get result within timeout,
timeout=6ms <-- INCLUDE ID IN THIS LINE
{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] [Updated] (IMPALA-7427) Write Impala version information to writer.model.name footer field of Parquet
[ https://issues.apache.org/jira/browse/IMPALA-7427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7427: -- Component/s: Backend > Write Impala version information to writer.model.name footer field of Parquet > - > > Key: IMPALA-7427 > URL: https://issues.apache.org/jira/browse/IMPALA-7427 > Project: IMPALA > Issue Type: Improvement > Components: Backend >Reporter: Zoltan Ivanfi >Priority: Minor > Labels: parquet > > PARQUET-352 added support for the "writer.model.name" property in the Parquet > metadata to identify the object model (application) that wrote the file. -- 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-7427) Write Impala version information to writer.model.name footer field of Parquet
[ https://issues.apache.org/jira/browse/IMPALA-7427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7427: -- Labels: parquet (was: ) > Write Impala version information to writer.model.name footer field of Parquet > - > > Key: IMPALA-7427 > URL: https://issues.apache.org/jira/browse/IMPALA-7427 > Project: IMPALA > Issue Type: Improvement > Components: Backend >Reporter: Zoltan Ivanfi >Priority: Minor > Labels: parquet > > PARQUET-352 added support for the "writer.model.name" property in the Parquet > metadata to identify the object model (application) that wrote the file. -- 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-7398) Add logged_in_user alias for effective_user
[ https://issues.apache.org/jira/browse/IMPALA-7398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16578524#comment-16578524 ] ASF subversion and git services commented on IMPALA-7398: - Commit 7002ad3b35a8217daa0f5a1962eaff338030d327 in impala's branch refs/heads/master from [~aholley] [ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=7002ad3 ] IMPALA-7398: Add logged_in_user alias for effective_user This patch adds an alias to the effective_user function so that views created in Hive using the logged_in_user function will work in Impala. Example: CREATE VIEW foo.view1 AS SELECT * FROM foo.table1 WHERE name=logged_in_user(); Tests: - Added function and ran delegation tests - Ran backend tests - Ran custom-cluster tests including delegation Change-Id: Id63f243e0fffbe2798f1f9dbc4cc3ebe9d9529a6 Reviewed-on: http://gerrit.cloudera.org:8080/11184 Reviewed-by: Impala Public Jenkins Tested-by: Impala Public Jenkins > Add logged_in_user alias for effective_user > --- > > Key: IMPALA-7398 > URL: https://issues.apache.org/jira/browse/IMPALA-7398 > Project: IMPALA > Issue Type: Improvement > Components: Backend >Affects Versions: Impala 3.0, Impala 2.12.0 >Reporter: Peter Ebert >Assignee: Adam Holley >Priority: Major > Labels: authorization > Fix For: Impala 3.1.0 > > > When using sentry Hive will return a different value for 'current_user' than > Impala. This means a view using these values would be inconsistent between > the two SQL engines. By adding 'logged_in_user' as an alias for > 'effective_user' views would be consistent between Hive and Impala. -- 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-7423) NoSuchMethodError when starting Sentry in the minicluster
[
https://issues.apache.org/jira/browse/IMPALA-7423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16578523#comment-16578523
]
ASF subversion and git services commented on IMPALA-7423:
-
Commit 83fc1fbb6749b5d09089879e5f5e4c618dd91373 in impala's branch
refs/heads/master from [~fredyw]
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=83fc1fb ]
IMPALA-7423: NoSuchMethodError when starting Sentry
The issue that is caused by the classpath ordering because of two
conflicting sentry-provider JARs:
- sentry-provider-db-2.0.0-cdh6.x-SNAPSHOT.jar
- sentry-provider-db-2.0.0-cdh6.x-SNAPSHOT-sh.jar (uses shaded Sentry
Thrift)
This patch fixes the issue by removing sentry-provider-db:2.0.0:sh from
FE dependencies.
Testing:
- Ran a clean build and was able to start Sentry
Change-Id: Ie6cdfd184e06009a8d582499b2f6fd3011de6d5a
Reviewed-on: http://gerrit.cloudera.org:8080/11187
Reviewed-by: Impala Public Jenkins
Tested-by: Impala Public Jenkins
> NoSuchMethodError when starting Sentry in the minicluster
> -
>
> Key: IMPALA-7423
> URL: https://issues.apache.org/jira/browse/IMPALA-7423
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
>Affects Versions: Impala 3.0
>Reporter: Fredy Wijaya
>Assignee: Fredy Wijaya
>Priority: Major
> Labels: flaky-build
>
> {noformat}
> ERROR StatusLogger No log4j2 configuration file found. Using default
> configuration: logging only errors to the console. Set system property
> 'org.apache.logging.log4j.simplelog.StatusLogger.level' to TRACE to show
> Log4j2 internal initialization logging.
> Exception in thread "main" java.lang.NoSuchMethodError:
> org.apache.sentry.api.service.thrift.SentryPolicyServiceClientDefaultImpl.(Lorg/apache/hadoop/conf/Configuration;Lsentry/org/apache/sentry/core/common/transport/SentryTransportPool;)V
> at
> org.apache.sentry.service.thrift.SentryServiceClientFactory.create(SentryServiceClientFactory.java:90)
> at
> org.apache.sentry.service.thrift.SentryServiceClientFactory.create(SentryServiceClientFactory.java:68)
> at
> org.apache.impala.util.SentryPolicyService$SentryServiceClient.createClient(SentryPolicyService.java:91)
> at
> org.apache.impala.util.SentryPolicyService$SentryServiceClient.(SentryPolicyService.java:64)
> at
> org.apache.impala.util.SentryPolicyService.listAllRoles(SentryPolicyService.java:395)
> at
> org.apache.impala.testutil.SentryServicePinger.main(SentryServicePinger.java:81)
> Error in /home/impdev/Impala/testdata/bin/run-sentry-service.sh at line 39:
> "$JAVA" -cp $CLASSPATH org.apache.impala.testutil.SentryServicePinger \
> Error in /home/impdev/Impala/testdata/bin/run-all.sh at line 61: tee
> ${IMPALA_CLUSTER_LOGS_DIR}/run-sentry-service.log
> {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-7428) Flaky test: test_shell_commandline.py / test_large_sql
[
https://issues.apache.org/jira/browse/IMPALA-7428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16578481#comment-16578481
]
Fredy Wijaya commented on IMPALA-7428:
--
I'll work on it.
> Flaky test: test_shell_commandline.py / test_large_sql
> --
>
> Key: IMPALA-7428
> URL: https://issues.apache.org/jira/browse/IMPALA-7428
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
>Reporter: Csaba Ringhofer
>Assignee: Fredy Wijaya
>Priority: Major
> Labels: flaky-test
>
> One of the test failures in
> https://jenkins.impala.io/job/gerrit-verify-dryrun/2983/consoleFull was:
> {code}
> 14:03:27 ] assert actual_time_s <= time_limit_s, (
> 14:03:27 ] E AssertionError: It took 31.9429180622 seconds to execute the
> query. Time limit is 30 seconds.
> 14:03:27 ] E assert 31.942918062210083 <= 30
> {code}
> This should not be related to the tested change, so I think that the test is
> flaky.
--
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-7428) Flaky test: test_shell_commandline.py / test_large_sql
[
https://issues.apache.org/jira/browse/IMPALA-7428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on IMPALA-7428 started by Fredy Wijaya.
> Flaky test: test_shell_commandline.py / test_large_sql
> --
>
> Key: IMPALA-7428
> URL: https://issues.apache.org/jira/browse/IMPALA-7428
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
>Reporter: Csaba Ringhofer
>Assignee: Fredy Wijaya
>Priority: Major
> Labels: flaky-test
>
> One of the test failures in
> https://jenkins.impala.io/job/gerrit-verify-dryrun/2983/consoleFull was:
> {code}
> 14:03:27 ] assert actual_time_s <= time_limit_s, (
> 14:03:27 ] E AssertionError: It took 31.9429180622 seconds to execute the
> query. Time limit is 30 seconds.
> 14:03:27 ] E assert 31.942918062210083 <= 30
> {code}
> This should not be related to the tested change, so I think that the test is
> flaky.
--
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-7428) Flaky test: test_shell_commandline.py / test_large_sql
[
https://issues.apache.org/jira/browse/IMPALA-7428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16578479#comment-16578479
]
Csaba Ringhofer commented on IMPALA-7428:
-
[~fredyw] I have assigned this ticket to you because you added the test in
https://gerrit.cloudera.org/#/c/10939/
Feel free to assign it back to me if you do not have time to deal with it at
the moment.
> Flaky test: test_shell_commandline.py / test_large_sql
> --
>
> Key: IMPALA-7428
> URL: https://issues.apache.org/jira/browse/IMPALA-7428
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
>Reporter: Csaba Ringhofer
>Assignee: Fredy Wijaya
>Priority: Major
> Labels: flaky-test
>
> One of the test failures in
> https://jenkins.impala.io/job/gerrit-verify-dryrun/2983/consoleFull was:
> {code}
> 14:03:27 ] assert actual_time_s <= time_limit_s, (
> 14:03:27 ] E AssertionError: It took 31.9429180622 seconds to execute the
> query. Time limit is 30 seconds.
> 14:03:27 ] E assert 31.942918062210083 <= 30
> {code}
> This should not be related to the tested change, so I think that the test is
> flaky.
--
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-7428) Flaky test: test_shell_commandline.py / test_large_sql
[
https://issues.apache.org/jira/browse/IMPALA-7428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Csaba Ringhofer reassigned IMPALA-7428:
---
Assignee: Fredy Wijaya
> Flaky test: test_shell_commandline.py / test_large_sql
> --
>
> Key: IMPALA-7428
> URL: https://issues.apache.org/jira/browse/IMPALA-7428
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
>Reporter: Csaba Ringhofer
>Assignee: Fredy Wijaya
>Priority: Major
> Labels: flaky-test
>
> One of the test failures in
> https://jenkins.impala.io/job/gerrit-verify-dryrun/2983/consoleFull was:
> {code}
> 14:03:27 ] assert actual_time_s <= time_limit_s, (
> 14:03:27 ] E AssertionError: It took 31.9429180622 seconds to execute the
> query. Time limit is 30 seconds.
> 14:03:27 ] E assert 31.942918062210083 <= 30
> {code}
> This should not be related to the tested change, so I think that the test is
> flaky.
--
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-7428) Flaky test: test_shell_commandline.py / test_large_sql
Csaba Ringhofer created IMPALA-7428:
---
Summary: Flaky test: test_shell_commandline.py / test_large_sql
Key: IMPALA-7428
URL: https://issues.apache.org/jira/browse/IMPALA-7428
Project: IMPALA
Issue Type: Bug
Components: Infrastructure
Reporter: Csaba Ringhofer
One of the test failures in
https://jenkins.impala.io/job/gerrit-verify-dryrun/2983/consoleFull was:
{code}
14:03:27 ] assert actual_time_s <= time_limit_s, (
14:03:27 ] E AssertionError: It took 31.9429180622 seconds to execute the
query. Time limit is 30 seconds.
14:03:27 ] E assert 31.942918062210083 <= 30
{code}
This should not be related to the tested change, so I think that the test is
flaky.
--
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-7398) Add logged_in_user alias for effective_user
[ https://issues.apache.org/jira/browse/IMPALA-7398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Holley resolved IMPALA-7398. - Resolution: Fixed Fix Version/s: Impala 3.1.0 > Add logged_in_user alias for effective_user > --- > > Key: IMPALA-7398 > URL: https://issues.apache.org/jira/browse/IMPALA-7398 > Project: IMPALA > Issue Type: Improvement > Components: Backend >Affects Versions: Impala 3.0, Impala 2.12.0 >Reporter: Peter Ebert >Assignee: Adam Holley >Priority: Major > Labels: authorization > Fix For: Impala 3.1.0 > > > When using sentry Hive will return a different value for 'current_user' than > Impala. This means a view using these values would be inconsistent between > the two SQL engines. By adding 'logged_in_user' as an alias for > 'effective_user' views would be consistent between Hive and Impala. -- 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-7427) Write Impala version information to writer.model.name footer field of Parquet
Zoltan Ivanfi created IMPALA-7427: - Summary: Write Impala version information to writer.model.name footer field of Parquet Key: IMPALA-7427 URL: https://issues.apache.org/jira/browse/IMPALA-7427 Project: IMPALA Issue Type: Improvement Reporter: Zoltan Ivanfi PARQUET-352 added support for the "writer.model.name" property in the Parquet metadata to identify the object model (application) that wrote the file. -- 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-7427) Write Impala version information to writer.model.name footer field of Parquet
Zoltan Ivanfi created IMPALA-7427: - Summary: Write Impala version information to writer.model.name footer field of Parquet Key: IMPALA-7427 URL: https://issues.apache.org/jira/browse/IMPALA-7427 Project: IMPALA Issue Type: Improvement Reporter: Zoltan Ivanfi PARQUET-352 added support for the "writer.model.name" property in the Parquet metadata to identify the object model (application) that wrote the file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
