[jira] [Updated] (PHOENIX-4900) Modify MAX_MUTATION_SIZE_EXCEEDED and MAX_MUTATION_SIZE_BYTES_EXCEEDED exception message to recommend turning autocommit on for deletes

[ https://issues.apache.org/jira/browse/PHOENIX-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-4900: Fix Version/s: 5.0.1 > Modify MAX_MUTATION_SIZE_EXCEEDED and MAX_MUTATION_SIZE_BYTES_EXCEEDED >

[jira] [Updated] (PHOENIX-5069) Use asynchronous refresh to provide non-blocking Phoenix Stats Client Cache

[ https://issues.apache.org/jira/browse/PHOENIX-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5069: Fix Version/s: 5.0.1 > Use asynchronous refresh to provide non-blocking Phoenix Stats Client Cache >

[jira] [Updated] (PHOENIX-5131) Make spilling to disk for order/group by configurable

[ https://issues.apache.org/jira/browse/PHOENIX-5131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5131: Fix Version/s: 5.0.1 > Make spilling to disk for order/group by configurable >

[jira] [Updated] (PHOENIX-4907) IndexScrutinyTool should use empty catalog instead of null

[ https://issues.apache.org/jira/browse/PHOENIX-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-4907: Fix Version/s: 5.0.1 > IndexScrutinyTool should use empty catalog instead of null >

[jira] [Updated] (PHOENIX-5048) Index Rebuilder does not handle INDEX_STATE timestamp check for all index

[ https://issues.apache.org/jira/browse/PHOENIX-5048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5048: Fix Version/s: 5.0.1 > Index Rebuilder does not handle INDEX_STATE timestamp check for all index >

[jira] [Updated] (PHOENIX-5122) PHOENIX-4322 breaks client backward compatibility

[ https://issues.apache.org/jira/browse/PHOENIX-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5122: Fix Version/s: 5.0.1 > PHOENIX-4322 breaks client backward compatibility >

[jira] [Updated] (PHOENIX-5101) ScanningResultIterator getScanMetrics throws NPE

[ https://issues.apache.org/jira/browse/PHOENIX-5101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5101: Fix Version/s: 5.0.1 > ScanningResultIterator getScanMetrics throws NPE >

[jira] [Updated] (PHOENIX-5213) Phoenix-client improvements: add more relocations, exclude log binding, add source jar

[ https://issues.apache.org/jira/browse/PHOENIX-5213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5213: Fix Version/s: 5.0.1 > Phoenix-client improvements: add more relocations, exclude log binding, add >

[jira] [Updated] (PHOENIX-5126) RegionScanner leak leading to store files not getting cleared

[ https://issues.apache.org/jira/browse/PHOENIX-5126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5126: Fix Version/s: 5.0.1 > RegionScanner leak leading to store files not getting cleared >

[jira] [Updated] (PHOENIX-5207) Create index if not exists fails incorrectly if table has 'maxIndexesPerTable' indexes already

[ https://issues.apache.org/jira/browse/PHOENIX-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5207: Fix Version/s: 5.0.1 > Create index if not exists fails incorrectly if table has > 'maxIndexesPerTable'

[jira] [Updated] (PHOENIX-5184) HBase and Phoenix connection leaks in Indexing code path, OrphanViewTool and PhoenixConfigurationUtil

[ https://issues.apache.org/jira/browse/PHOENIX-5184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5184: Fix Version/s: 5.0.1 > HBase and Phoenix connection leaks in Indexing code path, OrphanViewTool and >

[jira] [Updated] (PHOENIX-5217) Incorrect result for COUNT DISTINCT limit

[ https://issues.apache.org/jira/browse/PHOENIX-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5217: Fix Version/s: 5.0.1 > Incorrect result for COUNT DISTINCT limit >

[jira] [Updated] (PHOENIX-5169) Query logger is still initialized for each query when the log level is off

[ https://issues.apache.org/jira/browse/PHOENIX-5169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5169: Fix Version/s: 5.0.1 > Query logger is still initialized for each query when the log level is off >

[jira] [Updated] (PHOENIX-5094) Index can transition from INACTIVE to ACTIVE via Phoenix Client

[ https://issues.apache.org/jira/browse/PHOENIX-5094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5094: Fix Version/s: 5.0.1 > Index can transition from INACTIVE to ACTIVE via Phoenix Client >

[jira] [Updated] (PHOENIX-5188) IndexedKeyValue should populate KeyValue fields

[ https://issues.apache.org/jira/browse/PHOENIX-5188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5188: Fix Version/s: 5.0.1 > IndexedKeyValue should populate KeyValue fields >

[jira] [Updated] (PHOENIX-5018) Index mutations created by UPSERT SELECT will have wrong timestamps

[ https://issues.apache.org/jira/browse/PHOENIX-5018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5018: Fix Version/s: 5.0.1 > Index mutations created by UPSERT SELECT will have wrong timestamps >

[jira] [Updated] (PHOENIX-5226) The format of VIEW_MODIFIED_PROPERTY_BYTES is incorrect as a tag of the cell

[ https://issues.apache.org/jira/browse/PHOENIX-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5226: Fix Version/s: 5.0.1 > The format of VIEW_MODIFIED_PROPERTY_BYTES is incorrect as a tag of the cell >

[jira] [Updated] (PHOENIX-5055) Split mutations batches probably affects correctness of index data

[ https://issues.apache.org/jira/browse/PHOENIX-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5055: Fix Version/s: 5.0.1 > Split mutations batches probably affects correctness of index data >

[jira] [Updated] (PHOENIX-5138) ViewIndexId sequences created after PHOENIX-5132 shouldn't collide with ones created before it

[ https://issues.apache.org/jira/browse/PHOENIX-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5138: Fix Version/s: 5.0.1 > ViewIndexId sequences created after PHOENIX-5132 shouldn't collide with ones >

[jira] [Updated] (PHOENIX-4759) During restart RS that hosts SYSTEM.CATALOG table may get stuck

[ https://issues.apache.org/jira/browse/PHOENIX-4759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-4759: Fix Version/s: 5.0.1 > During restart RS that hosts SYSTEM.CATALOG table may get stuck >

[jira] [Updated] (PHOENIX-5266) Client can only write on Index Table and skip data table if failure happens because of region split/move etc

[ https://issues.apache.org/jira/browse/PHOENIX-5266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5266: Fix Version/s: 5.0.1 > Client can only write on Index Table and skip data table if failure happens >

[jira] [Updated] (PHOENIX-5132) View indexes with different owners but of the same base table can be assigned same ViewIndexId

[ https://issues.apache.org/jira/browse/PHOENIX-5132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5132: Fix Version/s: 5.0.1 > View indexes with different owners but of the same base table can be assigned >

[jira] [Resolved] (PHOENIX-5113) Reason through the correct plans for salted tables and local indexes

[ https://issues.apache.org/jira/browse/PHOENIX-5113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl resolved PHOENIX-5113. Resolution: Invalid > Reason through the correct plans for salted tables and local

[jira] [Updated] (PHOENIX-5112) Simplify QueryPlan selection in Phoenix.

[ https://issues.apache.org/jira/browse/PHOENIX-5112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5112: --- Attachment: 5112-master.txt > Simplify QueryPlan selection in Phoenix. >

[jira] [Updated] (PHOENIX-5112) Simplify QueryPlan selection in Phoenix.

[ https://issues.apache.org/jira/browse/PHOENIX-5112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5112: --- Attachment: (was: 5112-master.txt) > Simplify QueryPlan selection in Phoenix. >

[jira] [Updated] (PHOENIX-5112) Simplify QueryPlan selection in Phoenix.

[ https://issues.apache.org/jira/browse/PHOENIX-5112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5112: --- Attachment: (was: 5112-master.txt) > Simplify QueryPlan selection in Phoenix. >

[jira] [Assigned] (PHOENIX-5225) Update Omid to 1.0.1

[ https://issues.apache.org/jira/browse/PHOENIX-5225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl reassigned PHOENIX-5225: -- Assignee: Lars Hofhansl > Update Omid to 1.0.1 > > >

[jira] [Resolved] (PHOENIX-5255) Create Orchestrator for PQS using PhoenixCanaryTool in phoenix-queryserver project

[ https://issues.apache.org/jira/browse/PHOENIX-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swaroopa Kadam resolved PHOENIX-5255. - Resolution: Resolved Merged in phoenix-queryserver git repo.  > Create Orchestrator

[jira] [Created] (PHOENIX-5288) Add ITs to phoenix-queryserver repo for new canary-orchestrator

Swaroopa Kadam created PHOENIX-5288: --- Summary: Add ITs to phoenix-queryserver repo for new canary-orchestrator Key: PHOENIX-5288 URL: https://issues.apache.org/jira/browse/PHOENIX-5288 Project:

Re: Handling of HBase version specifics.

+1, I think this is a good idea. This would make it easier to contribute and commit since you would only have to create a single patch. The tests would take longer to run (1.3, 1.4, 1.5 and 2.x). We should make sure our precommit build will run the tests for all the modules. On Fri, May 17,

[VOTE] Release of Apache Phoenix 4.14.2 RC1

Hello Everyone, This is a call for a vote on Apache Phoenix 4.14.2 RC1. This is a patch release of Phoenix 4.14 and is compatible with Apache HBase 1.3 and 1.4. The release includes both a source-only release and a convenience binary release for each supported HBase version. This release has