[jira] [Resolved] (IMPALA-5569) Implement UNSET TBLPROPERTIES for ALTER TABLE
[ https://issues.apache.org/jira/browse/IMPALA-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amogh Margoor resolved IMPALA-5569. --- Resolution: Fixed Resolving this as commit above adds the support. > Implement UNSET TBLPROPERTIES for ALTER TABLE > - > > Key: IMPALA-5569 > URL: https://issues.apache.org/jira/browse/IMPALA-5569 > Project: IMPALA > Issue Type: Improvement > Components: Catalog >Affects Versions: Impala 2.9.0 >Reporter: Nándor Kollár >Assignee: Amogh Margoor >Priority: Minor > > Right now, I can set table properties via Impala client, but I couldn't find > a way to unset them. I can set them to empty string, but I've to use Hive CLI > to remove the key-value par. > It would be nice to extend ALTER TABLE with UNSET clause to be able to unset > table properties. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Resolved] (IMPALA-10730) Create MD5 built-in function
[ https://issues.apache.org/jira/browse/IMPALA-10730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amogh Margoor resolved IMPALA-10730. Resolution: Fixed Resolving this as the commit above adds the support > Create MD5 built-in function > > > Key: IMPALA-10730 > URL: https://issues.apache.org/jira/browse/IMPALA-10730 > Project: IMPALA > Issue Type: New Feature >Reporter: Amogh Margoor >Assignee: Amogh Margoor >Priority: Major > > IMPALA-10679 introduced built-in functions for SHA1 and SHA2. > We would like to even add support for MD5. For FIPS mode MD5 function will be > disabled and will throw error if used. cc [~JacquesJZa] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-10777) Enable min/max filtering for Iceberg partitions.
[ https://issues.apache.org/jira/browse/IMPALA-10777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoltán Borók-Nagy updated IMPALA-10777: --- Component/s: Frontend > Enable min/max filtering for Iceberg partitions. > > > Key: IMPALA-10777 > URL: https://issues.apache.org/jira/browse/IMPALA-10777 > Project: IMPALA > Issue Type: Improvement > Components: Frontend >Reporter: Qifan Chen >Priority: Major > > The work to enable min/max filters for partition columns is underway. See > IMPALA-10738. > It is nice to enable the filtering for iceberg partitions. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-10777) Enable min/max filtering for Iceberg partitions.
[ https://issues.apache.org/jira/browse/IMPALA-10777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoltán Borók-Nagy updated IMPALA-10777: --- Labels: impala-iceberg (was: ) > Enable min/max filtering for Iceberg partitions. > > > Key: IMPALA-10777 > URL: https://issues.apache.org/jira/browse/IMPALA-10777 > Project: IMPALA > Issue Type: Improvement > Components: Frontend >Reporter: Qifan Chen >Priority: Major > Labels: impala-iceberg > > The work to enable min/max filters for partition columns is underway. See > IMPALA-10738. > It is nice to enable the filtering for iceberg partitions. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Commented] (IMPALA-10627) Use standard Iceberg table properties
[ https://issues.apache.org/jira/browse/IMPALA-10627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17375753#comment-17375753 ] Attila Jeges commented on IMPALA-10627: --- https://gerrit.cloudera.org/#/c/17654/ > Use standard Iceberg table properties > - > > Key: IMPALA-10627 > URL: https://issues.apache.org/jira/browse/IMPALA-10627 > Project: IMPALA > Issue Type: Bug >Reporter: Zoltán Borók-Nagy >Assignee: Attila Jeges >Priority: Major > Labels: impala-iceberg > > Iceberg lists the following properties: > [https://iceberg.apache.org/configuration/] > We should also use these properties if possible, e.g. write.format.default, > write..compression-codec > Currently Impala use the table property 'iceberg.file_format' to determine > the data file format for reads/writes. In the future, read operations should > automatically detect the file formats (IMPALA-10610), but for writes we > should use 'write.format.default'. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Commented] (IMPALA-9657) [DOC]: Document Hive 3 default
[ https://issues.apache.org/jira/browse/IMPALA-9657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17375928#comment-17375928 ] shajini thayasingh commented on IMPALA-9657: I believe that the change described here which is changing "USE_CDP_HIVE to true" by default which in turn causes Impala to compile against Hive 3 and Ranger, rather than Hive 2 and Sentry is something that happens behind the scene and does not have doc impact. [~stakiar] could you please confirm if my understanding is right! > [DOC]: Document Hive 3 default > -- > > Key: IMPALA-9657 > URL: https://issues.apache.org/jira/browse/IMPALA-9657 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Affects Versions: Not Applicable >Reporter: Kris Hahn >Assignee: shajini thayasingh >Priority: Major > Labels: docs > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
