cutting over to Apache git repo

I received the last piece of paperwork I needed for us to move the code over to Apache. The one thing we don't have is our Github issues transfered over yet, but I don't think we have to wait for that - our JIRA is active, we just don't have our existing issues transfered over yet. Do you have out

[jira] [Created] (PHOENIX-7) after Connection close, there are still 10 phoenix threads alive

LiLi created PHOENIX-7: -- Summary: after Connection close, there are still 10 phoenix threads alive Key: PHOENIX-7 URL: https://issues.apache.org/jira/browse/PHOENIX-7 Project: Phoenix Issue Type: Bug

[jira] [Resolved] (PHOENIX-5) HRegion.put() on Phoenix table from within endpoint coprocessor fails with NPE

[ https://issues.apache.org/jira/browse/PHOENIX-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Dumon resolved PHOENIX-5. --- Resolution: Not A Problem The problem can be easily worked around by using the short-circuiting HTable

[jira] [Commented] (PHOENIX-5) HRegion.put() on Phoenix table from within endpoint coprocessor fails with NPE

[ https://issues.apache.org/jira/browse/PHOENIX-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876812#comment-13876812 ] Bruno Dumon commented on PHOENIX-5: --- I tried it with the HTable from CoprocessorEnvironme

[jira] [Commented] (PHOENIX-5) HRegion.put() on Phoenix table from within endpoint coprocessor fails with NPE

[ https://issues.apache.org/jira/browse/PHOENIX-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876669#comment-13876669 ] Jesse Yates commented on PHOENIX-5: --- If you know you are on the same server, can you just

[jira] [Created] (PHOENIX-6) Support on duplicate key ignore construct

James Taylor created PHOENIX-6: -- Summary: Support on duplicate key ignore construct Key: PHOENIX-6 URL: https://issues.apache.org/jira/browse/PHOENIX-6 Project: Phoenix Issue Type: New Feature