[
https://issues.apache.org/jira/browse/PHOENIX-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2970:
--
Summary: SpoolingResultIterator using memory too conservative,and it lead
to use temp file
[
https://issues.apache.org/jira/browse/PHOENIX-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2970:
--
Summary: SpoolingResultIterator using memory too conservative ,and it leads
to use temp file
[
https://issues.apache.org/jira/browse/PHOENIX-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2970:
--
Summary: SpoolingResultIterator using memory too conservative , which leads
to use temp file
chenglei created PHOENIX-2970:
-
Summary: SpoolingResultIterator using memory too conservative
Key: PHOENIX-2970
URL: https://issues.apache.org/jira/browse/PHOENIX-2970
Project: Phoenix
Issue
[
https://issues.apache.org/jira/browse/PHOENIX-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2970:
--
Description:
Even if SpoolingResultIterator will be deprecated, but HBase older than
than
[
https://issues.apache.org/jira/browse/PHOENIX-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2970:
--
Description:
Even if SpoolingResultIterator will be deprecated, but HBase older than than
0.98.17
[
https://issues.apache.org/jira/browse/PHOENIX-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2970:
--
Description:
Even if SpoolingResultIterator will be deprecated, but HBase older than than
0.98.17
[
https://issues.apache.org/jira/browse/PHOENIX-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2970:
--
Summary: SpoolingResultIterator using memory too conservatively , which
leads to using temp file
[
https://issues.apache.org/jira/browse/PHOENIX-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2970:
--
Description:
Even if SpoolingResultIterator will be deprecated, but HBase older than than
0.98.17
[
https://issues.apache.org/jira/browse/PHOENIX-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2970:
--
Description:
Even if SpoolingResultIterator will be deprecated, but HBase older than than
0.98.17
[
https://issues.apache.org/jira/browse/PHOENIX-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2970:
--
Summary: SpoolingResultIterator using memory too conservatively , which
leads to use temp file
[
https://issues.apache.org/jira/browse/PHOENIX-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2970:
--
Description:
Even if SpoolingResultIterator will be deprecated, but HBase older than
0.98.17 would
[
https://issues.apache.org/jira/browse/PHOENIX-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15331089#comment-15331089
]
chenglei commented on PHOENIX-2876:
---
I think the AggregationManager's compile method should be static
[
https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2900:
--
Description:
When I join a salted table (which has been split after creation) with another
table in
[
https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2900:
--
Summary: Once a salted table 's first region has been split, the join SQL
which the salted table as
[
https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2900:
--
Summary: Once a salted table 's first region has been split, the join SQL
which the salted table as
[
https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2900:
--
Summary: Once a salted table 's first region has been split, the join SQL
which the salted table as
[
https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2613:
--
Description:
In pheonix 4.6,any column of multi-part primary key can be null.If a table has
one row
[
https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2613:
--
Description:
In pheonix 4.6,any column of multi-part primary key can be null.If a table has
one row
[
https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2613:
--
Description:
In pheonix 4.6,any column of multi-part primary key can be null.If a table has
one row
[
https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2613:
--
Description:
In pheonix 4.6,any column of multi-part primary key can be null.If a table has
one row
[
https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2613:
--
Description:
In pheonix 4.6,any column of multi-part primary key can be null.If a table has
one row
[
https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2613:
--
Description:
In pheonix 4.6,any column of multi-part primary key can be null.If a table has
one row
[
https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2613:
--
Description:
In pheonix 4.6,any column of multi-part primary key can be null.If a table has
one row
[
https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2613:
--
Description:
In pheonix 4.6,any column of multi-part primary key can be null.If a table has
one row
[
https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15111984#comment-15111984
]
chenglei commented on PHOENIX-2613:
---
I agree the cause of this issue is the following if condition in
[
https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15111984#comment-15111984
]
chenglei edited comment on PHOENIX-2613 at 1/22/16 6:16 AM:
I agree the
[
https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2613:
--
Description:
In pheonix 4.6,any column of multi-part primary key can be null.If a table has
one row
[
https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2613:
--
Description:
In pheonix 4.6,any column of multi-part primary key can be null.If a table has
one row
[
https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2613:
--
Description:
In pheonix 4.6,any column of multi-part primary key can be null.If a table has
one row
[
https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2613:
--
Description:
In pheonix 4.6,any column of multi-part primary key can be null.If a table has
one row
[
https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2613:
--
Description:
In pheonix 4.6,any column of multi-part primary key can be null.If a table has
one row
[
https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2613:
--
Description:
In pheonix 4.6,any column of multi-part primary key can be null.If a table has
one row
[
https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2613:
--
Description:
In pheonix 4.6,any column of multi-part primary key can be null.If a table has
one row
[
https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2613:
--
Description:
In pheonix 4.6,any column of multi-part primary key can be null.If a table has
one row
[
https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2613:
--
Description:
In pheonix 4.6,any column of multi-part primary key can be null.If a table has
one row
[
https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2613:
--
Description:
In pheonix 4.6,any column of multi-part primary key can be null.If a table has
one row
[
https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2613:
--
Description:
In pheonix 4.6,any column of multi-part primary key can be null.If a table has
one row
[
https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2613:
--
Description:
In pheonix 4.6,any column of multi-part primary key can be null.If a table has
one row
[
https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2613:
--
Description:
In pheonix 4.6,any column of multi-part primary key can be null.If a table has
one row
[
https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2613:
--
Description:
In pheonix 4.6,any column of multi-part primary key can be null.If a table has
one row
[
https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2613:
--
Description:
In pheonix 4.6,any column of multi-part primary key can be null.If a table has
one row
[
https://issues.apache.org/jira/browse/PHOENIX-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2613:
--
Description:
In pheonix 4.6,any column of multi-part primary key can be null.If a table has
one row
[
https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2753:
--
Summary: ClientAggregatePlan incorrectly using limit in aggregation may
cause sql with limit clause
[
https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2753:
--
Description:
When we execute a sql with subquery and aggregate,Phoenix may compile the sql
to a
[
https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2753:
--
Description:
When we execute a sql with subquery and aggregation,Phoenix may compile the sql
to get
[
https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2753:
--
Description:
When we execute a sql with subquery and aggregation,Phoenix may compile the sql
to get
[
https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2753:
--
Description:
When we execute a sql with subquery and aggregation,Phoenix may compile the sql
to get
[
https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2753:
--
Description:
When we execute a sql with subquery and aggregation,Phoenix may compile the sql
to get
[
https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2753:
--
Summary: ClientAggregatePlan incorrectly uses limit in aggregation may
cause sql with limit clause to
[
https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2753:
--
Fix Version/s: (was: 4.7.0)
> ClientAggregatePlan incorrectly uses limit in aggregation may cause
[
https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15185116#comment-15185116
]
chenglei edited comment on PHOENIX-2753 at 3/8/16 3:59 PM:
---
Sorry,I found the
chenglei created PHOENIX-2753:
-
Summary: ClientAggregatePlan incorrectly using limit in aggregate
may cause sql with limit clause to misbehave
Key: PHOENIX-2753
URL: https://issues.apache.org/jira/browse/PHOENIX-2753
[
https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2753:
--
Description:
When we execute a sql with subquery and aggregate,Phoenix may compile the sql
to a
[
https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2753:
--
Description:
When we execute a sql with subquery and aggregate,Phoenix may compile the sql
to a
[
https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2753:
--
Description:
When we execute a sql with subquery and aggregate,Phoenix may compile the sql
to a
[
https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2753:
--
Description:
When we execute a sql with subquery and aggregate,Phoenix may compile the sql
to a
[
https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2753:
--
Description:
When we execute a sql with subquery and aggregate,Phoenix may compile the sql
to a
[
https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2753:
--
Description:
When we execute a sql with subquery and aggregate,Phoenix may compile the sql
to a
[
https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2753:
--
Description:
When we execute a sql with subquery and aggregate,Phoenix may compile the sql
to a
[
https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2753:
--
Description:
When we execute a sql with subquery and aggregate,Phoenix may compile the sql
to a
[
https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2753:
--
Fix Version/s: 4.7.0
> ClientAggregatePlan incorrectly uses limit in aggregation may cause sql with
[
https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2753:
--
Description:
When we execute a sql with subquery and aggregate,Phoenix may compile the sql
to a
[
https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2753:
--
Description:
When we execute a sql with subquery and aggregate,Phoenix may compile the sql
to a
[
https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2753:
--
Description:
When we execute a sql with subquery and aggregate,Phoenix may compile the sql
to a
[
https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2753:
--
Description:
When we execute a sql with subquery and aggregate,Phoenix may compile the sql
to a
[
https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2753:
--
Description:
When we execute a sql with subquery and aggregation,Phoenix may compile the sql
to get
[
https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2753:
--
Description:
When we execute a sql with subquery and aggregation,Phoenix may compile the sql
to get
[
https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2753:
--
Description:
When we execute a sql with subquery and aggregate,Phoenix may compile the sql
to a
[
https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2753:
--
Description:
When we execute a sql with subquery and aggregate,Phoenix may compile the sql
to a
[
https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2753:
--
Description:
When we execute a sql with subquery and aggregate,Phoenix may compile the sql
to a
[
https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei resolved PHOENIX-2753.
---
Resolution: Fixed
sorry,I found the 2279 fixed this problem
> ClientAggregatePlan incorrectly uses
[
https://issues.apache.org/jira/browse/PHOENIX-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15185116#comment-15185116
]
chenglei edited comment on PHOENIX-2753 at 3/8/16 3:52 PM:
---
sorry,I found the
chenglei created PHOENIX-2748:
-
Summary: CsvToKeyValueMapper used by CsvBulkLoadTool should set
inner PhoenixConnection autocommit to false explicitly
Key: PHOENIX-2748
URL:
[
https://issues.apache.org/jira/browse/PHOENIX-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2748:
--
Summary: CsvToKeyValueMapper used by CsvBulkLoadTool should set inner
PhoenixConnection autoCommit to
[
https://issues.apache.org/jira/browse/PHOENIX-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2748:
--
Description:
CsvBulkLoadTool uses CsvToKeyValueMapper to convert csv record to KeyValues
which
[
https://issues.apache.org/jira/browse/PHOENIX-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2748:
--
Description:
CsvBulkLoadTool uses CsvToKeyValueMapper to convert csv record to KeyValues
which
[
https://issues.apache.org/jira/browse/PHOENIX-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2748:
--
Description:
CsvBulkLoadTool uses CsvToKeyValueMapper to convert csv record to KeyValues
which
[
https://issues.apache.org/jira/browse/PHOENIX-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2748:
--
Description:
CsvBulkLoadTool uses CsvToKeyValueMapper to convert csv record to KeyValues
which
[
https://issues.apache.org/jira/browse/PHOENIX-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2748:
--
Description:
CsvBulkLoadTool uses CsvToKeyValueMapper to convert csv record to
KeyValues
[
https://issues.apache.org/jira/browse/PHOENIX-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2748:
--
Description:
CsvBulkLoadTool uses CsvToKeyValueMapper to convert csv record to KeyValues
which
[
https://issues.apache.org/jira/browse/PHOENIX-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2748:
--
Description:
CsvBulkLoadTool uses CsvToKeyValueMapper to convert csv record to KeyValues
which
[
https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2900:
--
Description:
When I join a salted table (which has been split after creation) with another
table in
[
https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2900:
--
Priority: Major (was: Critical)
> Once a salted table 's first region has been split, the join SQL
[
https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2900:
--
Priority: Critical (was: Major)
> Once a salted table 's first region has been split, the join SQL
[
https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2900:
--
Description:
When I join a salted table (which is split after creation) with another table
in my
[
https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2900:
--
Description:
When I join a salted table (which is split after creation) with another table
in my
[
https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2900:
--
Description:
When I join a salted table (which is split after creation) with another table
in my
[
https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2900:
--
Description:
When I join a salted table (which is split after creation) with another table
in my
[
https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2900:
--
Description:
When I join a salted table (which is split after creation) with another table
in my
[
https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2900:
--
Description:
When I join a salted table (which is split after creation) with another table
in my
[
https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2900:
--
Description:
When I join a salted table (which is split after creation) with another table
in my
[
https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2900:
--
Summary: Once a salted table 's first region has been split, the Join SQL
which the salted table as
[
https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2900:
--
Description:
When I join a salted table (which is split after creation) with another table
in my
[
https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2900:
--
Description:
When I join a salted table (which is split after creation) with another table
in my
[
https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2900:
--
Description:
When I join a salted table (which is split after creation) with another table
in my
[
https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2900:
--
Description:
When I join a salted table (which is split after creation) with another table
in my
[
https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2900:
--
Description:
When I join a salted table (which is split after creation) with another table
in my
[
https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2900:
--
Description:
When I join a salted table (which is split after creation) with another table
in my
[
https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated PHOENIX-2900:
--
Summary: Once a salted table 's first region has been split, the join SQL
which the salted table as
1 - 100 of 874 matches
Mail list logo