Re: [VOTE] Should we release Hive Storage API 2.8.1 rc1?
https://github.com/apache/hive/pull/2543 .. Owen > On Jul 28, 2021, at 09:33, Dongjoon Hyun wrote: > > Thank you for sharing. What is the JIRA ID for redact issue? > > Dongjoon > >> On 2021/07/28 16:22:03, Owen O'Malley wrote: >> Ok, pavan found that hive 25190 broke the redact mask code in orc. Let me >> fix that. >> >> .. Owen >> On Jul 26, 2021, at 14:18, Owen O'Malley wrote: >>> >>> >>> Hello all, >>> >>> I would like to propose a new storage-api release including HIVE-25386 and >>> HIVE-25190. >>> >>> Shall we release the following artifacts as Hive Storage API 2.8.1? >>> >>> tar: http://home.apache.org/~omalley/hive-storage-2.8.1/ >>> tag: https://github.com/apache/hive/releases/tag/storage-release-2.8.1-rc1 >>> jiras: https://issues.apache.org/jira/projects/HIVE/versions/12350456 >>> >>> .. Owen >>
[jira] [Created] (HIVE-25400) Move the offset updating in BytesColumnVector to setValPreallocated.
Owen O'Malley created HIVE-25400: Summary: Move the offset updating in BytesColumnVector to setValPreallocated. Key: HIVE-25400 URL: https://issues.apache.org/jira/browse/HIVE-25400 Project: Hive Issue Type: Bug Reporter: Owen O'Malley Assignee: Owen O'Malley Fix For: storage-2.7.3, storage-2.8.1, storage-2.9.0 HIVE-25190 changed the semantics of BytesColumnVector so that ensureValPreallocated reserved the room, which interacted badly with ORC's redact mask code. The redact mask code needs to be able to increase the allocation as it goes so it can call the ensureValPreallocated multiple times. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [VOTE] Should we release Hive Storage API 2.8.1 rc1?
Thank you for sharing. What is the JIRA ID for redact issue? Dongjoon On 2021/07/28 16:22:03, Owen O'Malley wrote: > Ok, pavan found that hive 25190 broke the redact mask code in orc. Let me fix > that. > > .. Owen > > > On Jul 26, 2021, at 14:18, Owen O'Malley wrote: > > > > > > Hello all, > > > > I would like to propose a new storage-api release including HIVE-25386 and > > HIVE-25190. > > > > Shall we release the following artifacts as Hive Storage API 2.8.1? > > > > tar: http://home.apache.org/~omalley/hive-storage-2.8.1/ > > tag: https://github.com/apache/hive/releases/tag/storage-release-2.8.1-rc1 > > jiras: https://issues.apache.org/jira/projects/HIVE/versions/12350456 > > > > .. Owen >
Re: [VOTE] Should we release Hive Storage API 2.8.1 rc1?
Ok, pavan found that hive 25190 broke the redact mask code in orc. Let me fix that. .. Owen > On Jul 26, 2021, at 14:18, Owen O'Malley wrote: > > > Hello all, > > I would like to propose a new storage-api release including HIVE-25386 and > HIVE-25190. > > Shall we release the following artifacts as Hive Storage API 2.8.1? > > tar: http://home.apache.org/~omalley/hive-storage-2.8.1/ > tag: https://github.com/apache/hive/releases/tag/storage-release-2.8.1-rc1 > jiras: https://issues.apache.org/jira/projects/HIVE/versions/12350456 > > .. Owen
[jira] [Created] (HIVE-25399) Make command splitting consistent between beeline and hive cli
Xuedong Luan created HIVE-25399: --- Summary: Make command splitting consistent between beeline and hive cli Key: HIVE-25399 URL: https://issues.apache.org/jira/browse/HIVE-25399 Project: Hive Issue Type: Improvement Components: CLI Affects Versions: 3.1.2 Reporter: Xuedong Luan Assignee: Xuedong Luan Make command splitting consistent between beeline and hive cli -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HIVE-25398) Converted external tables should be able to configure purge behaviour
Panagiotis Garefalakis created HIVE-25398:
-
Summary: Converted external tables should be able to configure
purge behaviour
Key: HIVE-25398
URL: https://issues.apache.org/jira/browse/HIVE-25398
Project: Hive
Issue Type: Bug
Reporter: Panagiotis Garefalakis
Assignee: Panagiotis Garefalakis
Creating non-ACID MANAGED tables is not allowed on Hive, which is instead
converting these tables to External:
https://issues.apache.org/jira/browse/HIVE-22158
During table translation both TRANSLATED_TO_EXTERNAL and
'external.table.purge' are set to True. However, there could be the case that
the second parameter is already set in the table properties by the User. This
is ticket is adding an extra check to maintain that property if set.
PS: A cleaner solution would be to create these Tables as External directly but
there could be the case the User is taking advantage of the translation and is
expecting the data NOT to be purged!
Example:
{code:java}
-- Non-ACID table will be translated to EXTERNAL
create table c(c int) LOCATION 'etp_1'
TBLPROPERTIES('transactional'='false','external.table.purge'='false');
insert into c values(1);
-- Maintain the purge=false property set above
desc formatted c;
select count(*) from c;
drop table c;
-- Create table in same location, data should still be there
create table c(c int) LOCATION 'etp_1'
TBLPROPERTIES('transactional'='false','external.table.purge'='false');
desc formatted c;
select count(*) from c;
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HIVE-25397) Snapshot support for controlled failover
Arko Sharma created HIVE-25397: -- Summary: Snapshot support for controlled failover Key: HIVE-25397 URL: https://issues.apache.org/jira/browse/HIVE-25397 Project: Hive Issue Type: Bug Reporter: Arko Sharma Assignee: Arko Sharma -- This message was sent by Atlassian Jira (v8.3.4#803005)
