[jira] [Resolved] (IMPALA-8578) Reduce code in metric headers
[ https://issues.apache.org/jira/browse/IMPALA-8578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-8578. --- Resolution: Fixed Fix Version/s: Impala 3.3.0 > Reduce code in metric headers > - > > Key: IMPALA-8578 > URL: https://issues.apache.org/jira/browse/IMPALA-8578 > Project: IMPALA > Issue Type: Improvement > Components: Backend >Reporter: Tim Armstrong >Assignee: Tim Armstrong >Priority: Major > Fix For: Impala 3.3.0 > > > metrics.h and other metric headers are included a lot of places and there is > a lot of code in the header that has very few callers. It appears to be > pulled into several hundred compilation units, increasing the compile time of > each of those and forcing recompilation when the headers are changed. > Some ideas: > * Move function implementations to .cc files. E.g. ToJson() and > ToPrometheus() don't need to be inlined. > * Move MetricGroup to its own file > * Try to see if we can use forward declarations in more places to avoid > including 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] [Commented] (IMPALA-8505) Support AlterTable DDL with Kudu/HMS integration in Catalogd mode
[ https://issues.apache.org/jira/browse/IMPALA-8505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16856313#comment-16856313 ] ASF subversion and git services commented on IMPALA-8505: - Commit 9891597e5a0f9a8a290da5295a1343228b7dafef in impala's branch refs/heads/master from Hao Hao [ https://gitbox.apache.org/repos/asf?p=impala.git;h=9891597 ] IMPALA-8505: Disallow setting Kudu table id in ALTER TABLE This commit disallows explicitly setting the Kudu table id property for Kudu tables in a ALTER TABLE set statement. The Kudu table id property is generated when the table is created and should not be altered afterwards. This commit also extracts Kudu-related analyzing tests for table alteration, so that they can be run with or without Kudu/HMS integration enabled. Change-Id: Ibc1f3f87054db5e28f72a5b54ea5b3c040c1bf22 Reviewed-on: http://gerrit.cloudera.org:8080/13465 Reviewed-by: Grant Henke Reviewed-by: Thomas Marshall Reviewed-by: Alexey Serbin Tested-by: Impala Public Jenkins > Support AlterTable DDL with Kudu/HMS integration in Catalogd mode > - > > Key: IMPALA-8505 > URL: https://issues.apache.org/jira/browse/IMPALA-8505 > Project: IMPALA > Issue Type: Sub-task >Reporter: Hao Hao >Assignee: Hao Hao >Priority: Major > > Similar to IMPALA-8504, but for AlterTable DDL. -- 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-8578) Reduce code in metric headers
[ https://issues.apache.org/jira/browse/IMPALA-8578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16856314#comment-16856314 ] ASF subversion and git services commented on IMPALA-8578: - Commit 95a1da2d32ea7b28585ad574b22c2bb9dd921029 in impala's branch refs/heads/master from Tim Armstrong [ https://gitbox.apache.org/repos/asf?p=impala.git;h=95a1da2 ] IMPALA-8578: part 2: move metrics code to .cc files This moves a lot of metric function definitions into .cc files, to reduce the size of compilation units and to reduce the frequency of recompilation required when making changes to metrics. This moves most of the large, non-perf-critical metric functions into .cc files. For template classes, this requires explicitly instantiating all combinations of template parameters that are used in impala, including in tests. Disable weak-template-vtables warning because of spurious warnings on template instantiations. See https://bugs.llvm.org/show_bug.cgi?id=18733 Change-Id: I78ad045ded6e6a7b7524711be9302c26115b97b9 Reviewed-on: http://gerrit.cloudera.org:8080/13501 Reviewed-by: Tim Armstrong Tested-by: Impala Public Jenkins > Reduce code in metric headers > - > > Key: IMPALA-8578 > URL: https://issues.apache.org/jira/browse/IMPALA-8578 > Project: IMPALA > Issue Type: Improvement > Components: Backend >Reporter: Tim Armstrong >Assignee: Tim Armstrong >Priority: Major > > metrics.h and other metric headers are included a lot of places and there is > a lot of code in the header that has very few callers. It appears to be > pulled into several hundred compilation units, increasing the compile time of > each of those and forcing recompilation when the headers are changed. > Some ideas: > * Move function implementations to .cc files. E.g. ToJson() and > ToPrometheus() don't need to be inlined. > * Move MetricGroup to its own file > * Try to see if we can use forward declarations in more places to avoid > including 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-8625) Crash in dockerised tests
Tim Armstrong created IMPALA-8625:
-
Summary: Crash in dockerised tests
Key: IMPALA-8625
URL: https://issues.apache.org/jira/browse/IMPALA-8625
Project: IMPALA
Issue Type: Bug
Components: Backend
Reporter: Tim Armstrong
Assignee: Tim Armstrong
Attachments: impalad.3b630ef7faf3.ubuntu.log.INFO.20190604-185929.11.gz
https://jenkins.impala.io/job/ubuntu-16.04-dockerised-tests/439/
I don't have much in the way of diagnostics, just this fragment in the log
[^impalad.3b630ef7faf3.ubuntu.log.INFO.20190604-185929.11.gz] :
{noformat}
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x7f0f139bc6e0, pid=11, tid=0x7f0ba23b1700
#
# JRE version: OpenJDK Runtime Environment (8.0_212-b03) (build
1.8.0_212-8u212-b03-0ubuntu1.16.04.1-b03)
# Java VM: OpenJDK 64-Bit Server VM (25.212-b03 mixed mode linux-amd64
compressed oops)
# Problematic frame:
# C 0x7f0f139bc6e0
#
# Core dump written. Default location: /opt/impala/core or core.11
#
# An error report file with more information is saved as:
# /tmp/hs_err_pid11.log
74: client_identifier (string) = "query_test/test_insert_parquet.py::T
{noformat}
Tests that were running:
{Noformat}
[gw10] PASSED
query_test/test_scanners.py::TestScannersAllTableFormats::test_hdfs_scanner_profile[batch_size:
0 | debug_action: -1:OPEN:SET_DENY_RESERVATION_PROBABILITY@0.5 | protocol:
beeswax | exec_option: {'batch_size': 0, 'num_nodes': 0,
'disable_codegen_rows_threshold': 0, 'disable_codegen': False,
'abort_on_error': 1, 'exec_single_node_rows_threshold': 0} | table_format:
avro/snap/block]
query_test/test_scanners.py::TestScannersAllTableFormats::test_hdfs_scanner_profile[batch_size:
0 | debug_action: -1:OPEN:SET_DENY_RESERVATION_PROBABILITY@1.0 | protocol:
beeswax | exec_option: {'batch_size': 0, 'num_nodes': 0,
'disable_codegen_rows_threshold': 0, 'disable_codegen': False,
'abort_on_error': 1, 'exec_single_node_rows_threshold': 0} | table_format:
parquet/none]
[gw6] PASSED
query_test/test_scanners.py::TestScannersAllTableFormats::test_string_escaping[batch_size:
16 | debug_action: HDFS_SCANNER_THREAD_CHECK_SOFT_MEM_LIMIT:FAIL@0.5 |
protocol: beeswax | exec_option: {'batch_size': 0, 'num_nodes': 0,
'disable_codegen_rows_threshold': 0, 'disable_codegen': False,
'abort_on_error': 1, 'exec_single_node_rows_threshold': 0} | table_format:
hbase/none]
query_test/test_scanners.py::TestScannersAllTableFormats::test_string_escaping[batch_size:
16 | debug_action: -1:OPEN:SET_DENY_RESERVATION_PROBABILITY@1.0 | protocol:
beeswax | exec_option: {'batch_size': 0, 'num_nodes': 0,
'disable_codegen_rows_threshold': 0, 'disable_codegen': False,
'abort_on_error': 1, 'exec_single_node_rows_threshold': 0} | table_format:
seq/def/block]
[gw3] PASSED
query_test/test_insert_parquet.py::TestHdfsParquetTableWriter::test_int64_timestamp_logical_type[protocol:
beeswax | exec_option: {'batch_size': 0, 'num_nodes': 0,
'disable_codegen_rows_threshold': 0, 'disable_codegen': False,
'abort_on_error': 1, 'exec_single_node_rows_threshold': 0} | table_format:
parquet/none]
query_test/test_insert_parquet.py::TestHdfsParquetTableStatsWriter::test_write_statistics_alltypes[protocol:
beeswax | exec_option: {'batch_size': 0, 'num_nodes': 0,
'disable_codegen_rows_threshold': 0, 'disable_codegen': False,
'abort_on_error': 1, 'exec_single_node_rows_threshold': 0} | table_format:
parquet/none]
[gw6] PASSED
query_test/test_scanners.py::TestScannersAllTableFormats::test_string_escaping[batch_size:
16 | debug_action: -1:OPEN:SET_DENY_RESERVATION_PROBABILITY@1.0 | protocol:
beeswax | exec_option: {'batch_size': 0, 'num_nodes': 0,
'disable_codegen_rows_threshold': 0, 'disable_codegen': False,
'abort_on_error': 1, 'exec_single_node_rows_threshold': 0} | table_format:
seq/def/block]
query_test/test_scanners.py::TestScannersAllTableFormats::test_string_escaping[batch_size:
16 | debug_action: -1:OPEN:SET_DENY_RESERVATION_PROBABILITY@0.5 | protocol:
beeswax | exec_option: {'batch_size': 0, 'num_nodes': 0,
'disable_codegen_rows_threshold': 0, 'disable_codegen': False,
'abort_on_error': 1, 'exec_single_node_rows_threshold': 0} | table_format:
kudu/none]
[gw13] PASSED
query_test/test_join_queries.py::TestTPCHJoinQueries::test_outer_joins[batch_size:
0 | protocol: beeswax | exec_option: {'batch_size': 0, 'num_nodes': 0,
'disable_codegen_rows_threshold': 0, 'disable_codegen': False,
'abort_on_error': 1, 'exec_single_node_rows_threshold': 0} | table_format:
parquet/none]
query_test/test_join_queries.py::TestSemiJoinQueries::test_semi_joins[batch_size:
0 | protocol: beeswax | exec_option: {'batch_size': 0, 'num_nodes': 0,
'disable_codegen_rows_threshold': 0, 'disable_codegen': False,
'abort_on_error': 1, 'exec_single_node_rows_threshold': 0} | table_format:
parquet/none]
[jira] [Created] (IMPALA-8624) Collect coredumps, minidumps and hserr*.log files from dockerised tests
Tim Armstrong created IMPALA-8624: - Summary: Collect coredumps, minidumps and hserr*.log files from dockerised tests Key: IMPALA-8624 URL: https://issues.apache.org/jira/browse/IMPALA-8624 Project: IMPALA Issue Type: Sub-task Components: Infrastructure Reporter: Tim Armstrong Assignee: Tim Armstrong -- 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-8623) Expose HS2 HTTP port in containers
Tim Armstrong created IMPALA-8623: - Summary: Expose HS2 HTTP port in containers Key: IMPALA-8623 URL: https://issues.apache.org/jira/browse/IMPALA-8623 Project: IMPALA Issue Type: Sub-task Reporter: Tim Armstrong Assignee: Tim Armstrong -- 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-8567) Many random catalog consistency issues with catalog v2/event processor
[ https://issues.apache.org/jira/browse/IMPALA-8567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16856156#comment-16856156 ] ASF subversion and git services commented on IMPALA-8567: - Commit 2c5eb89550cb25696c4457e23ce746980eb3c3e4 in impala's branch refs/heads/master from Tim Armstrong [ https://gitbox.apache.org/repos/asf?p=impala.git;h=2c5eb89 ] IMPALA-8567: revert dockerised cluster to catalog v1 Change-Id: Icf60b7ed7a22cc176d68ded1da23e4445750097c Reviewed-on: http://gerrit.cloudera.org:8080/13504 Reviewed-by: Lars Volker Tested-by: Impala Public Jenkins > Many random catalog consistency issues with catalog v2/event processor > -- > > Key: IMPALA-8567 > URL: https://issues.apache.org/jira/browse/IMPALA-8567 > Project: IMPALA > Issue Type: Bug > Components: Frontend >Affects Versions: Impala 3.3.0 >Reporter: Tim Armstrong >Assignee: Vihang Karajgaonkar >Priority: Blocker > Labels: broken-build, catalog, flaky > > [~tlipcon] [~vihangk1] FYI. I'm not sure whether the local catalog or the > event processor is likely to blame here so I'll let you look. The general > theme is tables and databases not existing when they should. > https://jenkins.impala.io/job/ubuntu-16.04-dockerised-tests/289/testReport/junit/metadata.test_refresh_partition/TestRefreshPartition/test_drop_hive_partition_and_refresh_protocol__beeswax___exec_optionbatch_size___0___num_nodes___0___disable_codegen_rows_threshold___5000___disable_codegen___False___abort_on_error___1___exec_single_node_rows_threshold___0table_format__text_none_/ > https://jenkins.impala.io/job/ubuntu-16.04-dockerised-tests/267/testReport/junit/query_test.test_kudu/TestKuduOperations/test_kudu_insert_protocol__beeswax___exec_optionkudu_read_modeREAD_AT_SNAPSHOTbatch_size___0___num_nodes___0___disable_codegen_rows_threshold___0___disable_codegen___False___abort_on_error___1___exec_single_node_rows_threshold___0table_format__text_none_/ > https://jenkins.impala.io/job/ubuntu-16.04-dockerised-tests/286/testReport/junit/metadata.test_metadata_query_statements/TestMetadataQueryStatements/test_describe_db_protocol__beeswax___exec_optionsync_ddl___0___batch_size___0___num_nodes___0___disable_codegen_rows_threshold___0___disable_codegen___False___abort_on_error___1___exec_single_node_rows_threshold___0table_format__text_none_/ > https://jenkins.impala.io/job/ubuntu-16.04-dockerised-tests/286/testReport/junit/metadata.test_hms_integration/TestHmsIntegrationSanity/test_sanity_protocol__beeswax___exec_optionbatch_size___0___num_nodes___0___disable_codegen_rows_threshold___5000___disable_codegen___False___abort_on_error___1___exec_single_node_rows_threshold___0table_format__text_none_/ > https://jenkins.impala.io/job/ubuntu-16.04-dockerised-tests/288/testReport/junit/query_test.test_insert_parquet/TestHdfsParquetTableStatsWriter/test_write_statistics_multiple_row_groups_protocol__beeswax___exec_optionbatch_size___0___num_nodes___0___disable_codegen_rows_threshold___0___disable_codegen___False___abort_on_error___1___exec_single_node_rows_threshold___0table_format__parquet_none_/ > I'll include the output of each job in a follow-on comment. -- 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-8504) Support CreateTable DDL with Kudu/HMS integration in Catalogd mode
[ https://issues.apache.org/jira/browse/IMPALA-8504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16856146#comment-16856146 ] ASF subversion and git services commented on IMPALA-8504: - Commit 6bb404dc35999c250cc9112c19b74ffcf17fe14b in impala's branch refs/heads/master from Hao Hao [ https://gitbox.apache.org/repos/asf?p=impala.git;h=6bb404d ] IMPALA-8504 (part 2): Support CREATE TABLE statement with Kudu/HMS integration This commit supports the actual handling of CREATE TABLE DDL for managed Kudu tables when integration with Hive Metastore is enabled. When Kudu/HMS integration is enabled, for CREATE TABLE statement, Impala can rely on Kudu to create the table in the HMS. Change-Id: Icffe412395f47f5e07d97bad457020770cfa7502 Reviewed-on: http://gerrit.cloudera.org:8080/13375 Reviewed-by: Thomas Marshall Reviewed-by: Grant Henke Tested-by: Thomas Marshall > Support CreateTable DDL with Kudu/HMS integration in Catalogd mode > -- > > Key: IMPALA-8504 > URL: https://issues.apache.org/jira/browse/IMPALA-8504 > Project: IMPALA > Issue Type: Sub-task >Reporter: Hao Hao >Assignee: Hao Hao >Priority: Major > > For both managed and external table, we need to ensure the syntax is correct > and Kudu related table creation DDL is adapted when Kudu/HMS integration is > enabled. -- 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-8578) Reduce code in metric headers
[ https://issues.apache.org/jira/browse/IMPALA-8578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16856147#comment-16856147 ] ASF subversion and git services commented on IMPALA-8578: - Commit e78e6f0c260b342c67e055656d239438bca13288 in impala's branch refs/heads/master from Tim Armstrong [ https://gitbox.apache.org/repos/asf?p=impala.git;h=e78e6f0 ] IMPALA-8578: part 1: reduce dependencies on *metrics.h Before this patch there were 100s of compilation units that pulled in metrics.h and the significant amount of code in that header. It was painfully slow to recompile after changes to that file. The patch reduces that significantly and mostly eliminates transitive inclusions via other headers. * Add metrics-fwds.h with forward declarations needed to have pointers to the various classes. * Update headers to use metrics-fwds.h and move includes of *metrics.h to the .cc files. * Add includes, etc to fix compilation errors where files depended on transitively-included headers from *metrics.h This shaved about 30s off the build time on Jenkins - about a 4% speedup. I didn't end up removing anything from the headers - that is a bit more work since most of the classes are templatized and need to be explicitly instantiated in .cc files if functions are not all defined in the headers. Testing: Ran a core build Change-Id: Ie2942366cab5421f2db7c27e7da712ea6f775fdb Reviewed-on: http://gerrit.cloudera.org:8080/13491 Reviewed-by: Impala Public Jenkins Tested-by: Tim Armstrong > Reduce code in metric headers > - > > Key: IMPALA-8578 > URL: https://issues.apache.org/jira/browse/IMPALA-8578 > Project: IMPALA > Issue Type: Improvement > Components: Backend >Reporter: Tim Armstrong >Assignee: Tim Armstrong >Priority: Major > > metrics.h and other metric headers are included a lot of places and there is > a lot of code in the header that has very few callers. It appears to be > pulled into several hundred compilation units, increasing the compile time of > each of those and forcing recompilation when the headers are changed. > Some ideas: > * Move function implementations to .cc files. E.g. ToJson() and > ToPrometheus() don't need to be inlined. > * Move MetricGroup to its own file > * Try to see if we can use forward declarations in more places to avoid > including 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] [Resolved] (IMPALA-7930) Crash in thrift-server-test
[
https://issues.apache.org/jira/browse/IMPALA-7930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Tauber-Marshall resolved IMPALA-7930.
Resolution: Cannot Reproduce
> Crash in thrift-server-test
> ---
>
> Key: IMPALA-7930
> URL: https://issues.apache.org/jira/browse/IMPALA-7930
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
>Affects Versions: Impala 3.2.0
>Reporter: Lars Volker
>Assignee: Thomas Tauber-Marshall
>Priority: Critical
> Labels: broken-build, flaky
>
> I've seen a crash in thrift-server-test during an exhaustive test run.
> Unfortunately the core file indicated that it was written by a directory,
> which caused the automatic core dump resolution to fail. Here's the resolved
> minidump:
> {noformat}
> Crash reason: SIGABRT
> Crash address: 0x7d11d19
> Process uptime: not available
> Thread 0 (crashed)
> 0 libc-2.17.so + 0x351f7
> rax = 0x rdx = 0x0006
> rcx = 0x rbx = 0x7f1e65876000
> rsi = 0x1d19 rdi = 0x1d19
> rbp = 0x7f1e61dbde68 rsp = 0x7fffc22796d8
> r8 = 0x000a1a10r9 = 0xfefefefefeff092d
> r10 = 0x0008 r11 = 0x0202
> r12 = 0x029dca31 r13 = 0x033a5e00
> r14 = 0x r15 = 0x
> rip = 0x7f1e61c721f7
> Found by: given as instruction pointer in context
> 1 libc-2.17.so + 0x368e8
> rsp = 0x7fffc22796e0 rip = 0x7f1e61c738e8
> Found by: stack scanning
> 2 libc-2.17.so + 0x17df70
> rsp = 0x7fffc2279770 rip = 0x7f1e61dbaf70
> Found by: stack scanning
> 3 thrift-server-test!_fini + 0xdf918
> rsp = 0x7fffc2279778 rip = 0x02ab0288
> Found by: stack scanning
> 4 libc-2.17.so + 0x2fbc3
> rsp = 0x7fffc2279790 rip = 0x7f1e61c6cbc3
> Found by: stack scanning
> 5
> thrift-server-test!testing::internal::TestEventRepeater::OnTestProgramEnd(testing::UnitTest
> const&) + 0x55
> rsp = 0x7fffc22797b0 rip = 0x028711f5
> Found by: stack scanning
> 6 libc-2.17.so + 0x17df70
> rbx = 0x rbp = 0x
> rsp = 0x7fffc22797e0 r12 = 0x
> r13 = 0x0005 rip = 0x7f1e61dbaf70
> Found by: call frame info
> 7 thrift-server-test!_fini + 0xc0c1
> rsp = 0x7fffc22797f0 rip = 0x029dca31
> Found by: stack scanning
> 8 thrift-server-test!_fini + 0x9d5490
> rsp = 0x7fffc22797f8 rip = 0x033a5e00
> Found by: stack scanning
> 9 libc-2.17.so + 0x180e68
> rsp = 0x7fffc2279808 rip = 0x7f1e61dbde68
> Found by: stack scanning
> 10 libc-2.17.so + 0x2e266
> rsp = 0x7fffc2279810 rip = 0x7f1e61c6b266
> Found by: stack scanning
> 11 thrift-server-test!_fini + 0x9d5490
> rsp = 0x7fffc2279818 rip = 0x033a5e00
> Found by: stack scanning
> 12 libc-2.17.so + 0x17df70
> rsp = 0x7fffc2279820 rip = 0x7f1e61dbaf70
> Found by: stack scanning
> 13 thrift-server-test!_fini + 0xc0c1
> rsp = 0x7fffc2279828 rip = 0x029dca31
> Found by: stack scanning
> 14 thrift-server-test!_fini + 0xdf918
> rsp = 0x7fffc2279840 rip = 0x02ab0288
> Found by: stack scanning
> 15 thrift-server-test!_fini + 0x9d5490
> rsp = 0x7fffc2279850 rip = 0x033a5e00
> Found by: stack scanning
> 16 thrift-server-test!_fini + 0xc0c1
> rsp = 0x7fffc2279860 rip = 0x029dca31
> Found by: stack scanning
> 17 thrift-server-test!_fini + 0x9d5490
> rsp = 0x7fffc2279870 rip = 0x033a5e00
> Found by: stack scanning
> 18 thrift-server-test!_fini + 0xc0c1
> rsp = 0x7fffc2279878 rip = 0x029dca31
> Found by: stack scanning
> 19 thrift-server-test!_fini + 0xdf918
> rsp = 0x7fffc2279880 rip = 0x02ab0288
> Found by: stack scanning
> 20 libc-2.17.so + 0x2e312
> rsp = 0x7fffc2279890 rip = 0x7f1e61c6b312
> Found by: stack scanning
> 21
> thrift-server-test!boost::shared_array::~shared_array()
> + 0x70
> rsp = 0x7fffc22798b0 rip = 0x02719b40
> Found by: stack scanning
> 22
> thrift-server-test!boost::detail::sp_counted_impl_p::dispose()
> + 0x4f
> rsp = 0x7fffc22798c0 rip = 0x0271e1af
> Found by: stack scanning
> 23
> thrift-server-test!boost::detail::sp_counted_impl_pd boost::checked_array_deleter
> >::dispose() + 0xaa
> rbx = 0x042f7128 rsp = 0x7fffc22798d0
> rip = 0x02719cfa
> Found by: call frame info
> 24
> thrift-server-test!boost::shared_array::~shared_array()
> +
[jira] [Resolved] (IMPALA-7326) test_kudu_partition_ddl failed with exception message: "Table already exists"
[
https://issues.apache.org/jira/browse/IMPALA-7326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Tauber-Marshall resolved IMPALA-7326.
Resolution: Cannot Reproduce
> test_kudu_partition_ddl failed with exception message: "Table already exists"
> -
>
> Key: IMPALA-7326
> URL: https://issues.apache.org/jira/browse/IMPALA-7326
> Project: IMPALA
> Issue Type: Bug
> Components: Catalog
>Affects Versions: Impala 3.1.0, Impala 3.2.0
>Reporter: Michael Ho
>Assignee: Thomas Tauber-Marshall
>Priority: Critical
> Labels: broken-build, flaky, kudu
>
> cc'ing [~twm378]. Does it look like some known issue ? Putting it in the
> catalog category for now but please feel free to update the component as you
> see fit.
> {noformat}
> query_test/test_kudu.py:96: in test_kudu_partition_ddl
> self.run_test_case('QueryTest/kudu_partition_ddl', vector,
> use_db=unique_database)
> common/impala_test_suite.py:397: in run_test_case
> result = self.__execute_query(target_impalad_client, query, user=user)
> common/impala_test_suite.py:612: in __execute_query
> return impalad_client.execute(query, user=user)
> common/impala_connection.py:160: in execute
> return self.__beeswax_client.execute(sql_stmt, user=user)
> beeswax/impala_beeswax.py:173: in execute
> handle = self.__execute_query(query_string.strip(), user=user)
> beeswax/impala_beeswax.py:339: in __execute_query
> handle = self.execute_query_async(query_string, user=user)
> beeswax/impala_beeswax.py:335: in execute_query_async
> return self.__do_rpc(lambda: self.imp_service.query(query,))
> beeswax/impala_beeswax.py:460: in __do_rpc
> raise ImpalaBeeswaxException(self.__build_error_message(b), b)
> E ImpalaBeeswaxException: ImpalaBeeswaxException:
> EINNER EXCEPTION:
> EMESSAGE: ImpalaRuntimeException: Error creating Kudu table
> 'impala::test_kudu_partition_ddl_7e04e8f9.simple_hash_range'
> E CAUSED BY: NonRecoverableException: Table
> impala::test_kudu_partition_ddl_7e04e8f9.simple_hash_range already exists
> with id 3e81a4ceff27471cad9fcb3bc0b977c3
> {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-8560) Prometheus metrics support in Impala
[ https://issues.apache.org/jira/browse/IMPALA-8560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-8560. --- Resolution: Fixed Fix Version/s: Impala 3.3.0 > Prometheus metrics support in Impala > > > Key: IMPALA-8560 > URL: https://issues.apache.org/jira/browse/IMPALA-8560 > Project: IMPALA > Issue Type: Bug > Components: Backend >Reporter: Harshil Shah >Assignee: Harshil Shah >Priority: Major > Fix For: Impala 3.3.0 > > > -- This change adds Prometheus text explosion format metric generation in > impala. > -- more details about text explosion can be found here: > [https://prometheus.io/docs/instrumenting/exposition_formats/#text-based-format] -- 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-8622) Generate list of docker images generated by the build
[
https://issues.apache.org/jira/browse/IMPALA-8622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong reassigned IMPALA-8622:
-
Assignee: Harshil Shah (was: Tim Armstrong)
> Generate list of docker images generated by the build
> -
>
> Key: IMPALA-8622
> URL: https://issues.apache.org/jira/browse/IMPALA-8622
> Project: IMPALA
> Issue Type: Sub-task
> Components: Infrastructure
>Reporter: Tim Armstrong
>Assignee: Harshil Shah
>Priority: Major
> Labels: docker
>
> Some consumers of the Impala docker images will want to publish them to a
> repo. Currently they would have to hardcode a list of the docker images
> produced by the Impala build to publish them, or do something brittle like
> "docker image ls" to deduce what images were built.
> It would be useful if the build produced a list of the images in some
> consumable format that would be updated (either manually or automatically)
> when the set of images changes. If it needs to be manually updated, we should
> have some kind of check to verify that it isn't stale.
> One option is to produce JSON, something like:
> {noformat}
> {
> “docker_images”: {
>“impala_base”: “$docker_registry/impala_base”,
>” impalad_coord_exec”: “$docker_registry/impalad_coord_exec”,
>
> }
> }
> {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-8560) Prometheus metrics support in Impala
[ https://issues.apache.org/jira/browse/IMPALA-8560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16856120#comment-16856120 ] Tim Armstrong commented on IMPALA-8560: --- Thanks for the contribution [~harshil_shah]. I just added you as a contributor to the project so you we can assign issues to you ( we missed that step earlier) > Prometheus metrics support in Impala > > > Key: IMPALA-8560 > URL: https://issues.apache.org/jira/browse/IMPALA-8560 > Project: IMPALA > Issue Type: Bug > Components: Backend >Reporter: Harshil Shah >Assignee: Harshil Shah >Priority: Major > > -- This change adds Prometheus text explosion format metric generation in > impala. > -- more details about text explosion can be found here: > [https://prometheus.io/docs/instrumenting/exposition_formats/#text-based-format] -- 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-8560) Prometheus metrics support in Impala
[ https://issues.apache.org/jira/browse/IMPALA-8560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong reassigned IMPALA-8560: - Assignee: Harshil Shah > Prometheus metrics support in Impala > > > Key: IMPALA-8560 > URL: https://issues.apache.org/jira/browse/IMPALA-8560 > Project: IMPALA > Issue Type: Bug > Components: Backend >Reporter: Harshil Shah >Assignee: Harshil Shah >Priority: Major > > -- This change adds Prometheus text explosion format metric generation in > impala. > -- more details about text explosion can be found here: > [https://prometheus.io/docs/instrumenting/exposition_formats/#text-based-format] -- 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-8622) Generate list of docker images generated by the build
[
https://issues.apache.org/jira/browse/IMPALA-8622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong updated IMPALA-8622:
--
Description:
Some consumers of the Impala docker images will want to publish them to a repo.
Currently they would have to hardcode a list of the docker images produced by
the Impala build to publish them, or do something brittle like "docker image
ls" to deduce what images were built.
It would be useful if the build produced a list of the images in some
consumable format that would be updated (either manually or automatically) when
the set of images changes. If it needs to be manually updated, we should have
some kind of check to verify that it isn't stale.
One option is to produce JSON, something like:
{noformat}
{
“docker_images”: {
“impala_base”: “$docker_registry/impala_base”,
” impalad_coord_exec”: “$docker_registry/impalad_coord_exec”,
}
}
{noformat}
was:
Some consumers of the Impala docker images will want to publish them to a repo.
Currently they would have to hardcode a list of the docker images produced by
the Impala build to publish them, or do something brittle like "docker image
ls" to deduce what images were built.
It would be useful if the build produced a list of the images in some
consumable format that would be updated (either manually or automatically) when
the set of images changes. If it needs to be manually updated, we should have
some kind of check to verify that it isn't stale.
> Generate list of docker images generated by the build
> -
>
> Key: IMPALA-8622
> URL: https://issues.apache.org/jira/browse/IMPALA-8622
> Project: IMPALA
> Issue Type: Sub-task
> Components: Infrastructure
>Reporter: Tim Armstrong
>Assignee: Tim Armstrong
>Priority: Major
> Labels: docker
>
> Some consumers of the Impala docker images will want to publish them to a
> repo. Currently they would have to hardcode a list of the docker images
> produced by the Impala build to publish them, or do something brittle like
> "docker image ls" to deduce what images were built.
> It would be useful if the build produced a list of the images in some
> consumable format that would be updated (either manually or automatically)
> when the set of images changes. If it needs to be manually updated, we should
> have some kind of check to verify that it isn't stale.
> One option is to produce JSON, something like:
> {noformat}
> {
> “docker_images”: {
>“impala_base”: “$docker_registry/impala_base”,
>” impalad_coord_exec”: “$docker_registry/impalad_coord_exec”,
>
> }
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Created] (IMPALA-8622) Generate list of docker images generated by the build
Tim Armstrong created IMPALA-8622: - Summary: Generate list of docker images generated by the build Key: IMPALA-8622 URL: https://issues.apache.org/jira/browse/IMPALA-8622 Project: IMPALA Issue Type: Sub-task Components: Infrastructure Reporter: Tim Armstrong Assignee: Tim Armstrong Some consumers of the Impala docker images will want to publish them to a repo. Currently they would have to hardcode a list of the docker images produced by the Impala build to publish them, or do something brittle like "docker image ls" to deduce what images were built. It would be useful if the build produced a list of the images in some consumable format that would be updated (either manually or automatically) when the set of images changes. If it needs to be manually updated, we should have some kind of check to verify that it isn't stale. -- 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-8621) Flaky build on impala.jenkins.io - mvn downloading kerby
Tim Armstrong created IMPALA-8621:
-
Summary: Flaky build on impala.jenkins.io - mvn downloading kerby
Key: IMPALA-8621
URL: https://issues.apache.org/jira/browse/IMPALA-8621
Project: IMPALA
Issue Type: Bug
Components: Infrastructure
Affects Versions: Impala 3.3.0
Reporter: Tim Armstrong
{noformat}
[ERROR] Failed to execute goal on project yarn-extras: Could not resolve
dependencies for project org.apache.impala:yarn-extras:jar:0.1-SNAPSHOT: Failed
to collect dependencies at
org.apache.hadoop:hadoop-common:jar:3.0.0-cdh6.x-SNAPSHOT ->
org.apache.hadoop:hadoop-auth:jar:3.0.0-cdh6.x-SNAPSHOT ->
org.apache.kerby:kerb-simplekdc:jar:1.0.0 ->
org.apache.kerby:kerb-client:jar:1.0.0 ->
org.apache.kerby:kerb-common:jar:1.0.0 ->
org.apache.kerby:kerb-crypto:jar:1.0.0: Failed to read artifact descriptor for
org.apache.kerby:kerb-crypto:jar:1.0.0: Could not transfer artifact
org.apache.kerby:kerb-crypto:pom:1.0.0 from/to impala.cdp.repo
(https://native-toolchain.s3.amazonaws.com/build/cdp_components/1056671/maven):
Access denied to:
https://native-toolchain.s3.amazonaws.com/build/cdp_components/1056671/maven/org/apache/kerby/kerb-crypto/1.0.0/kerb-crypto-1.0.0.pom,
ReasonPhrase: Forbidden. -> [Help 1]
{noformat}
https://jenkins.impala.io/job/ubuntu-16.04-dockerised-tests/433/
Only saw this once. Filing to track if it reoccurs.
--
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-8567) Many random catalog consistency issues with catalog v2/event processor
[ https://issues.apache.org/jira/browse/IMPALA-8567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16855881#comment-16855881 ] Tim Armstrong commented on IMPALA-8567: --- Posted https://gerrit.cloudera.org/#/c/13504/ to revert to metadata v1 > Many random catalog consistency issues with catalog v2/event processor > -- > > Key: IMPALA-8567 > URL: https://issues.apache.org/jira/browse/IMPALA-8567 > Project: IMPALA > Issue Type: Bug > Components: Frontend >Affects Versions: Impala 3.3.0 >Reporter: Tim Armstrong >Assignee: Vihang Karajgaonkar >Priority: Blocker > Labels: broken-build, catalog, flaky > > [~tlipcon] [~vihangk1] FYI. I'm not sure whether the local catalog or the > event processor is likely to blame here so I'll let you look. The general > theme is tables and databases not existing when they should. > https://jenkins.impala.io/job/ubuntu-16.04-dockerised-tests/289/testReport/junit/metadata.test_refresh_partition/TestRefreshPartition/test_drop_hive_partition_and_refresh_protocol__beeswax___exec_optionbatch_size___0___num_nodes___0___disable_codegen_rows_threshold___5000___disable_codegen___False___abort_on_error___1___exec_single_node_rows_threshold___0table_format__text_none_/ > https://jenkins.impala.io/job/ubuntu-16.04-dockerised-tests/267/testReport/junit/query_test.test_kudu/TestKuduOperations/test_kudu_insert_protocol__beeswax___exec_optionkudu_read_modeREAD_AT_SNAPSHOTbatch_size___0___num_nodes___0___disable_codegen_rows_threshold___0___disable_codegen___False___abort_on_error___1___exec_single_node_rows_threshold___0table_format__text_none_/ > https://jenkins.impala.io/job/ubuntu-16.04-dockerised-tests/286/testReport/junit/metadata.test_metadata_query_statements/TestMetadataQueryStatements/test_describe_db_protocol__beeswax___exec_optionsync_ddl___0___batch_size___0___num_nodes___0___disable_codegen_rows_threshold___0___disable_codegen___False___abort_on_error___1___exec_single_node_rows_threshold___0table_format__text_none_/ > https://jenkins.impala.io/job/ubuntu-16.04-dockerised-tests/286/testReport/junit/metadata.test_hms_integration/TestHmsIntegrationSanity/test_sanity_protocol__beeswax___exec_optionbatch_size___0___num_nodes___0___disable_codegen_rows_threshold___5000___disable_codegen___False___abort_on_error___1___exec_single_node_rows_threshold___0table_format__text_none_/ > https://jenkins.impala.io/job/ubuntu-16.04-dockerised-tests/288/testReport/junit/query_test.test_insert_parquet/TestHdfsParquetTableStatsWriter/test_write_statistics_multiple_row_groups_protocol__beeswax___exec_optionbatch_size___0___num_nodes___0___disable_codegen_rows_threshold___0___disable_codegen___False___abort_on_error___1___exec_single_node_rows_threshold___0table_format__parquet_none_/ > I'll include the output of each job in a follow-on comment. -- 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-5967) Impala process hangs in breakpad exception handler
[
https://issues.apache.org/jira/browse/IMPALA-5967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong resolved IMPALA-5967.
---
Resolution: Cannot Reproduce
> Impala process hangs in breakpad exception handler
> --
>
> Key: IMPALA-5967
> URL: https://issues.apache.org/jira/browse/IMPALA-5967
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
>Affects Versions: Impala 2.11.0
>Reporter: Tim Armstrong
>Assignee: Lars Volker
>Priority: Major
> Attachments: gdb.txt
>
>
> I managed to reproduce this issue by accident locally. I believe we've seen
> it before but I'm not sure if we have an open JIRA for it.
> With this branch I was able to trigger the bug:
> https://github.com/timarmstrong/incubator-impala/tree/buggy-avro-trigger-breakpad-hang
> By running this from impala-shell.sh
> {code}
> set num_nodes=1;
> set disable_codegen=0;
> set disable_codegen_rows_threshold=0;
> use functional_avro;
> select count(*),
> sum(id)
> from alltypesagg
> where id % 2 = 0 and day is not null;
> {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-5967) Impala process hangs in breakpad exception handler
[
https://issues.apache.org/jira/browse/IMPALA-5967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16855878#comment-16855878
]
Tim Armstrong commented on IMPALA-5967:
---
[~lv] I think we can close until we see it again.
> Impala process hangs in breakpad exception handler
> --
>
> Key: IMPALA-5967
> URL: https://issues.apache.org/jira/browse/IMPALA-5967
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
>Affects Versions: Impala 2.11.0
>Reporter: Tim Armstrong
>Assignee: Lars Volker
>Priority: Major
> Attachments: gdb.txt
>
>
> I managed to reproduce this issue by accident locally. I believe we've seen
> it before but I'm not sure if we have an open JIRA for it.
> With this branch I was able to trigger the bug:
> https://github.com/timarmstrong/incubator-impala/tree/buggy-avro-trigger-breakpad-hang
> By running this from impala-shell.sh
> {code}
> set num_nodes=1;
> set disable_codegen=0;
> set disable_codegen_rows_threshold=0;
> use functional_avro;
> select count(*),
> sum(id)
> from alltypesagg
> where id % 2 = 0 and day is not null;
> {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] [Resolved] (IMPALA-4047) Remove "CDH" from Impala
[ https://issues.apache.org/jira/browse/IMPALA-4047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Volker resolved IMPALA-4047. - Resolution: Fixed > Remove "CDH" from Impala > > > Key: IMPALA-4047 > URL: https://issues.apache.org/jira/browse/IMPALA-4047 > Project: IMPALA > Issue Type: Task > Components: Infrastructure >Affects Versions: Impala 2.7.0 >Reporter: Jim Apple >Assignee: Lars Volker >Priority: Major > Labels: asf > > Impala is an Apache (incubating) project, and "CDH"/"cdh" should be removed > from shell scripts and config files and so on. -- 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-7117) Lower debug level for HDFS S3 connector back to INFO
[ https://issues.apache.org/jira/browse/IMPALA-7117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16855849#comment-16855849 ] Lars Volker commented on IMPALA-7117: - [[~joemcdonnell], [~stakiar] - Looks like this one fell through the cracks more than once but the log level increase only had an effect during tests. Should we keep it at "debug"? > Lower debug level for HDFS S3 connector back to INFO > > > Key: IMPALA-7117 > URL: https://issues.apache.org/jira/browse/IMPALA-7117 > Project: IMPALA > Issue Type: Improvement > Components: Frontend >Affects Versions: Impala 2.13.0, Impala 3.1.0 >Reporter: Lars Volker >Assignee: Lars Volker >Priority: Blocker > Labels: s3 > > This change will increase the log level for the HDFS S3 connector to DEBUG to > help with IMPALA-6910 and IMPALA-7070. Before the next release we need to > lower it again. > https://gerrit.cloudera.org/#/c/10596/ > I'm making this a P1 to remind us that we must do this before cutting a > release. -- 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-6951) java7 vs. java8 warning prevents installation of impala-python on test machines
[
https://issues.apache.org/jira/browse/IMPALA-6951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Volker resolved IMPALA-6951.
-
Resolution: Fixed
> java7 vs. java8 warning prevents installation of impala-python on test
> machines
> ---
>
> Key: IMPALA-6951
> URL: https://issues.apache.org/jira/browse/IMPALA-6951
> Project: IMPALA
> Issue Type: Bug
>Reporter: Michael Brown
>Assignee: Lars Volker
>Priority: Major
>
> Commit {{22c7ded07eb2710aba3e1aa07ed7ec1a448f7c61}} now prevents the
> installation of impala-python on a test machine wanting to run tests against
> an Impala cluster. It was very convenient to be able to install impala-python
> and run tests like the stress test regardless of the Java version on the host.
> In order to install impala-python, one must source impala-config.sh. When the
> failpoint is there, then impala-python now MUST have Java 8. This is a burden
> to update.
--
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-5967) Impala process hangs in breakpad exception handler
[
https://issues.apache.org/jira/browse/IMPALA-5967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16855785#comment-16855785
]
Lars Volker commented on IMPALA-5967:
-
[~tarmstrong] - A lot has changed in the past 18 months. Do you think this is
still worth investigating?
> Impala process hangs in breakpad exception handler
> --
>
> Key: IMPALA-5967
> URL: https://issues.apache.org/jira/browse/IMPALA-5967
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
>Affects Versions: Impala 2.11.0
>Reporter: Tim Armstrong
>Assignee: Lars Volker
>Priority: Major
> Attachments: gdb.txt
>
>
> I managed to reproduce this issue by accident locally. I believe we've seen
> it before but I'm not sure if we have an open JIRA for it.
> With this branch I was able to trigger the bug:
> https://github.com/timarmstrong/incubator-impala/tree/buggy-avro-trigger-breakpad-hang
> By running this from impala-shell.sh
> {code}
> set num_nodes=1;
> set disable_codegen=0;
> set disable_codegen_rows_threshold=0;
> use functional_avro;
> select count(*),
> sum(id)
> from alltypesagg
> where id % 2 = 0 and day is not null;
> {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] [Closed] (IMPALA-8613) AnalyzeKuduDDLTest broken in S3 environment
[ https://issues.apache.org/jira/browse/IMPALA-8613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Csaba Ringhofer closed IMPALA-8613. --- Resolution: Fixed Fix Version/s: Impala 3.3.0 Solved in https://gerrit.cloudera.org/#/c/13500/ > AnalyzeKuduDDLTest broken in S3 environment > --- > > Key: IMPALA-8613 > URL: https://issues.apache.org/jira/browse/IMPALA-8613 > Project: IMPALA > Issue Type: Bug > Components: Frontend, Infrastructure >Affects Versions: Impala 3.3.0 >Reporter: Csaba Ringhofer >Priority: Critical > Fix For: Impala 3.3.0 > > > The following tests are broken in S3: > org.apache.impala.analysis.AnalyzeKuduDDLTest.TestCreateManagedKuduTable(AnalyzeKuduDDLTest.java:213) > org.apache.impala.analysis.AnalyzeKuduDDLTest.TestCreateExternalKuduTable(AnalyzeKuduDDLTest.java:482) > both have the following error: > got error: > The specified cache pool does not exist: testPool > expected: > A Kudu table cannot be cached in HDFS. -- 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-8612) NPE when DropTableOrViewStmt analysis leaves serverName_ NULL
[ https://issues.apache.org/jira/browse/IMPALA-8612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Kaszab reassigned IMPALA-8612: Assignee: Gabor Kaszab > NPE when DropTableOrViewStmt analysis leaves serverName_ NULL > - > > Key: IMPALA-8612 > URL: https://issues.apache.org/jira/browse/IMPALA-8612 > Project: IMPALA > Issue Type: Bug > Components: Frontend >Affects Versions: Impala 2.12.0, Impala 3.2.0 >Reporter: Gabor Kaszab >Assignee: Gabor Kaszab >Priority: Critical > > This line is skipped when analyzer.getTable() throws few lines above: > https://github.com/apache/impala/blob/cd30949102425e28adadb51232653d910ac8422f/fe/src/main/java/org/apache/impala/analysis/DropTableOrViewStmt.java#L117 > As a result a drop table statement (with permissions ON) can throw > NullPointerException here: > https://github.com/apache/impala/blob/master/fe/src/main/java/org/apache/impala/authorization/sentry/SentryCatalogdAuthorizationManager.java#L381 -- 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-8612) NPE when DropTableOrViewStmt analysis leaves serverName_ NULL
[ https://issues.apache.org/jira/browse/IMPALA-8612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-8612 started by Gabor Kaszab. > NPE when DropTableOrViewStmt analysis leaves serverName_ NULL > - > > Key: IMPALA-8612 > URL: https://issues.apache.org/jira/browse/IMPALA-8612 > Project: IMPALA > Issue Type: Bug > Components: Frontend >Affects Versions: Impala 2.12.0, Impala 3.2.0 >Reporter: Gabor Kaszab >Assignee: Gabor Kaszab >Priority: Critical > > This line is skipped when analyzer.getTable() throws few lines above: > https://github.com/apache/impala/blob/cd30949102425e28adadb51232653d910ac8422f/fe/src/main/java/org/apache/impala/analysis/DropTableOrViewStmt.java#L117 > As a result a drop table statement (with permissions ON) can throw > NullPointerException here: > https://github.com/apache/impala/blob/master/fe/src/main/java/org/apache/impala/authorization/sentry/SentryCatalogdAuthorizationManager.java#L381 -- 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-8620) Add compression codecs as table/column properties
Abhishek Rawat created IMPALA-8620: -- Summary: Add compression codecs as table/column properties Key: IMPALA-8620 URL: https://issues.apache.org/jira/browse/IMPALA-8620 Project: IMPALA Issue Type: Improvement Components: Backend Reporter: Abhishek Rawat Assignee: Abhishek Rawat COMPRESSION_CODEC is supported as a query option. It probably makes sense to provide a finer granularity control on the scope of compression such as table and/or even columns. There could also be scenarios where a select few columns (such as variable length strings) could be compressed while others (such as integer family columns) remain uncompressed for performance. Parquet's unit of compression is a page and so it makes sense to provide capability to compress a given column. -- 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-8619) Add interoperability tests for parquet/zstd
Abhishek Rawat created IMPALA-8619: -- Summary: Add interoperability tests for parquet/zstd Key: IMPALA-8619 URL: https://issues.apache.org/jira/browse/IMPALA-8619 Project: IMPALA Issue Type: Test Components: Backend Reporter: Abhishek Rawat Assignee: Abhishek Rawat Add smoke tests in the upstream repo to test Hive/Impala interoperability when using parquet/zstd format. -- 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
