Re: Are we embracing Java 8?

Yes, what I was trying to say is even if you don't adopt 8 language features and specify a source level of 7 when compiling the binaries, there will be other runtime issues. And so sure there's no reason to hold back on source level changes. The runtime compatibility story will change

Re: Are we embracing Java 8?

Hi! Actually, the convenience binaries would be the least of a (hypothetical) Java7 user's problem. The whole point of moving 4.x to Java8 would be to enable the usage of Java8 features in the project, so almost immediately the 4.x branch wouldn't even compile on 4.x . I would imagine that any

Re: Are we embracing Java 8?

Just to be super clear: > Compile the code with Java 8, then if someone tries to install the resulting binaries into a HBase convenience binary release 1.x, which will have been compiled with Java 7, the regionserver will abort. ... if the code is running on Java 7. I don't know if anyone is

Re: Are we embracing Java 8?

The main problem you will face is the convenience binaries. If you are planning to move to Java 8, for 4.x branches, then you will no longer be able to make binary convenience releases compatible with any HBase 1.x convenience binary, even if you don't adopt any Java 8 language features. Compile

[jira] [Created] (PHOENIX-5864) RuleGeneratorTest unit test seem to be failing

Sandeep Guggilam created PHOENIX-5864: - Summary: RuleGeneratorTest unit test seem to be failing Key: PHOENIX-5864 URL: https://issues.apache.org/jira/browse/PHOENIX-5864 Project: Phoenix

[jira] [Created] (PHOENIX-5863) Upsert into view against a table with index throws exception when 4.14.3 client connects to 4.16 server

Sandeep Guggilam created PHOENIX-5863: - Summary: Upsert into view against a table with index throws exception when 4.14.3 client connects to 4.16 server Key: PHOENIX-5863 URL:

[jira] [Updated] (PHOENIX-5833) Incorrect results with RVCs and AND operator

[ https://issues.apache.org/jira/browse/PHOENIX-5833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Wong updated PHOENIX-5833: - Attachment: PHOENIX-5833.4.x.patch > Incorrect results with RVCs and AND operator >

[jira] [Updated] (PHOENIX-5833) Incorrect results with RVCs and AND operator

[ https://issues.apache.org/jira/browse/PHOENIX-5833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Wong updated PHOENIX-5833: - Attachment: 0001-PHOENIX-5833-Fix-Incorrect-results-with-RVCs-and-AND.patch > Incorrect

[jira] [Updated] (PHOENIX-5833) Incorrect results with RVCs and AND operator

[ https://issues.apache.org/jira/browse/PHOENIX-5833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Wong updated PHOENIX-5833: - Attachment: (was: 0001-PHOENIX-5833-Fix-Incorrect-results-with-RVCs-and-AND.patch) >

[jira] [Assigned] (PHOENIX-5833) Incorrect results with RVCs and AND operator

[ https://issues.apache.org/jira/browse/PHOENIX-5833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Wong reassigned PHOENIX-5833: Assignee: Daniel Wong > Incorrect results with RVCs and AND operator >

[jira] [Updated] (PHOENIX-5833) Incorrect results with RVCs and AND operator

[ https://issues.apache.org/jira/browse/PHOENIX-5833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Wong updated PHOENIX-5833: - Summary: Incorrect results with RVCs and AND operator (was: Incorrect results with LIKE

[jira] [Updated] (PHOENIX-5841) When data columns get TTLed, we need inline index validation to publish a metric for this

[ https://issues.apache.org/jira/browse/PHOENIX-5841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gokcen Iskender updated PHOENIX-5841: - Attachment: PHOENIX-5841.master.002.patch PHOENIX-5841.4.x.002.patch >

[jira] [Assigned] (PHOENIX-5842) Code Coverage tool for Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-5842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam reassigned PHOENIX-5842: - Assignee: Sandeep Guggilam > Code Coverage tool for Phoenix >

[jira] [Updated] (PHOENIX-5580) Wrong values seen when updating a view for a table that has an index

[ https://issues.apache.org/jira/browse/PHOENIX-5580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5580: -- Attachment: PHOENIX-5580.4.x.v2.patch > Wrong values seen when updating a view for a

[jira] [Updated] (PHOENIX-5496) Ensure that we handle all server-side mutation codes on the client[Create table]

[ https://issues.apache.org/jira/browse/PHOENIX-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Gupta updated PHOENIX-5496: Fix Version/s: (was: 5.1.1) (was: 4.15.1) > Ensure that we handle all

[jira] [Updated] (PHOENIX-5862) Ensure that we handle all server-side mutation codes on the client

[ https://issues.apache.org/jira/browse/PHOENIX-5862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Gupta updated PHOENIX-5862: Fix Version/s: 4.16.0 > Ensure that we handle all server-side mutation codes on the client >

[jira] [Updated] (PHOENIX-5496) Ensure that we handle all server-side mutation codes on the client[Create table]

[ https://issues.apache.org/jira/browse/PHOENIX-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-5496: -- Fix Version/s: 4.16.0 > Ensure that we handle all server-side mutation codes on the

[jira] [Updated] (PHOENIX-5496) Ensure that we handle all server-side mutation codes on the client[Create table]

[ https://issues.apache.org/jira/browse/PHOENIX-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Gupta updated PHOENIX-5496: Parent: PHOENIX-5862 Issue Type: Sub-task (was: Bug) > Ensure that we handle all

[jira] [Updated] (PHOENIX-5862) Ensure that we handle all server-side mutation codes on the client

[ https://issues.apache.org/jira/browse/PHOENIX-5862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Gupta updated PHOENIX-5862: Description: More details in  https://issues.apache.org/jira/browse/PHOENIX-5496 was:More

[jira] [Updated] (PHOENIX-5496) Ensure that we handle all server-side mutation codes on the client[Create table]

[ https://issues.apache.org/jira/browse/PHOENIX-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Gupta updated PHOENIX-5496: Summary: Ensure that we handle all server-side mutation codes on the client[Create table] (was:

[jira] [Created] (PHOENIX-5862) Ensure that we handle all server-side mutation codes on the client

Neha Gupta created PHOENIX-5862: --- Summary: Ensure that we handle all server-side mutation codes on the client Key: PHOENIX-5862 URL: https://issues.apache.org/jira/browse/PHOENIX-5862 Project: Phoenix

Re: No builds on Phoenix-Master jenkins since Feb 19th?

I've deleted all but the four Phoenix jobs listed in the JIRA.

[jira] [Resolved] (PHOENIX-5843) Remove unused Phoenix jobs from ASF Jenkins

[ https://issues.apache.org/jira/browse/PHOENIX-5843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved PHOENIX-5843. -- Resolution: Fixed Done. > Remove unused Phoenix jobs from ASF Jenkins >

[jira] [Updated] (PHOENIX-5861) Delete index data failed,due to pool closed

[ https://issues.apache.org/jira/browse/PHOENIX-5861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chao Wang updated PHOENIX-5861: --- Attachment: (was: PHOENIX-5861.4.13.x-HBASE.1.3.x.001.patch) > Delete index data failed,due to

[jira] [Updated] (PHOENIX-5861) Delete index data failed,due to pool closed

[ https://issues.apache.org/jira/browse/PHOENIX-5861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chao Wang updated PHOENIX-5861: --- Attachment: PHOENIX-5861.4.13.x-HBASE.1.3.x.001.patch > Delete index data failed,due to pool

[jira] [Updated] (PHOENIX-5861) Delete index data failed,due to pool closed

[ https://issues.apache.org/jira/browse/PHOENIX-5861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chao Wang updated PHOENIX-5861: --- Attachment: PHOENIX-5861.4.13.x-HBASE.1.3.x.001.patch > Delete index data failed,due to pool

[jira] [Created] (PHOENIX-5861) Delete index data failed,due to pool closed

Chao Wang created PHOENIX-5861: -- Summary: Delete index data failed,due to pool closed Key: PHOENIX-5861 URL: https://issues.apache.org/jira/browse/PHOENIX-5861 Project: Phoenix Issue Type: Bug

[jira] [Updated] (PHOENIX-5860) Throw exception which region is closing or splitting when delete data

[ https://issues.apache.org/jira/browse/PHOENIX-5860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chao Wang updated PHOENIX-5860: --- Attachment: PHOENIX-5860.4.13.x-HBASE.1.3.x.001.patch > Throw exception which region is closing or

[jira] [Updated] (PHOENIX-5860) Throw exception which region is closing or splitting when delete data

[ https://issues.apache.org/jira/browse/PHOENIX-5860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chao Wang updated PHOENIX-5860: --- Attachment: (was: PHOENIX.4.13.x-HBASE-1.3.x.001.patch) > Throw exception which region is