[jira] [Updated] (HIVE-28188) Upgrade PostGres to 42.5.6

2024-04-12 Thread ASF GitHub Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/HIVE-28188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated HIVE-28188:
--
Labels: Security pull-request-available  (was: Security)

> Upgrade PostGres to 42.5.6
> --
>
> Key: HIVE-28188
> URL: https://issues.apache.org/jira/browse/HIVE-28188
> Project: Hive
>  Issue Type: Task
>  Components: Hive
>Reporter: Devaspati Krishnatri
>Assignee: Devaspati Krishnatri
>Priority: Major
>  Labels: Security, pull-request-available
>
> Upgrade Postgres to 42.5.6 to target critical CVEs.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Assigned] (HIVE-28173) Issues with staging dirs with materialized views on HDFS encrypted table

2024-04-12 Thread Krisztian Kasa (Jira)


 [ 
https://issues.apache.org/jira/browse/HIVE-28173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Krisztian Kasa reassigned HIVE-28173:
-

Assignee: Steve Carlin

> Issues with staging dirs with materialized views on HDFS encrypted table
> 
>
> Key: HIVE-28173
> URL: https://issues.apache.org/jira/browse/HIVE-28173
> Project: Hive
>  Issue Type: Bug
>  Components: HiveServer2
>Affects Versions: 4.0.0
>Reporter: Steve Carlin
>Assignee: Steve Carlin
>Priority: Major
>  Labels: pull-request-available
>
> In the materialized view registry thread which runs in the background, there 
> are 2 issues involving staging directories on hdfs encrypted tables
> 1) The staging directory is created at compile time.  For non hdfs encrypted 
> tables, the "mkdir" flag is set to false.  There is no such flag for hdfs 
> encrypted tables.
> 2) The "FileSystem.deleteOnFileExit()" method is not called from the 
> HiveMaterializedViewRegistry thread.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (HIVE-28153) Flaky test TestConflictingDataFiles.testMultiFiltersUpdate

2024-04-12 Thread ASF GitHub Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/HIVE-28153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated HIVE-28153:
--
Labels: pull-request-available  (was: )

> Flaky test TestConflictingDataFiles.testMultiFiltersUpdate
> --
>
> Key: HIVE-28153
> URL: https://issues.apache.org/jira/browse/HIVE-28153
> Project: Hive
>  Issue Type: Test
>  Components: Test
>Reporter: Butao Zhang
>Assignee: Simhadri Govindappa
>Priority: Major
>  Labels: pull-request-available
>
> This test has been failing a lot lately, such as 
> [http://ci.hive.apache.org/blue/organizations/jenkins/hive-precommit/detail/PR-5063/13/tests/]
>  
> And the flaky test shows this test is unstable:
> [http://ci.hive.apache.org/job/hive-flaky-check/831/testReport/]
> {code:java}
> 10:29:21  [INFO]  T E S T S
> 10:29:21  [INFO] ---
> 10:29:21  [INFO] Running org.apache.iceberg.mr.hive.TestConflictingDataFiles
> 10:36:13  [ERROR] Tests run: 60, Failures: 1, Errors: 0, Skipped: 24, Time 
> elapsed: 399.12 s <<< FAILURE! - in 
> org.apache.iceberg.mr.hive.TestConflictingDataFiles
> 10:36:13  [ERROR] 
> org.apache.iceberg.mr.hive.TestConflictingDataFiles.testMultiFiltersUpdate[fileFormat=PARQUET,
>  engine=tez, catalog=HIVE_CATALOG, isVectorized=false, formatVersion=1]  Time 
> elapsed: 11.781 s  <<< FAILURE!
> 10:36:13  java.lang.AssertionError: expected:<12> but was:<13>
> 10:36:13  at org.junit.Assert.fail(Assert.java:89)
> 10:36:13  at org.junit.Assert.failNotEquals(Assert.java:835)
> 10:36:13  at org.junit.Assert.assertEquals(Assert.java:647)
> 10:36:13  at org.junit.Assert.assertEquals(Assert.java:633)
> 10:36:13  at 
> org.apache.iceberg.mr.hive.TestConflictingDataFiles.testMultiFiltersUpdate(TestConflictingDataFiles.java:135)
> 10:36:13  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 10:36:13  at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 10:36:13  at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 10:36:13  at java.lang.reflect.Method.invoke(Method.java:498)
> 10:36:13  at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> 10:36:13  at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> 10:36:13  at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> 10:36:13  at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> 10:36:13  at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> 10:36:13  at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> 10:36:13  at 
> org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
> 10:36:13  at 
> org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:299)
> 10:36:13  at 
> org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:293)
> 10:36:13  at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 10:36:13  at java.lang.Thread.run(Thread.java:748) {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (HIVE-28189) PrivilegeSynchonizer Need to lock the table while synchronizing privs data

2024-04-12 Thread Yuping Fan (Jira)


[ 
https://issues.apache.org/jira/browse/HIVE-28189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836424#comment-17836424
 ] 

Yuping Fan commented on HIVE-28189:
---

Could anyone take a discussion for this issue? 

> PrivilegeSynchonizer Need to lock the table while synchronizing privs data
> --
>
> Key: HIVE-28189
> URL: https://issues.apache.org/jira/browse/HIVE-28189
> Project: Hive
>  Issue Type: Bug
>  Components: HiveServer2
>Affects Versions: 3.1.0
>Reporter: Yuping Fan
>Priority: Major
>
> Due to the large number of permissions, the synchronization time exceeds 1 
> minute. 
> If I delete this table during that 1 minute, it will cause the table to fail 
> to delete, with the error that the tbl_col_privs foreign key constraint check 
> failed. So I think the table should be locked when the permissions are 
> synchronized



--
This message was sent by Atlassian Jira
(v8.20.10#820010)