[jira] [Commented] (IMPALA-8870) Bump guava version when building against Hive 3
[
https://issues.apache.org/jira/browse/IMPALA-8870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16910183#comment-16910183
]
Vihang Karajgaonkar commented on IMPALA-8870:
-
Took a quick look at this. Its not just simply bumping up the version to what
hive is using since there are API changes between 14 and version 19 (what hive
uses). This will require code changes as well.
> Bump guava version when building against Hive 3
> ---
>
> Key: IMPALA-8870
> URL: https://issues.apache.org/jira/browse/IMPALA-8870
> Project: IMPALA
> Issue Type: Improvement
> Components: Infrastructure
>Affects Versions: Impala 3.3.0
>Reporter: Tim Armstrong
>Assignee: Vihang Karajgaonkar
>Priority: Blocker
>
> Guava is pinned to 14.01
> https://github.com/apache/impala/blob/8094811/impala-parent/pom.xml#L59
> {code}
>
> 14.0.1
> {code}
> I think this has likely changed in Hive 3 and we probably want to revisit
> this.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Resolved] (IMPALA-8874) TestEventProcessing.test_empty_partition_events_transactional seems flaky
[ https://issues.apache.org/jira/browse/IMPALA-8874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vihang Karajgaonkar resolved IMPALA-8874. - Resolution: Fixed Fix Version/s: Impala 3.3.0 Hi [~fangyurao] Can you please confirm if this test is working since the fix? > TestEventProcessing.test_empty_partition_events_transactional seems flaky > - > > Key: IMPALA-8874 > URL: https://issues.apache.org/jira/browse/IMPALA-8874 > Project: IMPALA > Issue Type: Bug > Components: Infrastructure >Reporter: Fang-Yu Rao >Assignee: Vihang Karajgaonkar >Priority: Blocker > Fix For: Impala 3.3.0 > > > TestEventProcessing.test_empty_partition_events_transactional seems flaky > after a recent patch due to > https://issues.apache.org/jira/browse/IMPALA-8847. Create a JIRA to track > this failed test. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Resolved] (IMPALA-8874) TestEventProcessing.test_empty_partition_events_transactional seems flaky
[ https://issues.apache.org/jira/browse/IMPALA-8874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vihang Karajgaonkar resolved IMPALA-8874. - Resolution: Fixed Fix Version/s: Impala 3.3.0 Hi [~fangyurao] Can you please confirm if this test is working since the fix? > TestEventProcessing.test_empty_partition_events_transactional seems flaky > - > > Key: IMPALA-8874 > URL: https://issues.apache.org/jira/browse/IMPALA-8874 > Project: IMPALA > Issue Type: Bug > Components: Infrastructure >Reporter: Fang-Yu Rao >Assignee: Vihang Karajgaonkar >Priority: Blocker > Fix For: Impala 3.3.0 > > > TestEventProcessing.test_empty_partition_events_transactional seems flaky > after a recent patch due to > https://issues.apache.org/jira/browse/IMPALA-8847. Create a JIRA to track > this failed test. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (IMPALA-8874) TestEventProcessing.test_empty_partition_events_transactional seems flaky
[ https://issues.apache.org/jira/browse/IMPALA-8874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16910180#comment-16910180 ] Vihang Karajgaonkar commented on IMPALA-8874: - This was fixed in https://github.com/apache/impala/commit/70b0492e6b0322ec5b673a2ab20e02d9e35d0a93 > TestEventProcessing.test_empty_partition_events_transactional seems flaky > - > > Key: IMPALA-8874 > URL: https://issues.apache.org/jira/browse/IMPALA-8874 > Project: IMPALA > Issue Type: Bug > Components: Infrastructure >Reporter: Fang-Yu Rao >Assignee: Vihang Karajgaonkar >Priority: Blocker > > TestEventProcessing.test_empty_partition_events_transactional seems flaky > after a recent patch due to > https://issues.apache.org/jira/browse/IMPALA-8847. Create a JIRA to track > this failed test. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Assigned] (IMPALA-8870) Bump guava version when building against Hive 3
[
https://issues.apache.org/jira/browse/IMPALA-8870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vihang Karajgaonkar reassigned IMPALA-8870:
---
Assignee: Vihang Karajgaonkar
> Bump guava version when building against Hive 3
> ---
>
> Key: IMPALA-8870
> URL: https://issues.apache.org/jira/browse/IMPALA-8870
> Project: IMPALA
> Issue Type: Improvement
> Components: Infrastructure
>Affects Versions: Impala 3.3.0
>Reporter: Tim Armstrong
>Assignee: Vihang Karajgaonkar
>Priority: Blocker
>
> Guava is pinned to 14.01
> https://github.com/apache/impala/blob/8094811/impala-parent/pom.xml#L59
> {code}
>
> 14.0.1
> {code}
> I think this has likely changed in Hive 3 and we probably want to revisit
> this.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Created] (IMPALA-8876) Benchmark zstd and lz4 compression codecs
Abhishek Rawat created IMPALA-8876: -- Summary: Benchmark zstd and lz4 compression codecs Key: IMPALA-8876 URL: https://issues.apache.org/jira/browse/IMPALA-8876 Project: IMPALA Issue Type: Documentation Affects Versions: Impala 3.4.0 Reporter: Abhishek Rawat Assignee: Abhishek Rawat -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (IMPALA-8511) Impala Doc: Incompatible changes in Impala 3.3
[ https://issues.apache.org/jira/browse/IMPALA-8511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16910166#comment-16910166 ] Alex Rodoni commented on IMPALA-8511: - [~stiga-huang] Is there any incompatible changes in this release? I am not aware of any. So if I don't hear from you, I will close this ticket. Is that okat with you? > Impala Doc: Incompatible changes in Impala 3.3 > -- > > Key: IMPALA-8511 > URL: https://issues.apache.org/jira/browse/IMPALA-8511 > Project: IMPALA > Issue Type: Task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Labels: future_release_doc, in_33 > -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-8813) Impala Doc: Support Hive ACID Insert-only Tables
[ https://issues.apache.org/jira/browse/IMPALA-8813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-8813. --- Resolution: Fixed Fix Version/s: Impala 3.3.0 > Impala Doc: Support Hive ACID Insert-only Tables > > > Key: IMPALA-8813 > URL: https://issues.apache.org/jira/browse/IMPALA-8813 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Labels: future_release_doc, in_33 > Fix For: Impala 3.3.0 > > > Create, Insert, and read Insert-only ACID tables. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (IMPALA-8813) Impala Doc: Support Hive ACID Insert-only Tables
[ https://issues.apache.org/jira/browse/IMPALA-8813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-8813. --- Resolution: Fixed Fix Version/s: Impala 3.3.0 > Impala Doc: Support Hive ACID Insert-only Tables > > > Key: IMPALA-8813 > URL: https://issues.apache.org/jira/browse/IMPALA-8813 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Labels: future_release_doc, in_33 > Fix For: Impala 3.3.0 > > > Create, Insert, and read Insert-only ACID tables. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Closed] (IMPALA-8811) Impala Doc: query option to change default ACID type of new tables
[ https://issues.apache.org/jira/browse/IMPALA-8811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-8811. --- Resolution: Fixed Fix Version/s: Impala 3.3.0 > Impala Doc: query option to change default ACID type of new tables > -- > > Key: IMPALA-8811 > URL: https://issues.apache.org/jira/browse/IMPALA-8811 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > Labels: future_release_doc, in_33 > Fix For: Impala 3.3.0 > > > https://gerrit.cloudera.org/#/c/14021/ -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (IMPALA-8683) Document parquet/lz4 compression codec
[ https://issues.apache.org/jira/browse/IMPALA-8683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Rawat updated IMPALA-8683: --- Target Version: Impala 3.3.0 > Document parquet/lz4 compression codec > -- > > Key: IMPALA-8683 > URL: https://issues.apache.org/jira/browse/IMPALA-8683 > Project: IMPALA > Issue Type: Documentation > Components: Docs >Reporter: Abhishek Rawat >Assignee: Abhishek Rawat >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-8875) TestHmsIntegration.test_drop_column_maintains_stats seems flaky
[
https://issues.apache.org/jira/browse/IMPALA-8875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fang-Yu Rao updated IMPALA-8875:
Description:
The test of TestHmsIntegration.test_drop_column_maintains_stats seems flaky.
The related test file was updated recently due to
https://issues.apache.org/jira/browse/IMPALA-8823. Create this JIRA to track
this failed test. Maybe [~gaborkaszab] you could take a brief look at this?
Thanks!
The error messages are provided in the following.
{code:java}
Error Message
assert {'avg_col_len...ializer', ...} == {'COLUMN_STATS...me': 'x', ...} Common
items: {'avg_col_len': '', 'bitVector': '', 'col_name': 'x', 'comment': 'from
deserializer', 'data_type': 'int', 'distinct_count': '0', 'max': '0',
'max_col_len': '', 'min': '0', 'num_falses': '', 'num_nulls': '0', 'num_trues':
''} Right contains more items: {'COLUMN_STATS_ACCURATE': '{}'} Full diff: +
{'COLUMN_STATS_ACCURATE': '{}', - {'avg_col_len': '', ? ^ + 'avg_col_len': '',
? ^ 'bitVector': '', 'col_name': 'x', 'comment': 'from deserializer',
'data_type': 'int', 'distinct_count': '0', 'max': '0', 'max_col_len': '',
'min': '0', 'num_falses': '', 'num_nulls': '0', 'num_trues': ''}
{code}
The stack trace is given as follows.
{code:java}
Stacktrace
metadata/test_hms_integration.py:390: in test_drop_column_maintains_stats
assert hive_x_stats == self.hive_column_stats(table_name, 'x')
E assert {'avg_col_len...ializer', ...} == {'COLUMN_STATS...me': 'x', ...}
E Common items:
E {'avg_col_len': '',
E 'bitVector': '',
E 'col_name': 'x',
E 'comment': 'from deserializer',
E 'data_type': 'int',
E 'distinct_count': '0',
E 'max': '0',
E 'max_col_len': '',
E 'min': '0',
E 'num_falses': '',
E 'num_nulls': '0',
E 'num_trues': ''}
E Right contains more items:
E {'COLUMN_STATS_ACCURATE': '{}'}
E Full diff:
E + {'COLUMN_STATS_ACCURATE': '{}',
E - {'avg_col_len': '',
E ? ^
E + 'avg_col_len': '',
E ? ^
E 'bitVector': '',
E 'col_name': 'x',
E 'comment': 'from deserializer',
E 'data_type': 'int',
E 'distinct_count': '0',
E 'max': '0',
E 'max_col_len': '',
E 'min': '0',
E 'num_falses': '',
E 'num_nulls': '0',
E 'num_trues': ''}
{code}
was:
The test of TestHmsIntegration.test_drop_column_maintains_stats seems flaky.
The related test file was updated recently due to
https://issues.apache.org/jira/browse/IMPALA-8823. Create this JIRA to track
this failed test.
The error messages are provided in the following.
{code:java}
Error Message
assert {'avg_col_len...ializer', ...} == {'COLUMN_STATS...me': 'x', ...} Common
items: {'avg_col_len': '', 'bitVector': '', 'col_name': 'x', 'comment': 'from
deserializer', 'data_type': 'int', 'distinct_count': '0', 'max': '0',
'max_col_len': '', 'min': '0', 'num_falses': '', 'num_nulls': '0', 'num_trues':
''} Right contains more items: {'COLUMN_STATS_ACCURATE': '{}'} Full diff: +
{'COLUMN_STATS_ACCURATE': '{}', - {'avg_col_len': '', ? ^ + 'avg_col_len': '',
? ^ 'bitVector': '', 'col_name': 'x', 'comment': 'from deserializer',
'data_type': 'int', 'distinct_count': '0', 'max': '0', 'max_col_len': '',
'min': '0', 'num_falses': '', 'num_nulls': '0', 'num_trues': ''}
{code}
The stack trace is given as follows.
{code:java}
Stacktrace
metadata/test_hms_integration.py:390: in test_drop_column_maintains_stats
assert hive_x_stats == self.hive_column_stats(table_name, 'x')
E assert {'avg_col_len...ializer', ...} == {'COLUMN_STATS...me': 'x', ...}
E Common items:
E {'avg_col_len': '',
E 'bitVector': '',
E 'col_name': 'x',
E 'comment': 'from deserializer',
E 'data_type': 'int',
E 'distinct_count': '0',
E 'max': '0',
E 'max_col_len': '',
E 'min': '0',
E 'num_falses': '',
E 'num_nulls': '0',
E 'num_trues': ''}
E Right contains more items:
E {'COLUMN_STATS_ACCURATE': '{}'}
E Full diff:
E + {'COLUMN_STATS_ACCURATE': '{}',
E - {'avg_col_len': '',
E ? ^
E + 'avg_col_len': '',
E ? ^
E 'bitVector': '',
E 'col_name': 'x',
E 'comment': 'from deserializer',
E 'data_type': 'int',
E 'distinct_count': '0',
E 'max': '0',
E 'max_col_len': '',
E 'min': '0',
E 'num_falses': '',
E 'num_nulls': '0',
E 'num_trues': ''}
{code}
> TestHmsIntegration.test_drop_column_maintains_stats seems flaky
> ---
>
> Key: IMPALA-8875
> URL: https://issues.apache.org/jira/browse/IMPALA-8875
> Project: IMPALA
> Issue Type: Bug
>Reporter: Fang-Yu Rao
>Priority: Blocker
> Labels: broken-build
>
> The test of TestHmsIntegration.test_drop_column_maintains_stats seems flaky.
> The related test file was updated recently due to
>
[jira] [Resolved] (IMPALA-7070) Failed test: query_test.test_nested_types.TestParquetArrayEncodings.test_thrift_array_of_arrays on S3
[
https://issues.apache.org/jira/browse/IMPALA-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Volker resolved IMPALA-7070.
-
Resolution: Fixed
Fix Version/s: Impala 3.3.0
> Failed test:
> query_test.test_nested_types.TestParquetArrayEncodings.test_thrift_array_of_arrays
> on S3
> -
>
> Key: IMPALA-7070
> URL: https://issues.apache.org/jira/browse/IMPALA-7070
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
>Affects Versions: Impala 3.0
>Reporter: Dimitris Tsirogiannis
>Priority: Critical
> Labels: broken-build, flaky, s3, test-failure
> Fix For: Impala 3.3.0
>
>
>
> {code:java}
> Error Message
> query_test/test_nested_types.py:406: in test_thrift_array_of_arrays "col1
> array>") query_test/test_nested_types.py:579: in
> _create_test_table check_call(["hadoop", "fs", "-put", local_path,
> location], shell=False) /usr/lib64/python2.6/subprocess.py:505: in check_call
> raise CalledProcessError(retcode, cmd) E CalledProcessError: Command
> '['hadoop', 'fs', '-put',
> '/data/jenkins/workspace/impala-asf-2.x-core-s3/repos/Impala/testdata/parquet_nested_types_encodings/bad-thrift.parquet',
>
> 's3a://impala-cdh5-s3-test/test-warehouse/test_thrift_array_of_arrays_11da5fde.db/ThriftArrayOfArrays']'
> returned non-zero exit status 1
> Stacktrace
> query_test/test_nested_types.py:406: in test_thrift_array_of_arrays
> "col1 array>")
> query_test/test_nested_types.py:579: in _create_test_table
> check_call(["hadoop", "fs", "-put", local_path, location], shell=False)
> /usr/lib64/python2.6/subprocess.py:505: in check_call
> raise CalledProcessError(retcode, cmd)
> E CalledProcessError: Command '['hadoop', 'fs', '-put',
> '/data/jenkins/workspace/impala-asf-2.x-core-s3/repos/Impala/testdata/parquet_nested_types_encodings/bad-thrift.parquet',
>
> 's3a://impala-cdh5-s3-test/test-warehouse/test_thrift_array_of_arrays_11da5fde.db/ThriftArrayOfArrays']'
> returned non-zero exit status 1
> Standard Error
> SET sync_ddl=False;
> -- executing against localhost:21000
> DROP DATABASE IF EXISTS `test_thrift_array_of_arrays_11da5fde` CASCADE;
> SET sync_ddl=False;
> -- executing against localhost:21000
> CREATE DATABASE `test_thrift_array_of_arrays_11da5fde`;
> MainThread: Created database "test_thrift_array_of_arrays_11da5fde" for test
> ID
> "query_test/test_nested_types.py::TestParquetArrayEncodings::()::test_thrift_array_of_arrays[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]"
> -- executing against localhost:21000
> create table test_thrift_array_of_arrays_11da5fde.ThriftArrayOfArrays (col1
> array>) stored as parquet location
> 's3a://impala-cdh5-s3-test/test-warehouse/test_thrift_array_of_arrays_11da5fde.db/ThriftArrayOfArrays';
> 18/05/20 18:31:03 WARN impl.MetricsConfig: Cannot locate configuration: tried
> hadoop-metrics2-s3a-file-system.properties,hadoop-metrics2.properties
> 18/05/20 18:31:03 INFO impl.MetricsSystemImpl: Scheduled snapshot period at
> 10 second(s).
> 18/05/20 18:31:03 INFO impl.MetricsSystemImpl: s3a-file-system metrics system
> started
> 18/05/20 18:31:06 INFO Configuration.deprecation:
> fs.s3a.server-side-encryption-key is deprecated. Instead, use
> fs.s3a.server-side-encryption.key
> put: rename
> `s3a://impala-cdh5-s3-test/test-warehouse/test_thrift_array_of_arrays_11da5fde.db/ThriftArrayOfArrays/bad-thrift.parquet._COPYING_'
> to
> `s3a://impala-cdh5-s3-test/test-warehouse/test_thrift_array_of_arrays_11da5fde.db/ThriftArrayOfArrays/bad-thrift.parquet':
> Input/output error
> 18/05/20 18:31:08 INFO impl.MetricsSystemImpl: Stopping s3a-file-system
> metrics system...
> 18/05/20 18:31:08 INFO impl.MetricsSystemImpl: s3a-file-system metrics system
> stopped.
> 18/05/20 18:31:08 INFO impl.MetricsSystemImpl: s3a-file-system metrics system
> shutdown complete.{code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Resolved] (IMPALA-7070) Failed test: query_test.test_nested_types.TestParquetArrayEncodings.test_thrift_array_of_arrays on S3
[
https://issues.apache.org/jira/browse/IMPALA-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Volker resolved IMPALA-7070.
-
Resolution: Fixed
Fix Version/s: Impala 3.3.0
> Failed test:
> query_test.test_nested_types.TestParquetArrayEncodings.test_thrift_array_of_arrays
> on S3
> -
>
> Key: IMPALA-7070
> URL: https://issues.apache.org/jira/browse/IMPALA-7070
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
>Affects Versions: Impala 3.0
>Reporter: Dimitris Tsirogiannis
>Priority: Critical
> Labels: broken-build, flaky, s3, test-failure
> Fix For: Impala 3.3.0
>
>
>
> {code:java}
> Error Message
> query_test/test_nested_types.py:406: in test_thrift_array_of_arrays "col1
> array>") query_test/test_nested_types.py:579: in
> _create_test_table check_call(["hadoop", "fs", "-put", local_path,
> location], shell=False) /usr/lib64/python2.6/subprocess.py:505: in check_call
> raise CalledProcessError(retcode, cmd) E CalledProcessError: Command
> '['hadoop', 'fs', '-put',
> '/data/jenkins/workspace/impala-asf-2.x-core-s3/repos/Impala/testdata/parquet_nested_types_encodings/bad-thrift.parquet',
>
> 's3a://impala-cdh5-s3-test/test-warehouse/test_thrift_array_of_arrays_11da5fde.db/ThriftArrayOfArrays']'
> returned non-zero exit status 1
> Stacktrace
> query_test/test_nested_types.py:406: in test_thrift_array_of_arrays
> "col1 array>")
> query_test/test_nested_types.py:579: in _create_test_table
> check_call(["hadoop", "fs", "-put", local_path, location], shell=False)
> /usr/lib64/python2.6/subprocess.py:505: in check_call
> raise CalledProcessError(retcode, cmd)
> E CalledProcessError: Command '['hadoop', 'fs', '-put',
> '/data/jenkins/workspace/impala-asf-2.x-core-s3/repos/Impala/testdata/parquet_nested_types_encodings/bad-thrift.parquet',
>
> 's3a://impala-cdh5-s3-test/test-warehouse/test_thrift_array_of_arrays_11da5fde.db/ThriftArrayOfArrays']'
> returned non-zero exit status 1
> Standard Error
> SET sync_ddl=False;
> -- executing against localhost:21000
> DROP DATABASE IF EXISTS `test_thrift_array_of_arrays_11da5fde` CASCADE;
> SET sync_ddl=False;
> -- executing against localhost:21000
> CREATE DATABASE `test_thrift_array_of_arrays_11da5fde`;
> MainThread: Created database "test_thrift_array_of_arrays_11da5fde" for test
> ID
> "query_test/test_nested_types.py::TestParquetArrayEncodings::()::test_thrift_array_of_arrays[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]"
> -- executing against localhost:21000
> create table test_thrift_array_of_arrays_11da5fde.ThriftArrayOfArrays (col1
> array>) stored as parquet location
> 's3a://impala-cdh5-s3-test/test-warehouse/test_thrift_array_of_arrays_11da5fde.db/ThriftArrayOfArrays';
> 18/05/20 18:31:03 WARN impl.MetricsConfig: Cannot locate configuration: tried
> hadoop-metrics2-s3a-file-system.properties,hadoop-metrics2.properties
> 18/05/20 18:31:03 INFO impl.MetricsSystemImpl: Scheduled snapshot period at
> 10 second(s).
> 18/05/20 18:31:03 INFO impl.MetricsSystemImpl: s3a-file-system metrics system
> started
> 18/05/20 18:31:06 INFO Configuration.deprecation:
> fs.s3a.server-side-encryption-key is deprecated. Instead, use
> fs.s3a.server-side-encryption.key
> put: rename
> `s3a://impala-cdh5-s3-test/test-warehouse/test_thrift_array_of_arrays_11da5fde.db/ThriftArrayOfArrays/bad-thrift.parquet._COPYING_'
> to
> `s3a://impala-cdh5-s3-test/test-warehouse/test_thrift_array_of_arrays_11da5fde.db/ThriftArrayOfArrays/bad-thrift.parquet':
> Input/output error
> 18/05/20 18:31:08 INFO impl.MetricsSystemImpl: Stopping s3a-file-system
> metrics system...
> 18/05/20 18:31:08 INFO impl.MetricsSystemImpl: s3a-file-system metrics system
> stopped.
> 18/05/20 18:31:08 INFO impl.MetricsSystemImpl: s3a-file-system metrics system
> shutdown complete.{code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[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=16910063#comment-16910063 ] Lars Volker commented on IMPALA-7117: - I think we can just keep it at Debug since it only affects our own tests and no-one objected so far. Closing this one for now. > 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.14#76016) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (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:all-tabpanel ] Lars Volker closed IMPALA-7117. --- Resolution: Won't Fix > 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.14#76016) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Closed] (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:all-tabpanel ] Lars Volker closed IMPALA-7117. --- Resolution: Won't Fix > 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.14#76016)
[jira] [Commented] (IMPALA-8870) Bump guava version when building against Hive 3
[
https://issues.apache.org/jira/browse/IMPALA-8870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16909998#comment-16909998
]
Quanlong Huang commented on IMPALA-8870:
Hi [~tarmstrong], do you know anyone has bandwidth on this? I think we build on
hive2 in CDH by default. Is this a blocker for 3.3.0 release?
> Bump guava version when building against Hive 3
> ---
>
> Key: IMPALA-8870
> URL: https://issues.apache.org/jira/browse/IMPALA-8870
> Project: IMPALA
> Issue Type: Improvement
> Components: Infrastructure
>Affects Versions: Impala 3.3.0
>Reporter: Tim Armstrong
>Priority: Blocker
>
> Guava is pinned to 14.01
> https://github.com/apache/impala/blob/8094811/impala-parent/pom.xml#L59
> {code}
>
> 14.0.1
> {code}
> I think this has likely changed in Hive 3 and we probably want to revisit
> this.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
