[jira] [Updated] (PHOENIX-2525) Views on transactional tables return no rows

[ https://issues.apache.org/jira/browse/PHOENIX-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-2525: Attachment: PHOENIX-2525-v3.patch [~jamestaylor] I added a call to connection.removeTable

[jira] [Commented] (PHOENIX-2475) Date arithmetic broken for time and timestamp

[ https://issues.apache.org/jira/browse/PHOENIX-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069224#comment-15069224 ] ramkrishna.s.vasudevan commented on PHOENIX-2475: - Just to add on.. Once

Re: Re: Re: Why do we need an empty column when doing upsert?

Yes, thanks, Gabriel - very well thought out answer and another good candidate to add to our FAQs if anyone is up for it. On Tue, Dec 22, 2015 at 12:39 AM, William wrote: > Hi Gabriel, > > > Thanks a lot for your reply. > I was confused. I misunderstood 'not null' constraint as 'required at each

[jira] [Commented] (PHOENIX-2475) Date arithmetic broken for time and timestamp

[ https://issues.apache.org/jira/browse/PHOENIX-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069214#comment-15069214 ] ramkrishna.s.vasudevan commented on PHOENIX-2475: - With the above select

[jira] [Resolved] (PHOENIX-2539) Add FAQ entry on pooling phoenix connection pooling

[ https://issues.apache.org/jira/browse/PHOENIX-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-2539. --- Resolution: Fixed Thanks, [~elserj]. I pushed this out (with a minor tweak to point to the J

[jira] [Updated] (PHOENIX-2388) Support pooling Phoenix connections

[ https://issues.apache.org/jira/browse/PHOENIX-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2388: -- Description: Frequently user are plugging Phoenix into an ecosystem that pools connections. It

Re: master vs. 4.x-HBase-1.1

Thanks for the update, Ram. Would you mind following up with INFRA to get a more definitive answer? On Tuesday, December 22, 2015, Vasudevan, Ramkrishna S < ramkrishna.s.vasude...@intel.com> wrote: > They have closed INFRA-10920 and pointed me to > https://issues.apache.org/jira/browse/INFRA-1080

RE: master vs. 4.x-HBase-1.1

They have closed INFRA-10920 and pointed me to https://issues.apache.org/jira/browse/INFRA-10800. But there also there is no conclusion on it and I think the ETA for deleting a branch is not yet finalized. I am not aware of the background as why it was stopped. Regards Ram From: James Taylor

[jira] [Commented] (PHOENIX-2314) Cannot prepare parameterized statement with a 'like' predicate

[ https://issues.apache.org/jira/browse/PHOENIX-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069130#comment-15069130 ] Josh Elser commented on PHOENIX-2314: - Also, the schema for your {{emp}} table would

[jira] [Commented] (PHOENIX-2314) Cannot prepare parameterized statement with a 'like' predicate

[ https://issues.apache.org/jira/browse/PHOENIX-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069129#comment-15069129 ] Josh Elser commented on PHOENIX-2314: - Hi [~kliew], Any chance you could try this o

[jira] [Resolved] (PHOENIX-2505) Unexpected error caused by GROUP BY

[ https://issues.apache.org/jira/browse/PHOENIX-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-2505. --- Resolution: Cannot Reproduce > Unexpected error caused by GROUP BY > ---

[jira] [Comment Edited] (PHOENIX-2143) Use guidepost bytes instead of region name in stats primary key

[ https://issues.apache.org/jira/browse/PHOENIX-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069032#comment-15069032 ] James Taylor edited comment on PHOENIX-2143 at 12/23/15 2:09 AM: -

[jira] [Comment Edited] (PHOENIX-2143) Use guidepost bytes instead of region name in stats primary key

[ https://issues.apache.org/jira/browse/PHOENIX-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069032#comment-15069032 ] James Taylor edited comment on PHOENIX-2143 at 12/23/15 2:07 AM: -

[jira] [Comment Edited] (PHOENIX-2143) Use guidepost bytes instead of region name in stats primary key

[ https://issues.apache.org/jira/browse/PHOENIX-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069032#comment-15069032 ] James Taylor edited comment on PHOENIX-2143 at 12/23/15 2:08 AM: -

[jira] [Commented] (PHOENIX-2143) Use guidepost bytes instead of region name in stats primary key

[ https://issues.apache.org/jira/browse/PHOENIX-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069032#comment-15069032 ] James Taylor commented on PHOENIX-2143: --- Thanks for the WIP patch, [~ankit.singhal

[jira] [Commented] (PHOENIX-2505) Unexpected error caused by GROUP BY

[ https://issues.apache.org/jira/browse/PHOENIX-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069026#comment-15069026 ] Jelena commented on PHOENIX-2505: - Actually I just noticed that I have been using Phoeni

[jira] [Commented] (PHOENIX-2505) Unexpected error caused by GROUP BY

[ https://issues.apache.org/jira/browse/PHOENIX-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069012#comment-15069012 ] Jelena commented on PHOENIX-2505: - I mistakenly thought that the previous message meant

[jira] [Commented] (PHOENIX-2528) Pherf JVM doesn't exit due to un-closed ThreadPool

[ https://issues.apache.org/jira/browse/PHOENIX-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068957#comment-15068957 ] Hudson commented on PHOENIX-2528: - FAILURE: Integrated in Phoenix-master #1034 (See [ht

[jira] [Commented] (PHOENIX-2525) Views on transactional tables return no rows

[ https://issues.apache.org/jira/browse/PHOENIX-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068947#comment-15068947 ] James Taylor commented on PHOENIX-2525: --- Running UPDATE STATISTICS shouldn't be im

[jira] [Commented] (PHOENIX-2505) Unexpected error caused by GROUP BY

[ https://issues.apache.org/jira/browse/PHOENIX-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068938#comment-15068938 ] James Taylor commented on PHOENIX-2505: --- Any updates, [~jelenaf]? Should we close

[jira] [Issue Comment Deleted] (PHOENIX-2430) Improve statistics collection

[ https://issues.apache.org/jira/browse/PHOENIX-2430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-2430: -- Comment: was deleted (was: SUCCESS: Integrated in Phoenix-master #1032 (See [https://builds.a

[jira] [Commented] (PHOENIX-2492) Expose PhoenixRecordWritable outside of spark

[ https://issues.apache.org/jira/browse/PHOENIX-2492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068857#comment-15068857 ] Hudson commented on PHOENIX-2492: - SUCCESS: Integrated in Phoenix-master #1033 (See [ht

[jira] [Commented] (PHOENIX-2525) Views on transactional tables return no rows

[ https://issues.apache.org/jira/browse/PHOENIX-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068832#comment-15068832 ] Thomas D'Silva commented on PHOENIX-2525: - The tests fail without those two chan

[jira] [Commented] (PHOENIX-2525) Views on transactional tables return no rows

[ https://issues.apache.org/jira/browse/PHOENIX-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068812#comment-15068812 ] James Taylor commented on PHOENIX-2525: --- Good idea, [~tdsilva]. Looks like you lef

[jira] [Resolved] (PHOENIX-1340) Prevent collecting stats on the same region multiple times in same call

[ https://issues.apache.org/jira/browse/PHOENIX-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain resolved PHOENIX-1340. --- Resolution: Fixed This is no longer needed as we now have a stats tracker of sorts to make s

[jira] [Resolved] (PHOENIX-1261) Update stats table asynchronously

[ https://issues.apache.org/jira/browse/PHOENIX-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain resolved PHOENIX-1261. --- Resolution: Fixed > Update stats table asynchronously > - >

[jira] [Updated] (PHOENIX-1261) Update stats table asynchronously

[ https://issues.apache.org/jira/browse/PHOENIX-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-1261: -- Attachment: PHOENIX-1261_1.0.patch Patch for 1.0 branch. Just realized that I used the wrong J

[jira] [Updated] (PHOENIX-2525) Views on transactional tables return no rows

[ https://issues.apache.org/jira/browse/PHOENIX-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-2525: Attachment: PHOENIX-2525-v2.patch [~jamestaylor] I used a delegate table to wrap the tabl

[jira] [Resolved] (PHOENIX-1901) Performance test transaction implementation for immutable data

[ https://issues.apache.org/jira/browse/PHOENIX-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-1901. --- Resolution: Fixed > Performance test transaction implementation for immutable data > ---

[jira] [Created] (PHOENIX-2544) Consolidate implementations of PhoenixRecordWritable

Nick Dimiduk created PHOENIX-2544: - Summary: Consolidate implementations of PhoenixRecordWritable Key: PHOENIX-2544 URL: https://issues.apache.org/jira/browse/PHOENIX-2544 Project: Phoenix Is

[jira] [Resolved] (PHOENIX-2492) Expose PhoenixRecordWritable outside of spark

[ https://issues.apache.org/jira/browse/PHOENIX-2492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk resolved PHOENIX-2492. --- Resolution: Fixed Pushed to master, 4.x-1.0 and 4.x-0.98. > Expose PhoenixRecordWritable ou

[jira] [Commented] (PHOENIX-2430) Improve statistics collection

[ https://issues.apache.org/jira/browse/PHOENIX-2430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068765#comment-15068765 ] Hudson commented on PHOENIX-2430: - SUCCESS: Integrated in Phoenix-master #1032 (See [ht

Re: master vs. 4.x-HBase-1.1

Yes, that was pushed in error. INFRA-10920 was filed to remove it, but now it's closed with a link to another JIRA that links more JIRAs - it's unclear what the resolution is. Ram - would you mind following up on that? Thanks, James On Tue, Dec 22, 2015 at 1:12 PM, Nick Dimiduk wrote: > Heya,

master vs. 4.x-HBase-1.1

Heya, I see we now have a branch 4.x-HBase-1.1. It's pom version is 4.5.0-HBase-1.1-SNAPSHOT. Was this pushed in error? -n

[jira] [Updated] (PHOENIX-1261) Update stats table asynchronously

[ https://issues.apache.org/jira/browse/PHOENIX-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-1261: -- Attachment: PHOENIX-1261_98_v2.patch Patch for 4.x-0.98 branch. > Update stats table asynchro

[jira] [Created] (PHOENIX-2543) Modify StatsCollectorIT to test transactional test cases

Thomas D'Silva created PHOENIX-2543: --- Summary: Modify StatsCollectorIT to test transactional test cases Key: PHOENIX-2543 URL: https://issues.apache.org/jira/browse/PHOENIX-2543 Project: Phoenix

[jira] [Commented] (PHOENIX-1901) Performance test transaction implementation for immutable data

[ https://issues.apache.org/jira/browse/PHOENIX-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068713#comment-15068713 ] Mujtaba Chohan commented on PHOENIX-1901: - h4. Write Performance on the write si

[jira] [Assigned] (PHOENIX-1340) Prevent collecting stats on the same region multiple times in same call

[ https://issues.apache.org/jira/browse/PHOENIX-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain reassigned PHOENIX-1340: - Assignee: Samarth Jain > Prevent collecting stats on the same region multiple times in

[jira] [Commented] (PHOENIX-1261) Update stats table asynchronously

[ https://issues.apache.org/jira/browse/PHOENIX-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068651#comment-15068651 ] James Taylor commented on PHOENIX-1261: --- +1. Looks great, [~samarthjain]. > Updat

[jira] [Updated] (PHOENIX-2417) Compress memory used by row key byte[] of guideposts

[ https://issues.apache.org/jira/browse/PHOENIX-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2417: -- Attachment: PHOENIX-2417_encoder.diff Here's an encoder and decoder class without Parquet depe

[jira] [Updated] (PHOENIX-1261) Update stats table asynchronously

[ https://issues.apache.org/jira/browse/PHOENIX-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-1261: -- Attachment: PHOENIX-1261_master_v2.patch Patch for master branch. Added tests to verify that t

[jira] [Commented] (PHOENIX-2417) Compress memory used by row key byte[] of guideposts

[ https://issues.apache.org/jira/browse/PHOENIX-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068442#comment-15068442 ] James Taylor commented on PHOENIX-2417: --- With PHOENIX-2143, the compression would

[jira] [Commented] (PHOENIX-2525) Views on transactional tables return no rows

[ https://issues.apache.org/jira/browse/PHOENIX-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068431#comment-15068431 ] James Taylor commented on PHOENIX-2525: --- Looking at this closer, the root issue is

[jira] [Commented] (PHOENIX-2417) Compress memory used by row key byte[] of guideposts

[ https://issues.apache.org/jira/browse/PHOENIX-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068428#comment-15068428 ] Ankit Singhal commented on PHOENIX-2417: [~jamestaylor],is the compression sugge

[jira] [Updated] (PHOENIX-2525) Views on transactional tables return no rows

[ https://issues.apache.org/jira/browse/PHOENIX-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-2525: Attachment: PHOENIX-2525.patch > Views on transactional tables return no rows > --

[jira] [Updated] (PHOENIX-2525) Views on transactional tables return no rows

[ https://issues.apache.org/jira/browse/PHOENIX-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-2525: Attachment: (was: PHOENIX-2525.patch) > Views on transactional tables return no rows >

[jira] [Commented] (PHOENIX-2478) Rows committed in transaction overlapping index creation are not populated

[ https://issues.apache.org/jira/browse/PHOENIX-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15067784#comment-15067784 ] Poorna Chandra commented on PHOENIX-2478: - [~jamestaylor] Here is the Tephra JIR

Re:Re: Re: Why do we need an empty column when doing upsert?

Hi Gabriel, Thanks a lot for your reply. I was confused. I misunderstood 'not null' constraint as 'required at each upsert'. -William At 2015-12-22 15:25:40, "Gabriel Reid" wrote: >Hi William, > >Yes, all your tests there look correct, and it looks like you've got a >good understanding on