[jira] [Assigned] (PHOENIX-6501) Use batching when joining data table rows with uncovered global index rows
[ https://issues.apache.org/jira/browse/PHOENIX-6501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl reassigned PHOENIX-6501: -- Assignee: Lars Hofhansl (was: Kadir OZDEMIR) > Use batching when joining data table rows with uncovered global index rows > -- > > Key: PHOENIX-6501 > URL: https://issues.apache.org/jira/browse/PHOENIX-6501 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.1.2 >Reporter: Kadir Ozdemir >Assignee: Lars Hofhansl >Priority: Major > Attachments: PHOENIX-6501.master.001.patch > > > PHOENIX-6458 extends the existing uncovered local index support for global > indexes. The current solution uses HBase get operations to join data table > rows with uncovered index rows on the server side. Doing a separate RPC call > for every data table row can be expensive. Instead, we can buffer lots of > data row keys in memory, use a skip scan filter and even multiple threads to > issue a separate scan for each data table region in parallel. This will > reduce the cost of join and also improve the performance. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (PHOENIX-6665) PreparedStatement#getMetaData() fails on parametrized "select next ? values for SEQ"
[
https://issues.apache.org/jira/browse/PHOENIX-6665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth updated PHOENIX-6665:
-
Summary: PreparedStatement#getMetaData() fails on parametrized "select next
? values for SEQ" (was: PreparedStatement#getMetaData() fails on paramatrized
"select next ? values for SEQ" )
> PreparedStatement#getMetaData() fails on parametrized "select next ? values
> for SEQ"
> -
>
> Key: PHOENIX-6665
> URL: https://issues.apache.org/jira/browse/PHOENIX-6665
> Project: Phoenix
> Issue Type: Bug
> Components: core
>Affects Versions: 5.2.0
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Major
>
>
> {code:java}
> PreparedStatement nextStmt = conn.prepareStatement("SELECT NEXT ? VALUES FOR
> SEQ_TABLE");
> nextStmt.getMetaData();{code}
> Fails.
> According to the PreparedStatement javadoc, this should work:
> {quote}
> Because a {{PreparedStatement}} object is precompiled, it is possible to know
> about the {{ResultSet}} object that it will return without having to execute
> it. Consequently, it is possible to invoke the method {{getMetaData}} on a
> {{PreparedStatement}} object rather than waiting to execute it and then
> invoking the {{ResultSet.getMetaData}} method on the {{ResultSet}} object
> that is returned.
> {quote}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (PHOENIX-6665) PreparedStatement#getMetaData() fails on paramatrized "select next ? values for SEQ"
[
https://issues.apache.org/jira/browse/PHOENIX-6665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth updated PHOENIX-6665:
-
Summary: PreparedStatement#getMetaData() fails on paramatrized "select next
? values for SEQ" (was: PreparedStatement#getMetaData() fails on parematrized
"select next ? values for SEQ" )
> PreparedStatement#getMetaData() fails on paramatrized "select next ? values
> for SEQ"
> -
>
> Key: PHOENIX-6665
> URL: https://issues.apache.org/jira/browse/PHOENIX-6665
> Project: Phoenix
> Issue Type: Bug
> Components: core
>Affects Versions: 5.2.0
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Major
>
>
> {code:java}
> PreparedStatement nextStmt = conn.prepareStatement("SELECT NEXT ? VALUES FOR
> SEQ_TABLE");
> nextStmt.getMetaData();{code}
> Fails.
> According to the PreparedStatement javadoc, this should work:
> {quote}
> Because a {{PreparedStatement}} object is precompiled, it is possible to know
> about the {{ResultSet}} object that it will return without having to execute
> it. Consequently, it is possible to invoke the method {{getMetaData}} on a
> {{PreparedStatement}} object rather than waiting to execute it and then
> invoking the {{ResultSet.getMetaData}} method on the {{ResultSet}} object
> that is returned.
> {quote}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (PHOENIX-6665) PreparedStatement#getMetaData() fails on parematrized "select next ? values for SEQ"
[
https://issues.apache.org/jira/browse/PHOENIX-6665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth reassigned PHOENIX-6665:
Assignee: Istvan Toth
> PreparedStatement#getMetaData() fails on parematrized "select next ? values
> for SEQ"
> -
>
> Key: PHOENIX-6665
> URL: https://issues.apache.org/jira/browse/PHOENIX-6665
> Project: Phoenix
> Issue Type: Bug
> Components: core
>Affects Versions: 5.2.0
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Major
>
>
> {code:java}
> PreparedStatement nextStmt = conn.prepareStatement("SELECT NEXT ? VALUES FOR
> SEQ_TABLE");
> nextStmt.getMetaData();{code}
> Fails.
> According to the PreparedStatement javadoc, this should work:
> {quote}
> Because a {{PreparedStatement}} object is precompiled, it is possible to know
> about the {{ResultSet}} object that it will return without having to execute
> it. Consequently, it is possible to invoke the method {{getMetaData}} on a
> {{PreparedStatement}} object rather than waiting to execute it and then
> invoking the {{ResultSet.getMetaData}} method on the {{ResultSet}} object
> that is returned.
> {quote}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (PHOENIX-6665) PreparedStatement#getMetaData() fails on parematrized "select next ? values for SEQ"
[
https://issues.apache.org/jira/browse/PHOENIX-6665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth updated PHOENIX-6665:
-
Summary: PreparedStatement#getMetaData() fails on parematrized "select next
? values for SEQ" (was: PreparedStatement#getMetaData() fails on paremetrized
"select next ? values for SEQ" )
> PreparedStatement#getMetaData() fails on parematrized "select next ? values
> for SEQ"
> -
>
> Key: PHOENIX-6665
> URL: https://issues.apache.org/jira/browse/PHOENIX-6665
> Project: Phoenix
> Issue Type: Bug
> Components: core
>Affects Versions: 5.2.0
>Reporter: Istvan Toth
>Priority: Major
>
>
> {code:java}
> PreparedStatement nextStmt = conn.prepareStatement("SELECT NEXT ? VALUES FOR
> SEQ_TABLE");
> nextStmt.getMetaData();{code}
> Fails.
> According to the PreparedStatement javadoc, this should work:
> {quote}
> Because a {{PreparedStatement}} object is precompiled, it is possible to know
> about the {{ResultSet}} object that it will return without having to execute
> it. Consequently, it is possible to invoke the method {{getMetaData}} on a
> {{PreparedStatement}} object rather than waiting to execute it and then
> invoking the {{ResultSet.getMetaData}} method on the {{ResultSet}} object
> that is returned.
> {quote}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
