[jira] [Resolved] (CALCITE-6111) Explicit cast from expression to numeric type doesn't check overflow
[
https://issues.apache.org/jira/browse/CALCITE-6111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mihai Budiu resolved CALCITE-6111.
--
Fix Version/s: 1.37.0
Resolution: Fixed
Fixed in
https://github.com/apache/calcite/commit/e2c84a6485afce05bd0dcf5a9d6e9aafcb8af65a
> Explicit cast from expression to numeric type doesn't check overflow
>
>
> Key: CALCITE-6111
> URL: https://issues.apache.org/jira/browse/CALCITE-6111
> Project: Calcite
> Issue Type: Bug
> Components: core
>Affects Versions: 1.36.0
>Reporter: Evgeny Stanilovsky
>Assignee: Mihai Budiu
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.37.0
>
>
> After [1] was implemented it is still possible to obtain erroneous result,
> check:
> {code:java}
> SELECT cast(100+30 as tinyint);{code}
> result:
> {code:java}
> -126{code}
> [1] https://issues.apache.org/jira/browse/CALCITE-5990
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CALCITE-6032) Multilevel correlated query is failing in RelDecorrelator code path
[
https://issues.apache.org/jira/browse/CALCITE-6032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated CALCITE-6032:
Labels: pull-request-available (was: )
> Multilevel correlated query is failing in RelDecorrelator code path
> ---
>
> Key: CALCITE-6032
> URL: https://issues.apache.org/jira/browse/CALCITE-6032
> Project: Calcite
> Issue Type: Bug
> Components: core
>Affects Versions: 1.35.0
>Reporter: Shiven Dvrk
>Assignee: Hanumath Rao Maduri
>Priority: Major
> Labels: pull-request-available
>
> We have following query:
> {code:java}
> SELECT
>Sum( In0.Col_5005 * (
>select
> MAX(mr.Col_147077 + mr.Col_147078 )
>from
> Bun mr
>where
> mr.Col_21084 = 1
> and mr.Col_21805 = 2
> and mr.Col_21807 = In0.Col_5003
> and mr.Col_21806 =
> (
> select
> Max(kr.Col_21806)
> from
> Bun kr
> where
> kr.Col_21807 = mr.Col_21807
> and kr.Col_21804 = mr.Col_21804
> and kr.Col_21805 = mr.Col_21805
> and kr.Col_21806 <= In0.Col_4085
> )
> ) ) as mmn,
> count(*) as mmnCount
>FROM
> Den In0
>where
> In0.Col_5005 < 10
> and In0.Col_5005 > 0
> {code}
> It is failing to decorrelate with standard program:
> {code:java}
> cm.mapCorToCorRel.get($cor4)
> java.lang.NullPointerException: cm.mapCorToCorRel.get($cor4)
> at java.util.Objects.requireNonNull(Objects.java:290)
> at
> org.apache.calcite.sql2rel.RelDecorrelator.getCorRel(RelDecorrelator.java:928)
> at
> org.apache.calcite.sql2rel.RelDecorrelator.createValueGenerator(RelDecorrelator.java:820)
> at
> org.apache.calcite.sql2rel.RelDecorrelator.decorrelateInputWithValueGenerator(RelDecorrelator.java:1028)
> at
> org.apache.calcite.sql2rel.RelDecorrelator.maybeAddValueGenerator(RelDecorrelator.java:947)
> at
> org.apache.calcite.sql2rel.RelDecorrelator.decorrelateRel(RelDecorrelator.java:1150)
> at
> org.apache.calcite.sql2rel.RelDecorrelator.decorrelateRel(RelDecorrelator.java:1116)
> 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.calcite.util.ReflectUtil$2.invoke(ReflectUtil.java:531)
> at
> org.apache.calcite.sql2rel.RelDecorrelator.getInvoke(RelDecorrelator.java:707)
> at
> org.apache.calcite.sql2rel.RelDecorrelator.decorrelateRel(RelDecorrelator.java:749)
> at
> org.apache.calcite.sql2rel.RelDecorrelator.decorrelateRel(RelDecorrelator.java:738)
> 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.calcite.util.ReflectUtil$2.invoke(ReflectUtil.java:531)
> at
> org.apache.calcite.sql2rel.RelDecorrelator.getInvoke(RelDecorrelator.java:707)
> at
> org.apache.calcite.sql2rel.RelDecorrelator.decorrelateRel(RelDecorrelator.java:512)
> at
> org.apache.calcite.sql2rel.RelDecorrelator.decorrelateRel(RelDecorrelator.java:495)
> 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.calcite.util.ReflectUtil$2.invoke(ReflectUtil.java:531)
> at
> org.apache.calcite.sql2rel.RelDecorrelator.getInvoke(RelDecorrelator.java:707)
> at
> org.apache.calcite.sql2rel.RelDecorrelator.decorrelateRel(RelDecorrelator.java:1187)
> at
> org.apache.calcite.sql2rel.RelDecorrelator.decorrelateRel(RelDecorrelator.java:1169)
> 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.calcite.util.ReflectUtil$2.invoke(ReflectUtil.java:531)
> at
> org.apache.calcite.sql2rel.RelDecorrelator.getInvoke(RelDecorrelator.java:707)
> at
>
[jira] [Commented] (CALCITE-6213) The default behavior of NullCollation in Presto is LAST
[
https://issues.apache.org/jira/browse/CALCITE-6213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17808736#comment-17808736
]
EveyWu commented on CALCITE-6213:
-
[~tanclary]
I have submitted the pull request，thank you for helping me review the code
> The default behavior of NullCollation in Presto is LAST
> ---
>
> Key: CALCITE-6213
> URL: https://issues.apache.org/jira/browse/CALCITE-6213
> Project: Calcite
> Issue Type: Bug
>Reporter: EveyWu
>Priority: Major
> Labels: pull-request-available
> Attachments: image-2024-01-19-23-54-26-383.png,
> image-2024-01-19-23-57-00-252.png
>
>
> [https://prestodb.io/docs/0.285/sql/select.html]
> Presto default null ordering is NULLS LAST
> !image-2024-01-19-23-54-26-383.png|width=511,height=168!
>
> Demo：select by presto with nulls last
> {code:java}
> select * from product order by brand_name; {code}
> !image-2024-01-19-23-57-00-252.png|width=517,height=83!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CALCITE-6213) The default behavior of NullCollation in Presto is LAST
[
https://issues.apache.org/jira/browse/CALCITE-6213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated CALCITE-6213:
Labels: pull-request-available (was: )
> The default behavior of NullCollation in Presto is LAST
> ---
>
> Key: CALCITE-6213
> URL: https://issues.apache.org/jira/browse/CALCITE-6213
> Project: Calcite
> Issue Type: Bug
>Reporter: EveyWu
>Priority: Major
> Labels: pull-request-available
> Attachments: image-2024-01-19-23-54-26-383.png,
> image-2024-01-19-23-57-00-252.png
>
>
> [https://prestodb.io/docs/0.285/sql/select.html]
> Presto default null ordering is NULLS LAST
> !image-2024-01-19-23-54-26-383.png|width=511,height=168!
>
> Demo：select by presto with nulls last
> {code:java}
> select * from product order by brand_name; {code}
> !image-2024-01-19-23-57-00-252.png|width=517,height=83!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CALCITE-6209) Long queries are failing with "java.net.SocketTimeoutException: Read timed out" after 3 minutes
[
https://issues.apache.org/jira/browse/CALCITE-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin updated CALCITE-6209:
Description:
Long queries are failing with "java.net.SocketTimeoutException: Read timed out"
after 3 minutes.
It's expected that they take more than 3 minutes and we need some way to
increase timeout.
I tried to change it via +http_connection_timeout+ property but it didn't help.
Looks like that property is related to connect timeout only, but not to request
timeout.
I checked source code but didn't found any ways to change it there.
Looks like it's always using default timeout=3minutes.
!screenshot-1.png!
Stack-trace:
{code:java}
org.jkiss.dbeaver.model.sql.DBSQLException: SQL Error: Error while executing
SQL "SELECT count(1) FROM trace": java.net.SocketTimeoutException: Read timed
out
at
org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.executeStatement(JDBCStatementImpl.java:133)
at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.executeStatement(SQLQueryJob.java:600)
at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.lambda$2(SQLQueryJob.java:503)
at
org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:190)
at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.executeSingleQuery(SQLQueryJob.java:510)
at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.extractData(SQLQueryJob.java:962)
at
org.jkiss.dbeaver.ui.editors.sql.SQLEditor$QueryResultsContainer.readData(SQLEditor.java:4130)
at
org.jkiss.dbeaver.ui.controls.resultset.ResultSetJobDataRead.lambda$0(ResultSetJobDataRead.java:123)
at
org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:190)
at
org.jkiss.dbeaver.ui.controls.resultset.ResultSetJobDataRead.run(ResultSetJobDataRead.java:121)
at
org.jkiss.dbeaver.ui.controls.resultset.ResultSetViewer$ResultSetDataPumpJob.run(ResultSetViewer.java:5148)
at org.jkiss.dbeaver.model.runtime.AbstractJob.run(AbstractJob.java:105)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
Caused by: java.sql.SQLException: Error while executing SQL "SELECT count(1)
FROM trace": java.net.SocketTimeoutException: Read timed out
at org.apache.calcite.avatica.Helper.createException(Helper.java:56)
at org.apache.calcite.avatica.Helper.createException(Helper.java:41)
at
org.apache.calcite.avatica.AvaticaStatement.executeInternal(AvaticaStatement.java:164)
at
org.apache.calcite.avatica.AvaticaStatement.execute(AvaticaStatement.java:218)
at
org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.execute(JDBCStatementImpl.java:330)
at
org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.executeStatement(JDBCStatementImpl.java:131)
... 12 more
Caused by: java.lang.RuntimeException: java.net.SocketTimeoutException: Read
timed out
at
org.apache.calcite.avatica.remote.AvaticaCommonsHttpClientImpl.send(AvaticaCommonsHttpClientImpl.java:155)
at
org.apache.calcite.avatica.remote.RemoteService.apply(RemoteService.java:36)
at
org.apache.calcite.avatica.remote.JsonService.apply(JsonService.java:140)
at
org.apache.calcite.avatica.remote.RemoteMeta$14.call(RemoteMeta.java:310)
at
org.apache.calcite.avatica.remote.RemoteMeta$14.call(RemoteMeta.java:307)
at
org.apache.calcite.avatica.AvaticaConnection.invokeWithRetries(AvaticaConnection.java:795)
at
org.apache.calcite.avatica.remote.RemoteMeta.fetch(RemoteMeta.java:306)
at
org.apache.calcite.avatica.MetaImpl$FetchIterator.moveNext(MetaImpl.java:1643)
at
org.apache.calcite.avatica.MetaImpl$FetchIterator.(MetaImpl.java:1611)
at
org.apache.calcite.avatica.MetaImpl$FetchIterator.(MetaImpl.java:1586)
at
org.apache.calcite.avatica.MetaImpl$FetchIterable.iterator(MetaImpl.java:1581)
at org.apache.calcite.avatica.MetaImpl.createCursor(MetaImpl.java:98)
at
org.apache.calcite.avatica.AvaticaResultSet.execute(AvaticaResultSet.java:186)
at
org.apache.calcite.avatica.AvaticaConnection$1.execute(AvaticaConnection.java:669)
at
org.apache.calcite.avatica.remote.RemoteMeta$13.call(RemoteMeta.java:283)
at
org.apache.calcite.avatica.remote.RemoteMeta$13.call(RemoteMeta.java:263)
at
org.apache.calcite.avatica.AvaticaConnection.invokeWithRetries(AvaticaConnection.java:795)
at
org.apache.calcite.avatica.remote.RemoteMeta.prepareAndExecute(RemoteMeta.java:262)
at
org.apache.calcite.avatica.AvaticaConnection.prepareAndExecuteInternal(AvaticaConnection.java:677)
at
org.apache.calcite.avatica.AvaticaStatement.executeInternal(AvaticaStatement.java:157)
... 15 more
Caused by: java.net.SocketTimeoutException: Read timed out
at
[jira] [Commented] (CALCITE-6209) Long queries are failing with "java.net.SocketTimeoutException: Read timed out" after 3 minutes
[
https://issues.apache.org/jira/browse/CALCITE-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17808719#comment-17808719
]
Konstantin commented on CALCITE-6209:
-
>>Based on the above, please change the ticket description.
ok, changed
> Long queries are failing with "java.net.SocketTimeoutException: Read timed
> out" after 3 minutes
> ---
>
> Key: CALCITE-6209
> URL: https://issues.apache.org/jira/browse/CALCITE-6209
> Project: Calcite
> Issue Type: Bug
> Components: avatica
>Affects Versions: avatica-1.24.0
>Reporter: Konstantin
>Priority: Critical
> Attachments: screenshot-1.png
>
>
> Long queries are failing with "java.net.SocketTimeoutException: Read timed
> out" after 3 minutes.
> It's expected that they take more than 3 minutes and we need some way to
> increase timeout.
> I tried to change it via +http_connection_timeout+ property but it didn't
> help.
> Looks like that property is related to connect timeout only, but not to
> request timeout.
> I checked source code but didn't found any ways to change it there.
> Looks like it's always using default timeout=3minutes.
> !screenshot-1.png!
> Stack-trace:
> {code:java}
> org.jkiss.dbeaver.model.sql.DBSQLException: SQL Error: Error while executing
> SQL "SELECT count(1) FROM trace": java.net.SocketTimeoutException: Read timed
> out
> at
> org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.executeStatement(JDBCStatementImpl.java:133)
> at
> org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.executeStatement(SQLQueryJob.java:600)
> at
> org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.lambda$2(SQLQueryJob.java:503)
> at
> org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:190)
> at
> org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.executeSingleQuery(SQLQueryJob.java:510)
> at
> org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.extractData(SQLQueryJob.java:962)
> at
> org.jkiss.dbeaver.ui.editors.sql.SQLEditor$QueryResultsContainer.readData(SQLEditor.java:4130)
> at
> org.jkiss.dbeaver.ui.controls.resultset.ResultSetJobDataRead.lambda$0(ResultSetJobDataRead.java:123)
> at
> org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:190)
> at
> org.jkiss.dbeaver.ui.controls.resultset.ResultSetJobDataRead.run(ResultSetJobDataRead.java:121)
> at
> org.jkiss.dbeaver.ui.controls.resultset.ResultSetViewer$ResultSetDataPumpJob.run(ResultSetViewer.java:5148)
> at org.jkiss.dbeaver.model.runtime.AbstractJob.run(AbstractJob.java:105)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
> Caused by: java.sql.SQLException: Error while executing SQL "SELECT count(1)
> FROM trace": java.net.SocketTimeoutException: Read timed out
> at org.apache.calcite.avatica.Helper.createException(Helper.java:56)
> at org.apache.calcite.avatica.Helper.createException(Helper.java:41)
> at
> org.apache.calcite.avatica.AvaticaStatement.executeInternal(AvaticaStatement.java:164)
> at
> org.apache.calcite.avatica.AvaticaStatement.execute(AvaticaStatement.java:218)
> at
> org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.execute(JDBCStatementImpl.java:330)
> at
> org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.executeStatement(JDBCStatementImpl.java:131)
> ... 12 more
> Caused by: java.lang.RuntimeException: java.net.SocketTimeoutException: Read
> timed out
> at
> org.apache.calcite.avatica.remote.AvaticaCommonsHttpClientImpl.send(AvaticaCommonsHttpClientImpl.java:155)
> at
> org.apache.calcite.avatica.remote.RemoteService.apply(RemoteService.java:36)
> at
> org.apache.calcite.avatica.remote.JsonService.apply(JsonService.java:140)
> at
> org.apache.calcite.avatica.remote.RemoteMeta$14.call(RemoteMeta.java:310)
> at
> org.apache.calcite.avatica.remote.RemoteMeta$14.call(RemoteMeta.java:307)
> at
> org.apache.calcite.avatica.AvaticaConnection.invokeWithRetries(AvaticaConnection.java:795)
> at
> org.apache.calcite.avatica.remote.RemoteMeta.fetch(RemoteMeta.java:306)
> at
> org.apache.calcite.avatica.MetaImpl$FetchIterator.moveNext(MetaImpl.java:1643)
> at
> org.apache.calcite.avatica.MetaImpl$FetchIterator.(MetaImpl.java:1611)
> at
> org.apache.calcite.avatica.MetaImpl$FetchIterator.(MetaImpl.java:1586)
> at
> org.apache.calcite.avatica.MetaImpl$FetchIterable.iterator(MetaImpl.java:1581)
> at org.apache.calcite.avatica.MetaImpl.createCursor(MetaImpl.java:98)
> at
> org.apache.calcite.avatica.AvaticaResultSet.execute(AvaticaResultSet.java:186)
> at
>
[jira] [Updated] (CALCITE-6209) Long queries are failing with "java.net.SocketTimeoutException: Read timed out" after 3 minutes
[
https://issues.apache.org/jira/browse/CALCITE-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin updated CALCITE-6209:
Description:
Long queries are failing with "java.net.SocketTimeoutException: Read timed out"
after 3 minutes.
I tried to change it via +http_connection_timeout+ property but it didn't help.
Looks like that property is related to connect timeout only, but not to request
timeout.
I checked source code but didn't found any ways to change it there.
Looks like it's always using default timeout=3minutes.
!screenshot-1.png!
Stack-trace:
{code:java}
org.jkiss.dbeaver.model.sql.DBSQLException: SQL Error: Error while executing
SQL "SELECT count(1) FROM trace": java.net.SocketTimeoutException: Read timed
out
at
org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.executeStatement(JDBCStatementImpl.java:133)
at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.executeStatement(SQLQueryJob.java:600)
at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.lambda$2(SQLQueryJob.java:503)
at
org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:190)
at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.executeSingleQuery(SQLQueryJob.java:510)
at
org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.extractData(SQLQueryJob.java:962)
at
org.jkiss.dbeaver.ui.editors.sql.SQLEditor$QueryResultsContainer.readData(SQLEditor.java:4130)
at
org.jkiss.dbeaver.ui.controls.resultset.ResultSetJobDataRead.lambda$0(ResultSetJobDataRead.java:123)
at
org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:190)
at
org.jkiss.dbeaver.ui.controls.resultset.ResultSetJobDataRead.run(ResultSetJobDataRead.java:121)
at
org.jkiss.dbeaver.ui.controls.resultset.ResultSetViewer$ResultSetDataPumpJob.run(ResultSetViewer.java:5148)
at org.jkiss.dbeaver.model.runtime.AbstractJob.run(AbstractJob.java:105)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
Caused by: java.sql.SQLException: Error while executing SQL "SELECT count(1)
FROM trace": java.net.SocketTimeoutException: Read timed out
at org.apache.calcite.avatica.Helper.createException(Helper.java:56)
at org.apache.calcite.avatica.Helper.createException(Helper.java:41)
at
org.apache.calcite.avatica.AvaticaStatement.executeInternal(AvaticaStatement.java:164)
at
org.apache.calcite.avatica.AvaticaStatement.execute(AvaticaStatement.java:218)
at
org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.execute(JDBCStatementImpl.java:330)
at
org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.executeStatement(JDBCStatementImpl.java:131)
... 12 more
Caused by: java.lang.RuntimeException: java.net.SocketTimeoutException: Read
timed out
at
org.apache.calcite.avatica.remote.AvaticaCommonsHttpClientImpl.send(AvaticaCommonsHttpClientImpl.java:155)
at
org.apache.calcite.avatica.remote.RemoteService.apply(RemoteService.java:36)
at
org.apache.calcite.avatica.remote.JsonService.apply(JsonService.java:140)
at
org.apache.calcite.avatica.remote.RemoteMeta$14.call(RemoteMeta.java:310)
at
org.apache.calcite.avatica.remote.RemoteMeta$14.call(RemoteMeta.java:307)
at
org.apache.calcite.avatica.AvaticaConnection.invokeWithRetries(AvaticaConnection.java:795)
at
org.apache.calcite.avatica.remote.RemoteMeta.fetch(RemoteMeta.java:306)
at
org.apache.calcite.avatica.MetaImpl$FetchIterator.moveNext(MetaImpl.java:1643)
at
org.apache.calcite.avatica.MetaImpl$FetchIterator.(MetaImpl.java:1611)
at
org.apache.calcite.avatica.MetaImpl$FetchIterator.(MetaImpl.java:1586)
at
org.apache.calcite.avatica.MetaImpl$FetchIterable.iterator(MetaImpl.java:1581)
at org.apache.calcite.avatica.MetaImpl.createCursor(MetaImpl.java:98)
at
org.apache.calcite.avatica.AvaticaResultSet.execute(AvaticaResultSet.java:186)
at
org.apache.calcite.avatica.AvaticaConnection$1.execute(AvaticaConnection.java:669)
at
org.apache.calcite.avatica.remote.RemoteMeta$13.call(RemoteMeta.java:283)
at
org.apache.calcite.avatica.remote.RemoteMeta$13.call(RemoteMeta.java:263)
at
org.apache.calcite.avatica.AvaticaConnection.invokeWithRetries(AvaticaConnection.java:795)
at
org.apache.calcite.avatica.remote.RemoteMeta.prepareAndExecute(RemoteMeta.java:262)
at
org.apache.calcite.avatica.AvaticaConnection.prepareAndExecuteInternal(AvaticaConnection.java:677)
at
org.apache.calcite.avatica.AvaticaStatement.executeInternal(AvaticaStatement.java:157)
... 15 more
Caused by: java.net.SocketTimeoutException: Read timed out
at java.base/sun.nio.ch.NioSocketImpl.timedRead(Unknown Source)
at java.base/sun.nio.ch.NioSocketImpl.implRead(Unknown Source)
[jira] [Comment Edited] (CALCITE-6213) The default behavior of NullCollation in Presto is LAST
[
https://issues.apache.org/jira/browse/CALCITE-6213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17808716#comment-17808716
]
Tanner Clary edited comment on CALCITE-6213 at 1/19/24 4:04 PM:
Hi [~eveywu] the fix for this is probably ~1 line change and a test or two. Let
me know if you need help with review and thanks for filing this issue.
The [{{PrestoSqlDialect}}
class|https://github.com/apache/calcite/blob/main/core/src/main/java/org/apache/calcite/sql/dialect/PrestoSqlDialect.java]
is probably a good place to start.
was (Author: JIRAUSER298151):
Hi [~eveywu] the fix for this is probably ~1 line change and a test or two. Let
me know if you need help with review and thanks for filing this issue.
> The default behavior of NullCollation in Presto is LAST
> ---
>
> Key: CALCITE-6213
> URL: https://issues.apache.org/jira/browse/CALCITE-6213
> Project: Calcite
> Issue Type: Bug
>Reporter: EveyWu
>Priority: Major
> Attachments: image-2024-01-19-23-54-26-383.png,
> image-2024-01-19-23-57-00-252.png
>
>
> [https://prestodb.io/docs/0.285/sql/select.html]
> Presto default null ordering is NULLS LAST
> !image-2024-01-19-23-54-26-383.png|width=511,height=168!
>
> Demo：select by presto with nulls last
> {code:java}
> select * from product order by brand_name; {code}
> !image-2024-01-19-23-57-00-252.png|width=517,height=83!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CALCITE-6209) Long queries are failing with "java.net.SocketTimeoutException: Read timed out" after 3 minutes
[
https://issues.apache.org/jira/browse/CALCITE-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin updated CALCITE-6209:
Summary: Long queries are failing with "java.net.SocketTimeoutException:
Read timed out" after 3 minutes (was: All queries are failing with
"java.net.SocketTimeoutException: Read timed out" after 3 minutes)
> Long queries are failing with "java.net.SocketTimeoutException: Read timed
> out" after 3 minutes
> ---
>
> Key: CALCITE-6209
> URL: https://issues.apache.org/jira/browse/CALCITE-6209
> Project: Calcite
> Issue Type: Bug
> Components: avatica
>Affects Versions: avatica-1.24.0
>Reporter: Konstantin
>Priority: Critical
> Attachments: screenshot-1.png
>
>
> All queries are failing with "java.net.SocketTimeoutException: Read timed
> out" after 3 minutes.
> I tried to change it via +http_connection_timeout+ property but it didn't
> help.
> Looks like that property is related to connect timeout only, but not to
> request timeout.
> I checked source code but didn't found any ways to change it there.
> Looks like it's always using default timeout=3minutes.
> !screenshot-1.png!
> Stack-trace:
> {code:java}
> org.jkiss.dbeaver.model.sql.DBSQLException: SQL Error: Error while executing
> SQL "SELECT count(1) FROM trace": java.net.SocketTimeoutException: Read timed
> out
> at
> org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.executeStatement(JDBCStatementImpl.java:133)
> at
> org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.executeStatement(SQLQueryJob.java:600)
> at
> org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.lambda$2(SQLQueryJob.java:503)
> at
> org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:190)
> at
> org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.executeSingleQuery(SQLQueryJob.java:510)
> at
> org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.extractData(SQLQueryJob.java:962)
> at
> org.jkiss.dbeaver.ui.editors.sql.SQLEditor$QueryResultsContainer.readData(SQLEditor.java:4130)
> at
> org.jkiss.dbeaver.ui.controls.resultset.ResultSetJobDataRead.lambda$0(ResultSetJobDataRead.java:123)
> at
> org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:190)
> at
> org.jkiss.dbeaver.ui.controls.resultset.ResultSetJobDataRead.run(ResultSetJobDataRead.java:121)
> at
> org.jkiss.dbeaver.ui.controls.resultset.ResultSetViewer$ResultSetDataPumpJob.run(ResultSetViewer.java:5148)
> at org.jkiss.dbeaver.model.runtime.AbstractJob.run(AbstractJob.java:105)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
> Caused by: java.sql.SQLException: Error while executing SQL "SELECT count(1)
> FROM trace": java.net.SocketTimeoutException: Read timed out
> at org.apache.calcite.avatica.Helper.createException(Helper.java:56)
> at org.apache.calcite.avatica.Helper.createException(Helper.java:41)
> at
> org.apache.calcite.avatica.AvaticaStatement.executeInternal(AvaticaStatement.java:164)
> at
> org.apache.calcite.avatica.AvaticaStatement.execute(AvaticaStatement.java:218)
> at
> org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.execute(JDBCStatementImpl.java:330)
> at
> org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.executeStatement(JDBCStatementImpl.java:131)
> ... 12 more
> Caused by: java.lang.RuntimeException: java.net.SocketTimeoutException: Read
> timed out
> at
> org.apache.calcite.avatica.remote.AvaticaCommonsHttpClientImpl.send(AvaticaCommonsHttpClientImpl.java:155)
> at
> org.apache.calcite.avatica.remote.RemoteService.apply(RemoteService.java:36)
> at
> org.apache.calcite.avatica.remote.JsonService.apply(JsonService.java:140)
> at
> org.apache.calcite.avatica.remote.RemoteMeta$14.call(RemoteMeta.java:310)
> at
> org.apache.calcite.avatica.remote.RemoteMeta$14.call(RemoteMeta.java:307)
> at
> org.apache.calcite.avatica.AvaticaConnection.invokeWithRetries(AvaticaConnection.java:795)
> at
> org.apache.calcite.avatica.remote.RemoteMeta.fetch(RemoteMeta.java:306)
> at
> org.apache.calcite.avatica.MetaImpl$FetchIterator.moveNext(MetaImpl.java:1643)
> at
> org.apache.calcite.avatica.MetaImpl$FetchIterator.(MetaImpl.java:1611)
> at
> org.apache.calcite.avatica.MetaImpl$FetchIterator.(MetaImpl.java:1586)
> at
> org.apache.calcite.avatica.MetaImpl$FetchIterable.iterator(MetaImpl.java:1581)
> at org.apache.calcite.avatica.MetaImpl.createCursor(MetaImpl.java:98)
> at
> org.apache.calcite.avatica.AvaticaResultSet.execute(AvaticaResultSet.java:186)
> at
>
[jira] [Commented] (CALCITE-6213) The default behavior of NullCollation in Presto is LAST
[
https://issues.apache.org/jira/browse/CALCITE-6213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17808716#comment-17808716
]
Tanner Clary commented on CALCITE-6213:
---
Hi [~eveywu] the fix for this is probably ~1 line change and a test or two. Let
me know if you need help with review and thanks for filing this issue.
> The default behavior of NullCollation in Presto is LAST
> ---
>
> Key: CALCITE-6213
> URL: https://issues.apache.org/jira/browse/CALCITE-6213
> Project: Calcite
> Issue Type: Bug
>Reporter: EveyWu
>Priority: Major
> Attachments: image-2024-01-19-23-54-26-383.png,
> image-2024-01-19-23-57-00-252.png
>
>
> [https://prestodb.io/docs/0.285/sql/select.html]
> Presto default null ordering is NULLS LAST
> !image-2024-01-19-23-54-26-383.png|width=511,height=168!
>
> Demo：select by presto with nulls last
> {code:java}
> select * from product order by brand_name; {code}
> !image-2024-01-19-23-57-00-252.png|width=517,height=83!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CALCITE-6213) The default behavior of NullCollation in Presto is LAST
EveyWu created CALCITE-6213:
---
Summary: The default behavior of NullCollation in Presto is LAST
Key: CALCITE-6213
URL: https://issues.apache.org/jira/browse/CALCITE-6213
Project: Calcite
Issue Type: Bug
Reporter: EveyWu
Attachments: image-2024-01-19-23-54-26-383.png,
image-2024-01-19-23-57-00-252.png
[https://prestodb.io/docs/0.285/sql/select.html]
Presto default null ordering is NULLS LAST
!image-2024-01-19-23-54-26-383.png|width=511,height=168!
Demo：select by presto with nulls last
{code:java}
select * from product order by brand_name; {code}
!image-2024-01-19-23-57-00-252.png|width=517,height=83!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CALCITE-6209) All queries are failing with "java.net.SocketTimeoutException: Read timed out" after 3 minutes
[
https://issues.apache.org/jira/browse/CALCITE-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17808556#comment-17808556
]
Istvan Toth commented on CALCITE-6209:
--
I find it strange that this hasn't come up yet, but it's feasible that we
should expose more timeout parameters (or perhaps enable http keepalive).
> All queries are failing with "java.net.SocketTimeoutException: Read timed
> out" after 3 minutes
> --
>
> Key: CALCITE-6209
> URL: https://issues.apache.org/jira/browse/CALCITE-6209
> Project: Calcite
> Issue Type: Bug
> Components: avatica
>Affects Versions: avatica-1.24.0
>Reporter: Konstantin
>Priority: Critical
> Attachments: screenshot-1.png
>
>
> All queries are failing with "java.net.SocketTimeoutException: Read timed
> out" after 3 minutes.
> I tried to change it via +http_connection_timeout+ property but it didn't
> help.
> Looks like that property is related to connect timeout only, but not to
> request timeout.
> I checked source code but didn't found any ways to change it there.
> Looks like it's always using default timeout=3minutes.
> !screenshot-1.png!
> Stack-trace:
> {code:java}
> org.jkiss.dbeaver.model.sql.DBSQLException: SQL Error: Error while executing
> SQL "SELECT count(1) FROM trace": java.net.SocketTimeoutException: Read timed
> out
> at
> org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.executeStatement(JDBCStatementImpl.java:133)
> at
> org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.executeStatement(SQLQueryJob.java:600)
> at
> org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.lambda$2(SQLQueryJob.java:503)
> at
> org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:190)
> at
> org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.executeSingleQuery(SQLQueryJob.java:510)
> at
> org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.extractData(SQLQueryJob.java:962)
> at
> org.jkiss.dbeaver.ui.editors.sql.SQLEditor$QueryResultsContainer.readData(SQLEditor.java:4130)
> at
> org.jkiss.dbeaver.ui.controls.resultset.ResultSetJobDataRead.lambda$0(ResultSetJobDataRead.java:123)
> at
> org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:190)
> at
> org.jkiss.dbeaver.ui.controls.resultset.ResultSetJobDataRead.run(ResultSetJobDataRead.java:121)
> at
> org.jkiss.dbeaver.ui.controls.resultset.ResultSetViewer$ResultSetDataPumpJob.run(ResultSetViewer.java:5148)
> at org.jkiss.dbeaver.model.runtime.AbstractJob.run(AbstractJob.java:105)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
> Caused by: java.sql.SQLException: Error while executing SQL "SELECT count(1)
> FROM trace": java.net.SocketTimeoutException: Read timed out
> at org.apache.calcite.avatica.Helper.createException(Helper.java:56)
> at org.apache.calcite.avatica.Helper.createException(Helper.java:41)
> at
> org.apache.calcite.avatica.AvaticaStatement.executeInternal(AvaticaStatement.java:164)
> at
> org.apache.calcite.avatica.AvaticaStatement.execute(AvaticaStatement.java:218)
> at
> org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.execute(JDBCStatementImpl.java:330)
> at
> org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.executeStatement(JDBCStatementImpl.java:131)
> ... 12 more
> Caused by: java.lang.RuntimeException: java.net.SocketTimeoutException: Read
> timed out
> at
> org.apache.calcite.avatica.remote.AvaticaCommonsHttpClientImpl.send(AvaticaCommonsHttpClientImpl.java:155)
> at
> org.apache.calcite.avatica.remote.RemoteService.apply(RemoteService.java:36)
> at
> org.apache.calcite.avatica.remote.JsonService.apply(JsonService.java:140)
> at
> org.apache.calcite.avatica.remote.RemoteMeta$14.call(RemoteMeta.java:310)
> at
> org.apache.calcite.avatica.remote.RemoteMeta$14.call(RemoteMeta.java:307)
> at
> org.apache.calcite.avatica.AvaticaConnection.invokeWithRetries(AvaticaConnection.java:795)
> at
> org.apache.calcite.avatica.remote.RemoteMeta.fetch(RemoteMeta.java:306)
> at
> org.apache.calcite.avatica.MetaImpl$FetchIterator.moveNext(MetaImpl.java:1643)
> at
> org.apache.calcite.avatica.MetaImpl$FetchIterator.(MetaImpl.java:1611)
> at
> org.apache.calcite.avatica.MetaImpl$FetchIterator.(MetaImpl.java:1586)
> at
> org.apache.calcite.avatica.MetaImpl$FetchIterable.iterator(MetaImpl.java:1581)
> at org.apache.calcite.avatica.MetaImpl.createCursor(MetaImpl.java:98)
> at
> org.apache.calcite.avatica.AvaticaResultSet.execute(AvaticaResultSet.java:186)
> at
>
[jira] [Commented] (CALCITE-6209) All queries are failing with "java.net.SocketTimeoutException: Read timed out" after 3 minutes
[
https://issues.apache.org/jira/browse/CALCITE-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17808555#comment-17808555
]
Istvan Toth commented on CALCITE-6209:
--
Based on the above, please change the ticket description.
Something like "Long running queries..." would work.
"All queries are failing" implies that even fast queries are running for three
minutes the fail, which would definitely imply an user error.
> All queries are failing with "java.net.SocketTimeoutException: Read timed
> out" after 3 minutes
> --
>
> Key: CALCITE-6209
> URL: https://issues.apache.org/jira/browse/CALCITE-6209
> Project: Calcite
> Issue Type: Bug
> Components: avatica
>Affects Versions: avatica-1.24.0
>Reporter: Konstantin
>Priority: Critical
> Attachments: screenshot-1.png
>
>
> All queries are failing with "java.net.SocketTimeoutException: Read timed
> out" after 3 minutes.
> I tried to change it via +http_connection_timeout+ property but it didn't
> help.
> Looks like that property is related to connect timeout only, but not to
> request timeout.
> I checked source code but didn't found any ways to change it there.
> Looks like it's always using default timeout=3minutes.
> !screenshot-1.png!
> Stack-trace:
> {code:java}
> org.jkiss.dbeaver.model.sql.DBSQLException: SQL Error: Error while executing
> SQL "SELECT count(1) FROM trace": java.net.SocketTimeoutException: Read timed
> out
> at
> org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.executeStatement(JDBCStatementImpl.java:133)
> at
> org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.executeStatement(SQLQueryJob.java:600)
> at
> org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.lambda$2(SQLQueryJob.java:503)
> at
> org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:190)
> at
> org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.executeSingleQuery(SQLQueryJob.java:510)
> at
> org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.extractData(SQLQueryJob.java:962)
> at
> org.jkiss.dbeaver.ui.editors.sql.SQLEditor$QueryResultsContainer.readData(SQLEditor.java:4130)
> at
> org.jkiss.dbeaver.ui.controls.resultset.ResultSetJobDataRead.lambda$0(ResultSetJobDataRead.java:123)
> at
> org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:190)
> at
> org.jkiss.dbeaver.ui.controls.resultset.ResultSetJobDataRead.run(ResultSetJobDataRead.java:121)
> at
> org.jkiss.dbeaver.ui.controls.resultset.ResultSetViewer$ResultSetDataPumpJob.run(ResultSetViewer.java:5148)
> at org.jkiss.dbeaver.model.runtime.AbstractJob.run(AbstractJob.java:105)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
> Caused by: java.sql.SQLException: Error while executing SQL "SELECT count(1)
> FROM trace": java.net.SocketTimeoutException: Read timed out
> at org.apache.calcite.avatica.Helper.createException(Helper.java:56)
> at org.apache.calcite.avatica.Helper.createException(Helper.java:41)
> at
> org.apache.calcite.avatica.AvaticaStatement.executeInternal(AvaticaStatement.java:164)
> at
> org.apache.calcite.avatica.AvaticaStatement.execute(AvaticaStatement.java:218)
> at
> org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.execute(JDBCStatementImpl.java:330)
> at
> org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.executeStatement(JDBCStatementImpl.java:131)
> ... 12 more
> Caused by: java.lang.RuntimeException: java.net.SocketTimeoutException: Read
> timed out
> at
> org.apache.calcite.avatica.remote.AvaticaCommonsHttpClientImpl.send(AvaticaCommonsHttpClientImpl.java:155)
> at
> org.apache.calcite.avatica.remote.RemoteService.apply(RemoteService.java:36)
> at
> org.apache.calcite.avatica.remote.JsonService.apply(JsonService.java:140)
> at
> org.apache.calcite.avatica.remote.RemoteMeta$14.call(RemoteMeta.java:310)
> at
> org.apache.calcite.avatica.remote.RemoteMeta$14.call(RemoteMeta.java:307)
> at
> org.apache.calcite.avatica.AvaticaConnection.invokeWithRetries(AvaticaConnection.java:795)
> at
> org.apache.calcite.avatica.remote.RemoteMeta.fetch(RemoteMeta.java:306)
> at
> org.apache.calcite.avatica.MetaImpl$FetchIterator.moveNext(MetaImpl.java:1643)
> at
> org.apache.calcite.avatica.MetaImpl$FetchIterator.(MetaImpl.java:1611)
> at
> org.apache.calcite.avatica.MetaImpl$FetchIterator.(MetaImpl.java:1586)
> at
> org.apache.calcite.avatica.MetaImpl$FetchIterable.iterator(MetaImpl.java:1581)
> at org.apache.calcite.avatica.MetaImpl.createCursor(MetaImpl.java:98)
> at
>
