[jira] [Updated] (PHOENIX-6044) Precommit script over-zealous zombie check may clobber parallel Phoenix test

[ https://issues.apache.org/jira/browse/PHOENIX-6044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated PHOENIX-6044: - Fix Version/s: 5.1.0 > Precommit script over-zealous zombie check may clobber parallel Phoenix

[jira] [Resolved] (PHOENIX-6044) Precommit script over-zealous zombie check may clobber parallel Phoenix test

[ https://issues.apache.org/jira/browse/PHOENIX-6044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved PHOENIX-6044. -- Resolution: Fixed Committed to master. (precommit always runs from master) Thanks for the re

[jira] [Resolved] (PHOENIX-6023) Wrong result when issuing query for an immutable table with multiple column families

[ https://issues.apache.org/jira/browse/PHOENIX-6023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved PHOENIX-6023. -- Resolution: Fixed Committed to 4.x as well. > Wrong result when issuing query for an immutab

[jira] [Reopened] (PHOENIX-6023) Wrong result when issuing query for an immutable table with multiple column families

[ https://issues.apache.org/jira/browse/PHOENIX-6023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth reopened PHOENIX-6023: -- Yes, we need this in 4.x as well. Thanks for reminding me, > Wrong result when issuing query for

[jira] [Created] (PHOENIX-6048) Strict batching in index rebuilds

Abhishek Singh Chouhan created PHOENIX-6048: --- Summary: Strict batching in index rebuilds Key: PHOENIX-6048 URL: https://issues.apache.org/jira/browse/PHOENIX-6048 Project: Phoenix I

[jira] [Updated] (PHOENIX-6045) Delete that should qualify for index path does not use index when multiple indexes are available.

[ https://issues.apache.org/jira/browse/PHOENIX-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-6045: -- Fix Version/s: 4.16.0 5.1.0 > Delete that should qualify for index

[jira] [Created] (PHOENIX-6047) Release phoenix-queryserver jars compatible with 4.15 and create a workflow for future 4.x releases

Chinmay Kulkarni created PHOENIX-6047: - Summary: Release phoenix-queryserver jars compatible with 4.15 and create a workflow for future 4.x releases Key: PHOENIX-6047 URL: https://issues.apache.org/jira/browse

[jira] [Created] (PHOENIX-6046) Release a phoenix-connectors jar compatible with 4.15 and create a workflow for future 4.x releases

Chinmay Kulkarni created PHOENIX-6046: - Summary: Release a phoenix-connectors jar compatible with 4.15 and create a workflow for future 4.x releases Key: PHOENIX-6046 URL: https://issues.apache.org/jira/browse

Re: How to check "split on" option on table

I would list table regions by either checking Hbase admin web UI or from the Hbase shell with list_regions 'table_name' and check that each region startKey matches your split points. Afaik there is no way for checking this from phoenix console. Also, these type of questions are a better fit for u

Fwd: How to check "split on" option on table

Hi folks, I would like to create a table with the « split on » option on one part of the primary key as follow : CREATE TABLE IF NOT EXISTS MYTABLE ("col1 " VARCHAR NOT NULL , "col2" VARCHAR, "col3" VARCHAR NOT NULL, "col4" VARCHAR, "col5" VARCHAR, …… CONSTRAINT ROWKEY PRIMARY KEY ("col1", "

[jira] [Assigned] (PHOENIX-6044) Precommit script over-zealous zombie check may clobber parallel Phoenix test

[ https://issues.apache.org/jira/browse/PHOENIX-6044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth reassigned PHOENIX-6044: Assignee: Istvan Toth > Precommit script over-zealous zombie check may clobber parallel

[jira] [Resolved] (PHOENIX-6023) Wrong result when issuing query for an immutable table with multiple column families

[ https://issues.apache.org/jira/browse/PHOENIX-6023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved PHOENIX-6023. -- Resolution: Fixed Committed addendum to master. > Wrong result when issuing query for an imm