[
https://issues.apache.org/jira/browse/PHOENIX-5051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chen Feng updated PHOENIX-5051:
---
Attachment: PHOENIX-5051-4.x-HBase-1.2-v1.patch
> ScanningResultIterator metric "RowsScanned" not
I think we have reached consensus about moving these modules into a
separate repo.
I filed PHOENIX-5062 and PHOENIX-5063.
On Tue, Dec 4, 2018 at 5:20 PM Alex Araujo wrote:
> > If we really want, I bet we could get rid of most of the code we have
> for PQS already and just push it into Avatica
Thomas D'Silva created PHOENIX-5063:
---
Summary: Create a new repo for the phoenix query server
Key: PHOENIX-5063
URL: https://issues.apache.org/jira/browse/PHOENIX-5063
Project: Phoenix
Thomas D'Silva created PHOENIX-5062:
---
Summary: Create a new repo for the phoenix connectors
Key: PHOENIX-5062
URL: https://issues.apache.org/jira/browse/PHOENIX-5062
Project: Phoenix
> If we really want, I bet we could get rid of most of the code we have
for PQS already and just push it into Avatica itself. Just a thought ;)
+1. Even willing to volunteer myself here.
On Tue, Dec 4, 2018 at 5:18 PM Josh Elser wrote:
> That makes the most sense to me.
>
> If we really want,
That makes the most sense to me.
If we really want, I bet we could get rid of most of the code we have
for PQS already and just push it into Avatica itself. Just a thought ;)
There are some other users of Avatica, but we are, far and away, the
most prevalent.
On 12/4/18 8:10 PM, Thomas
Should we have one repo for the connectors (phoenix-flume, phoenix-hive,
phoenix-kafka, phoenix-pig and phoenix-spark)
and a separate repo for the queryserver?
On Tue, Dec 4, 2018 at 3:58 PM Vincent Poon wrote:
> +1 to another repo for connectors
>
> On Mon, Dec 3, 2018 at 6:27 PM James Taylor
+1 to another repo for connectors
On Mon, Dec 3, 2018 at 6:27 PM James Taylor wrote:
> +1. Good idea, Thomas.
>
> On Mon, Dec 3, 2018 at 2:57 PM Thomas D'Silva
> wrote:
>
> > I believe we will be maintaining the 4.x branches which support HBase
> 1.2,
> > 1.3 and 1.4 for a while.
> > Should we
[
https://issues.apache.org/jira/browse/PHOENIX-5061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Geoffrey Jacoby updated PHOENIX-5061:
-
Summary: PhoenixIndexImportDirectMapper doesn't set SCN correctly for
indexes on
[
https://issues.apache.org/jira/browse/PHOENIX-5061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Geoffrey Jacoby updated PHOENIX-5061:
-
Summary: PhoenixIndexImportDirectMapper doesn't set correctly for indexes
on
Geoffrey Jacoby created PHOENIX-5061:
Summary: PhoenixIndexImportDirectMapper doesn't set SCN right for
indexes on transactional tables
Key: PHOENIX-5061
URL:
[
https://issues.apache.org/jira/browse/PHOENIX-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ankit Singhal updated PHOENIX-5060:
---
Attachment: PHOENIX-5060.patch
> DeleteFamily cells are getting skipped while building
Ankit Singhal created PHOENIX-5060:
--
Summary: DeleteFamily cells are getting skipped while building
Index data after HBASE-21158
Key: PHOENIX-5060
URL: https://issues.apache.org/jira/browse/PHOENIX-5060
Thomas D'Silva created PHOENIX-5059:
---
Summary: Use the Datasource v2 api in the spark connector
Key: PHOENIX-5059
URL: https://issues.apache.org/jira/browse/PHOENIX-5059
Project: Phoenix
[
https://issues.apache.org/jira/browse/PHOENIX-4781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Poon resolved PHOENIX-4781.
---
Resolution: Resolved
Pushed v5 to master and 4.x branches
> Phoenix client project's jar
[
https://issues.apache.org/jira/browse/PHOENIX-5051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas D'Silva reassigned PHOENIX-5051:
---
Assignee: Cheng Fan
> ScanningResultIterator metric "RowsScanned" not set
>
[
https://issues.apache.org/jira/browse/PHOENIX-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaanai updated PHOENIX-5055:
Description:
In order to get more performance, we split the list of mutations into multiple
batches in
[
https://issues.apache.org/jira/browse/PHOENIX-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaanai updated PHOENIX-5055:
Description:
In order to get more performance, we split the list of mutations into multiple
batches in
[
https://issues.apache.org/jira/browse/PHOENIX-5051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chen Feng updated PHOENIX-5051:
---
Affects Version/s: (was: 5.0.0)
> ScanningResultIterator metric "RowsScanned" not set
>
[
https://issues.apache.org/jira/browse/PHOENIX-5051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chen Feng updated PHOENIX-5051:
---
Fix Version/s: (was: 5.1.0)
(was: 4.15.0)
> ScanningResultIterator
20 matches
Mail list logo
