[jira] [Updated] (HIVE-17155) findConfFile() in HiveConf.java has some issues with the conf path
[ https://issues.apache.org/jira/browse/HIVE-17155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang chen updated HIVE-17155: -- Affects Version/s: 2.3.7 > findConfFile() in HiveConf.java has some issues with the conf path > -- > > Key: HIVE-17155 > URL: https://issues.apache.org/jira/browse/HIVE-17155 > Project: Hive > Issue Type: Bug > Components: Hive >Affects Versions: 2.3.7, 3.0.0 >Reporter: Aihua Xu >Assignee: xiaoqiang_song >Priority: Minor > Fix For: 3.0.0 > > Attachments: HIVE-17155.1.patch > > > In findConfFile() function of HiveConf.java, here are some issues. > File.pathSeparator which is ":" is used as the separator rather than "/". new > File(jarUri).getParentFile() will get the "$hive_home/lib" folder, but > actually we want "$hive_home". -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (HIVE-12371) Adding a timeout connection parameter for JDBC
[
https://issues.apache.org/jira/browse/HIVE-12371?focusedWorklogId=529713=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-529713
]
ASF GitHub Bot logged work on HIVE-12371:
-
Author: ASF GitHub Bot
Created on: 31/Dec/20 06:56
Start Date: 31/Dec/20 06:56
Worklog Time Spent: 10m
Work Description: jshmchenxi commented on pull request #1611:
URL: https://github.com/apache/hive/pull/1611#issuecomment-752868142
@dengzhhu653 Yes, I rebased the code. The errors seems to be unrelated
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 529713)
Time Spent: 2h (was: 1h 50m)
> Adding a timeout connection parameter for JDBC
> --
>
> Key: HIVE-12371
> URL: https://issues.apache.org/jira/browse/HIVE-12371
> Project: Hive
> Issue Type: Improvement
> Components: JDBC
>Reporter: Nemon Lou
>Assignee: Xi Chen
>Priority: Minor
> Labels: pull-request-available
> Time Spent: 2h
> Remaining Estimate: 0h
>
> There are some timeout settings from server side:
> HIVE-4766
> HIVE-6679
> Adding a timeout connection parameter for JDBC is useful in some scenario:
> 1,beeline (which can not set timeout manually)
> 2,customize timeout for different connections (among hive or RDBs,which can
> not be done via DriverManager.setLoginTimeout())
> Just like postgresql,
> {noformat}
> jdbc:postgresql://localhost/test?user=fred=secret=true=0
> {noformat}
> or mysql
> {noformat}
> jdbc:mysql://xxx.xx.xxx.xxx:3306/database?connectTimeout=6=6
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HIVE-17155) findConfFile() in HiveConf.java has some issues with the conf path
[ https://issues.apache.org/jira/browse/HIVE-17155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17256855#comment-17256855 ] Chang chen commented on HIVE-17155: --- Hi All Could we also cherry pick it into branch 2.3? we currently met a case where *org.springframework.boot.loader.LaunchedURLClassLoader* is used, and hence jar protocol is used. Thanks Chang > findConfFile() in HiveConf.java has some issues with the conf path > -- > > Key: HIVE-17155 > URL: https://issues.apache.org/jira/browse/HIVE-17155 > Project: Hive > Issue Type: Bug > Components: Hive >Affects Versions: 3.0.0 >Reporter: Aihua Xu >Assignee: xiaoqiang_song >Priority: Minor > Fix For: 3.0.0 > > Attachments: HIVE-17155.1.patch > > > In findConfFile() function of HiveConf.java, here are some issues. > File.pathSeparator which is ":" is used as the separator rather than "/". new > File(jarUri).getParentFile() will get the "$hive_home/lib" folder, but > actually we want "$hive_home". -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (HIVE-12371) Adding a timeout connection parameter for JDBC
[
https://issues.apache.org/jira/browse/HIVE-12371?focusedWorklogId=529711=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-529711
]
ASF GitHub Bot logged work on HIVE-12371:
-
Author: ASF GitHub Bot
Created on: 31/Dec/20 06:51
Start Date: 31/Dec/20 06:51
Worklog Time Spent: 10m
Work Description: jshmchenxi commented on a change in pull request #1611:
URL: https://github.com/apache/hive/pull/1611#discussion_r550411547
##
File path: jdbc/src/java/org/apache/hive/jdbc/HiveConnection.java
##
@@ -1002,11 +1002,19 @@ private String getSessionValue(String varName, String
varDefault) {
return varValue;
}
- // copy loginTimeout from driver manager. Thrift timeout needs to be in
millis
+ // use socketTimeout from jdbc connection url. Thrift timeout needs to be in
millis
private void setupLoginTimeout() {
-long timeOut = TimeUnit.SECONDS.toMillis(DriverManager.getLoginTimeout());
+String socketTimeoutStr =
sessConfMap.getOrDefault(JdbcConnectionParams.SOCKET_TIMEOUT, "0");
+long timeOut = 0;
Review comment:
Sorry for the late reply. If users depends on DriverManager.loginTimeout
to control HS2 jdbc timeout, they will have to refactor their code after
applying this. However, we haven't yet met a situation that we need this
timeout to return quickly when HS2 hangs or something. Our problem is when
submitting a big query which needs minutes to compile, the connection is lost
because of this DriverManager.loginTimeout. Maybe we need to set a timeout
parameter for HS2 on the server side too.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 529711)
Time Spent: 1h 50m (was: 1h 40m)
> Adding a timeout connection parameter for JDBC
> --
>
> Key: HIVE-12371
> URL: https://issues.apache.org/jira/browse/HIVE-12371
> Project: Hive
> Issue Type: Improvement
> Components: JDBC
>Reporter: Nemon Lou
>Assignee: Xi Chen
>Priority: Minor
> Labels: pull-request-available
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> There are some timeout settings from server side:
> HIVE-4766
> HIVE-6679
> Adding a timeout connection parameter for JDBC is useful in some scenario:
> 1,beeline (which can not set timeout manually)
> 2,customize timeout for different connections (among hive or RDBs,which can
> not be done via DriverManager.setLoginTimeout())
> Just like postgresql,
> {noformat}
> jdbc:postgresql://localhost/test?user=fred=secret=true=0
> {noformat}
> or mysql
> {noformat}
> jdbc:mysql://xxx.xx.xxx.xxx:3306/database?connectTimeout=6=6
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work logged] (HIVE-21961) Update jetty version to 9.4.x
[ https://issues.apache.org/jira/browse/HIVE-21961?focusedWorklogId=529701=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-529701 ] ASF GitHub Bot logged work on HIVE-21961: - Author: ASF GitHub Bot Created on: 31/Dec/20 05:52 Start Date: 31/Dec/20 05:52 Worklog Time Spent: 10m Work Description: wangyum commented on pull request #1813: URL: https://github.com/apache/hive/pull/1813#issuecomment-752853927 Test status: http://ci.hive.apache.org/blue/organizations/jenkins/hive-precommit/detail/PR-1813/3/pipeline/ This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 529701) Time Spent: 1h (was: 50m) > Update jetty version to 9.4.x > - > > Key: HIVE-21961 > URL: https://issues.apache.org/jira/browse/HIVE-21961 > Project: Hive > Issue Type: Task >Reporter: Oleksiy Sayankin >Assignee: László Bodor >Priority: Major > Labels: pull-request-available > Attachments: HIVE-21961.02.patch, HIVE-21961.03.patch, > HIVE-21961.patch > > Time Spent: 1h > Remaining Estimate: 0h > > Update jetty version to 9.4.x -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (HIVE-21961) Update jetty version to 9.4.x
[ https://issues.apache.org/jira/browse/HIVE-21961?focusedWorklogId=529693=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-529693 ] ASF GitHub Bot logged work on HIVE-21961: - Author: ASF GitHub Bot Created on: 31/Dec/20 04:34 Start Date: 31/Dec/20 04:34 Worklog Time Spent: 10m Work Description: wangyum closed pull request #1813: URL: https://github.com/apache/hive/pull/1813 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 529693) Time Spent: 50m (was: 40m) > Update jetty version to 9.4.x > - > > Key: HIVE-21961 > URL: https://issues.apache.org/jira/browse/HIVE-21961 > Project: Hive > Issue Type: Task >Reporter: Oleksiy Sayankin >Assignee: László Bodor >Priority: Major > Labels: pull-request-available > Attachments: HIVE-21961.02.patch, HIVE-21961.03.patch, > HIVE-21961.patch > > Time Spent: 50m > Remaining Estimate: 0h > > Update jetty version to 9.4.x -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (HIVE-21961) Update jetty version to 9.4.x
[ https://issues.apache.org/jira/browse/HIVE-21961?focusedWorklogId=529692=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-529692 ] ASF GitHub Bot logged work on HIVE-21961: - Author: ASF GitHub Bot Created on: 31/Dec/20 04:34 Start Date: 31/Dec/20 04:34 Worklog Time Spent: 10m Work Description: wangyum opened a new pull request #1813: URL: https://github.com/apache/hive/pull/1813 ### What changes were proposed in this pull request? Upgrade Hadoop to 3.1.4 and Jetty to 9.4.20.v20190813. ### Why are the changes needed? Fix compatibility issues: https://github.com/apache/hive/pull/1812#issuecomment-750782636 ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Existing test. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 529692) Time Spent: 40m (was: 0.5h) > Update jetty version to 9.4.x > - > > Key: HIVE-21961 > URL: https://issues.apache.org/jira/browse/HIVE-21961 > Project: Hive > Issue Type: Task >Reporter: Oleksiy Sayankin >Assignee: László Bodor >Priority: Major > Labels: pull-request-available > Attachments: HIVE-21961.02.patch, HIVE-21961.03.patch, > HIVE-21961.patch > > Time Spent: 40m > Remaining Estimate: 0h > > Update jetty version to 9.4.x -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (HIVE-12371) Adding a timeout connection parameter for JDBC
[
https://issues.apache.org/jira/browse/HIVE-12371?focusedWorklogId=529686=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-529686
]
ASF GitHub Bot logged work on HIVE-12371:
-
Author: ASF GitHub Bot
Created on: 31/Dec/20 03:41
Start Date: 31/Dec/20 03:41
Worklog Time Spent: 10m
Work Description: dengzhhu653 commented on pull request #1611:
URL: https://github.com/apache/hive/pull/1611#issuecomment-752832803
Hey @jshmchenxi, you can reopen the pr or push a commit to trigger a new
clean build...
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 529686)
Time Spent: 1h 40m (was: 1.5h)
> Adding a timeout connection parameter for JDBC
> --
>
> Key: HIVE-12371
> URL: https://issues.apache.org/jira/browse/HIVE-12371
> Project: Hive
> Issue Type: Improvement
> Components: JDBC
>Reporter: Nemon Lou
>Assignee: Xi Chen
>Priority: Minor
> Labels: pull-request-available
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> There are some timeout settings from server side:
> HIVE-4766
> HIVE-6679
> Adding a timeout connection parameter for JDBC is useful in some scenario:
> 1,beeline (which can not set timeout manually)
> 2,customize timeout for different connections (among hive or RDBs,which can
> not be done via DriverManager.setLoginTimeout())
> Just like postgresql,
> {noformat}
> jdbc:postgresql://localhost/test?user=fred=secret=true=0
> {noformat}
> or mysql
> {noformat}
> jdbc:mysql://xxx.xx.xxx.xxx:3306/database?connectTimeout=6=6
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work logged] (HIVE-21961) Update jetty version to 9.4.x
[ https://issues.apache.org/jira/browse/HIVE-21961?focusedWorklogId=529671=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-529671 ] ASF GitHub Bot logged work on HIVE-21961: - Author: ASF GitHub Bot Created on: 31/Dec/20 02:05 Start Date: 31/Dec/20 02:05 Worklog Time Spent: 10m Work Description: wangyum opened a new pull request #1813: URL: https://github.com/apache/hive/pull/1813 ### What changes were proposed in this pull request? ### Why are the changes needed? ### Does this PR introduce _any_ user-facing change? ### How was this patch tested? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 529671) Time Spent: 0.5h (was: 20m) > Update jetty version to 9.4.x > - > > Key: HIVE-21961 > URL: https://issues.apache.org/jira/browse/HIVE-21961 > Project: Hive > Issue Type: Task >Reporter: Oleksiy Sayankin >Assignee: László Bodor >Priority: Major > Labels: pull-request-available > Attachments: HIVE-21961.02.patch, HIVE-21961.03.patch, > HIVE-21961.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > Update jetty version to 9.4.x -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (HIVE-23935) Fetching primaryKey through beeline fails with NPE
[
https://issues.apache.org/jira/browse/HIVE-23935?focusedWorklogId=529655=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-529655
]
ASF GitHub Bot logged work on HIVE-23935:
-
Author: ASF GitHub Bot
Created on: 31/Dec/20 01:07
Start Date: 31/Dec/20 01:07
Worklog Time Spent: 10m
Work Description: github-actions[bot] closed pull request #1605:
URL: https://github.com/apache/hive/pull/1605
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 529655)
Time Spent: 2h 10m (was: 2h)
> Fetching primaryKey through beeline fails with NPE
> --
>
> Key: HIVE-23935
> URL: https://issues.apache.org/jira/browse/HIVE-23935
> Project: Hive
> Issue Type: Bug
>Reporter: Ayush Saxena
>Assignee: Ayush Saxena
>Priority: Major
> Labels: pull-request-available
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> Fetching PrimaryKey of a table through Beeline !primarykey fails with NPE
> {noformat}
> 0: jdbc:hive2://localhost:1> !primarykeys Persons
> Error: MetaException(message:java.lang.NullPointerException) (state=,code=0)
> org.apache.hive.service.cli.HiveSQLException:
> MetaException(message:java.lang.NullPointerException)
> at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:360)
> at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:351)
> at
> org.apache.hive.jdbc.HiveDatabaseMetaData.getPrimaryKeys(HiveDatabaseMetaData.java:573)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.hive.beeline.Reflector.invoke(Reflector.java:89)
> at org.apache.hive.beeline.Commands.metadata(Commands.java:125)
> at org.apache.hive.beeline.Commands.primarykeys(Commands.java:231)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hive.beeline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:57)
> at
> org.apache.hive.beeline.BeeLine.execCommandWithPrefix(BeeLine.java:1465)
> at org.apache.hive.beeline.BeeLine.dispatch(BeeLine.java:1504)
> at org.apache.hive.beeline.BeeLine.execute(BeeLine.java:1364)
> at org.apache.hive.beeline.BeeLine.begin(BeeLine.java:1134)
> at org.apache.hive.beeline.BeeLine.begin(BeeLine.java:1082)
> at
> org.apache.hive.beeline.BeeLine.mainWithInputRedirection(BeeLine.java:546)
> at org.apache.hive.beeline.BeeLine.main(BeeLine.java:528)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:323)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:236){noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work logged] (HIVE-24311) Rowcontainer should reset readBlocks when we clear rows to prevent OOM.
[ https://issues.apache.org/jira/browse/HIVE-24311?focusedWorklogId=529656=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-529656 ] ASF GitHub Bot logged work on HIVE-24311: - Author: ASF GitHub Bot Created on: 31/Dec/20 01:07 Start Date: 31/Dec/20 01:07 Worklog Time Spent: 10m Work Description: github-actions[bot] commented on pull request #1609: URL: https://github.com/apache/hive/pull/1609#issuecomment-752807254 This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Feel free to reach out on the d...@hive.apache.org list if the patch is in need of reviews. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 529656) Time Spent: 0.5h (was: 20m) > Rowcontainer should reset readBlocks when we clear rows to prevent OOM. > --- > > Key: HIVE-24311 > URL: https://issues.apache.org/jira/browse/HIVE-24311 > Project: Hive > Issue Type: Bug >Affects Versions: All Versions >Reporter: Qiang.Kang >Assignee: Qiang.Kang >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > Hi, We found that `Rowcontainer.clearRows()` only reset some index, such as: > `addCursor`, `itrCursor`, etc, without resetting read blocks. > As we all know, `currentReadBlock` and `currentWriteBlock` is the main memory > usage of a `Rowcontainer` and might be very large, depending on the data > pattern. > `currentReadBlock` and `currentWriteBlock` won't be the same object after > rowcontainer flushed data to disk. > Resetting `currentReadBlock` and `currentWriteBlock` while clearing rows will > prevent OOM. > > Therefore, I submit a patch to reset read blocks for `Rowcontainer`, just > like `PTFRowcontainer` does. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (HIVE-21961) Update jetty version to 9.4.x
[ https://issues.apache.org/jira/browse/HIVE-21961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17256699#comment-17256699 ] Chao Sun edited comment on HIVE-21961 at 12/30/20, 8:07 PM: HADOOP-16152 is also in Hadoop 3.1.4 so can we upgrade to that instead [~abstractdog]? it could be easier since Hive is now on Hadoop 3.1.0. was (Author: csun): HADOOP-16152 is also in Hadoop 3.1.4 so can we upgrade to that instead? it could be easier since Hive is now on Hadoop 3.1.0. > Update jetty version to 9.4.x > - > > Key: HIVE-21961 > URL: https://issues.apache.org/jira/browse/HIVE-21961 > Project: Hive > Issue Type: Task >Reporter: Oleksiy Sayankin >Assignee: László Bodor >Priority: Major > Labels: pull-request-available > Attachments: HIVE-21961.02.patch, HIVE-21961.03.patch, > HIVE-21961.patch > > Time Spent: 20m > Remaining Estimate: 0h > > Update jetty version to 9.4.x -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HIVE-21961) Update jetty version to 9.4.x
[ https://issues.apache.org/jira/browse/HIVE-21961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17256699#comment-17256699 ] Chao Sun commented on HIVE-21961: - HADOOP-16152 is also in Hadoop 3.1.4 so can we upgrade to that instead? it could be easier since Hive is now on Hadoop 3.1.0. > Update jetty version to 9.4.x > - > > Key: HIVE-21961 > URL: https://issues.apache.org/jira/browse/HIVE-21961 > Project: Hive > Issue Type: Task >Reporter: Oleksiy Sayankin >Assignee: László Bodor >Priority: Major > Labels: pull-request-available > Attachments: HIVE-21961.02.patch, HIVE-21961.03.patch, > HIVE-21961.patch > > Time Spent: 20m > Remaining Estimate: 0h > > Update jetty version to 9.4.x -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HIVE-21961) Update jetty version to 9.4.x
[ https://issues.apache.org/jira/browse/HIVE-21961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17256696#comment-17256696 ] Chao Sun commented on HIVE-21961: - I think the guava upgrade in 3.2.2 may cause a bigger headache than this since Hive depends on Spark which uses Guava 14.x as for now. cc [~ayushtkn] > Update jetty version to 9.4.x > - > > Key: HIVE-21961 > URL: https://issues.apache.org/jira/browse/HIVE-21961 > Project: Hive > Issue Type: Task >Reporter: Oleksiy Sayankin >Assignee: László Bodor >Priority: Major > Labels: pull-request-available > Attachments: HIVE-21961.02.patch, HIVE-21961.03.patch, > HIVE-21961.patch > > Time Spent: 20m > Remaining Estimate: 0h > > Update jetty version to 9.4.x -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (HIVE-14494) Add support for BUILD DEFERRED
[
https://issues.apache.org/jira/browse/HIVE-14494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish Sharma reassigned HIVE-14494:
Assignee: Ashish Sharma
> Add support for BUILD DEFERRED
> --
>
> Key: HIVE-14494
> URL: https://issues.apache.org/jira/browse/HIVE-14494
> Project: Hive
> Issue Type: Improvement
> Components: Materialized views
>Affects Versions: 2.2.0
>Reporter: Jesus Camacho Rodriguez
>Assignee: Ashish Sharma
>Priority: Major
>
> This is an important feature, as it allows to declare materialized views but
> do not materialize them till they are used for the first time, or a REBUILD
> statement is executed. The extension for the CREATE MATERIALIZED VIEW syntax
> should be as follows:
> {code:sql}
> CREATE MATERIALIZED VIEW [IF NOT EXISTS] [db_name.]materialized_view_name
> [BUILD DEFERRED] -- NEW!
> [COMMENT materialized_view_comment]
> [
>[ROW FORMAT row_format]
>[STORED AS file_format]
> | STORED BY 'storage.handler.class.name' [WITH SERDEPROPERTIES (...)]
> ]
> [LOCATION hdfs_path]
> [TBLPROPERTIES (property_name=property_value, ...)]
> AS select_statement;
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
