[jira] [Created] (PHOENIX-4734) SQL Query with an RVC expression lexographically higher than all values in an OR clause causes query to blow up

2018-05-10 Thread Jan Fernando (JIRA)
Jan Fernando created PHOENIX-4734: - Summary: SQL Query with an RVC expression lexographically higher than all values in an OR clause causes query to blow up Key: PHOENIX-4734 URL: https://issues.apache.org/jira

[jira] [Updated] (PHOENIX-4734) SQL Query with an RVC expression lexographically higher than all values in an OR clause causes query to blow up

2018-05-10 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Fernando updated PHOENIX-4734: -- Attachment: SqlInClauseIssueIT.java > SQL Query with an RVC expression lexographically hig

[jira] [Updated] (PHOENIX-4721) Issuing ALTER TABLE to add a PK Column to a table with secondary indexes fails

2018-04-30 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Fernando updated PHOENIX-4721: -- Attachment: AlterTableExtendPk.java > Issuing ALTER TABLE to add a PK Column to a table w

[jira] [Created] (PHOENIX-4721) Issuing ALTER TABLE to add a PK Column to a table with secondary indexes fails

2018-04-30 Thread Jan Fernando (JIRA)
Jan Fernando created PHOENIX-4721: - Summary: Issuing ALTER TABLE to add a PK Column to a table with secondary indexes fails Key: PHOENIX-4721 URL: https://issues.apache.org/jira/browse/PHOENIX-4721

[jira] [Commented] (PHOENIX-4292) Filters on Tables and Views with composite PK of VARCHAR fields with sort direction DESC do not work

2017-10-19 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16211704#comment-16211704 ] Jan Fernando commented on PHOENIX-4292: --- I think things have gotten los

[jira] [Commented] (PHOENIX-4292) Filters on Tables and Views with composite PK of VARCHAR fields with sort direction DESC do not work

2017-10-19 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16211636#comment-16211636 ] Jan Fernando commented on PHOENIX-4292: --- I'm not arguing with that [~apu

[jira] [Commented] (PHOENIX-4292) Filters on Tables and Views with composite PK of VARCHAR fields with sort direction DESC do not work

2017-10-19 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16211612#comment-16211612 ] Jan Fernando commented on PHOENIX-4292: --- I am not suggesting we test everyt

[jira] [Commented] (PHOENIX-4292) Filters on Tables and Views with composite PK of VARCHAR fields with sort direction DESC do not work

2017-10-19 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16211555#comment-16211555 ] Jan Fernando commented on PHOENIX-4292: --- I guess my 2 cents is I disagree

[jira] [Commented] (PHOENIX-4292) Filters on Tables and Views with composite PK of VARCHAR fields with sort direction DESC do not work

2017-10-19 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16211516#comment-16211516 ] Jan Fernando commented on PHOENIX-4292: --- Okay. I'm not a big fan

[jira] [Commented] (PHOENIX-4292) Filters on Tables and Views with composite PK of VARCHAR fields with sort direction DESC do not work

2017-10-19 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16211191#comment-16211191 ] Jan Fernando commented on PHOENIX-4292: --- [~tdsilva] Should we add more

[jira] [Created] (PHOENIX-4292) SOQL Filters on Tables and Filters with composite PK of VARCHAR fields with sort direction DESC does not work

2017-10-16 Thread Jan Fernando (JIRA)
Jan Fernando created PHOENIX-4292: - Summary: SOQL Filters on Tables and Filters with composite PK of VARCHAR fields with sort direction DESC does not work Key: PHOENIX-4292 URL: https://issues.apache.org/jira

[jira] [Updated] (PHOENIX-4292) SOQL Filters on Tables and Views with composite PK of VARCHAR fields with sort direction DESC do not work

2017-10-16 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Fernando updated PHOENIX-4292: -- Summary: SOQL Filters on Tables and Views with composite PK of VARCHAR fields with sort

[jira] [Updated] (PHOENIX-4292) SOQL Filters on Tables and Views with composite PK of VARCHAR fields with sort direction DESC does not work

2017-10-16 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Fernando updated PHOENIX-4292: -- Summary: SOQL Filters on Tables and Views with composite PK of VARCHAR fields with sort

[jira] [Assigned] (PHOENIX-4292) SOQL Filters on Tables and Filters with composite PK of VARCHAR fields with sort direction DESC does not work

2017-10-16 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-4292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Fernando reassigned PHOENIX-4292: - Assignee: Jan Fernando > SOQL Filters on Tables and Filters with composite PK

Re: Phoenix code quality

2017-09-25 Thread Jan Fernando
Lars, I think these are really awesome guidelines. As Phoenix reaches a new phase of maturity and operational complexity (which is really exciting and important for the project IMHO), I think these things are becoming even more important. Re #5, I agree we need to err on the side of stability. I

[jira] [Commented] (PHOENIX-3787) RVC For Paged Queries not working as expected when PK leads with column defined as 'DATE DESC'

2017-04-13 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15968476#comment-15968476 ] Jan Fernando commented on PHOENIX-3787: --- Best I can tell from other ad

[jira] [Commented] (PHOENIX-3787) RVC For Paged Queries not working as expected when PK leads with column defined as 'DATE DESC'

2017-04-13 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15968464#comment-15968464 ] Jan Fernando commented on PHOENIX-3787: --- This is also an issue with other

[jira] [Created] (PHOENIX-3787) RVC For Paged Queries not working as expected when PK leads with column defined as 'DATE DESC'

2017-04-13 Thread Jan Fernando (JIRA)
Jan Fernando created PHOENIX-3787: - Summary: RVC For Paged Queries not working as expected when PK leads with column defined as 'DATE DESC' Key: PHOENIX-3787 URL: https://issues.apache.org/jira/brow

[jira] [Commented] (PHOENIX-3725) Add support for per VIEW level TTLs in addition to table level TTLs

2017-03-08 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15901791#comment-15901791 ] Jan Fernando commented on PHOENIX-3725: --- [~giacomotaylor] This is an

[jira] [Created] (PHOENIX-3725) Add support for per VIEW level TTLs in addition to table level TTLs

2017-03-08 Thread Jan Fernando (JIRA)
Jan Fernando created PHOENIX-3725: - Summary: Add support for per VIEW level TTLs in addition to table level TTLs Key: PHOENIX-3725 URL: https://issues.apache.org/jira/browse/PHOENIX-3725 Project

Re: [ANNOUNCE] New Apache Phoenix committer - Geoffrey Jacoby

2017-02-28 Thread Jan Fernando
Congrats Geoffrey!! Great stuff! > On Feb 28, 2017, at 12:07 PM, James Taylor wrote: > > On behalf of the Apache Phoenix PMC, I'm pleased to announce that Geoffrey > Jacoby has accepted our invitation to become a committer on the Apache > Phoenix project. He's been involved with Phoenix for two y

[jira] [Updated] (PHOENIX-3516) Performance Issues with queries that have compound filters and specify phoenix.query.force.rowkeyorder=true

2016-12-02 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Fernando updated PHOENIX-3516: -- Description: On all our connections we specify the phoenix.query.force.rowkeyorder=true

[jira] [Commented] (PHOENIX-3516) Performance Issues with queries that have compound filters and specify phoenix.query.force.rowkeyorder=true

2016-12-02 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15717035#comment-15717035 ] Jan Fernando commented on PHOENIX-3516: --- One thing I forgot to mention is

[jira] [Created] (PHOENIX-3516) Performance Issues with queries that have compound filters and specify phoenix.query.force.rowkeyorder=true

2016-12-02 Thread Jan Fernando (JIRA)
Jan Fernando created PHOENIX-3516: - Summary: Performance Issues with queries that have compound filters and specify phoenix.query.force.rowkeyorder=true Key: PHOENIX-3516 URL: https://issues.apache.org/jira

[jira] [Commented] (PHOENIX-3439) Query using an RVC based on the base table PK is incorrectly using an index and doing a full scan instead of a point query

2016-11-05 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15640883#comment-15640883 ] Jan Fernando commented on PHOENIX-3439: --- [~giacomotaylor] Yes via a te

[jira] [Comment Edited] (PHOENIX-3439) Query using an RVC based on the base table PK is incorrectly using an index and doing a full scan instead of a point query

2016-11-05 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15640687#comment-15640687 ] Jan Fernando edited comment on PHOENIX-3439 at 11/5/16 10:2

[jira] [Reopened] (PHOENIX-3439) Query using an RVC based on the base table PK is incorrectly using an index and doing a full scan instead of a point query

2016-11-05 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Fernando reopened PHOENIX-3439: --- [~giacomotay...@gmail.com] [~samarthjain] I test this out with the Phoenix 4.9 jar and it

[jira] [Reopened] (PHOENIX-3421) Column name lookups fail when on an indexed table

2016-11-03 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Fernando reopened PHOENIX-3421: --- [~giacomotaylor] Unfortunately we discovered today that even with this fix we have a

[jira] [Created] (PHOENIX-3439) Query using an RVC based on the base table PK is incorrectly using an index and doing a full scan instead of a point query

2016-11-03 Thread Jan Fernando (JIRA)
Jan Fernando created PHOENIX-3439: - Summary: Query using an RVC based on the base table PK is incorrectly using an index and doing a full scan instead of a point query Key: PHOENIX-3439 URL: https

[jira] [Commented] (PHOENIX-3396) Valid Multi-byte strings whose total byte size is greater than the max char limit cannot be inserted into VARCHAR fields in the PK

2016-10-24 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15602805#comment-15602805 ] Jan Fernando commented on PHOENIX-3396: --- [~giacomotaylor] Was there a reason

[jira] [Comment Edited] (PHOENIX-3396) Valid Multi-byte strings whose total byte size is greater than the max char limit cannot be inserted into VARCHAR fields in the PK

2016-10-24 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15602805#comment-15602805 ] Jan Fernando edited comment on PHOENIX-3396 at 10/24/16 6:2

[jira] [Created] (PHOENIX-3396) Valid Multi-byte strings whose total byte size is greater than the max char limit cannot be inserted into VARCHAR fields in the PK

2016-10-21 Thread Jan Fernando (JIRA)
Jan Fernando created PHOENIX-3396: - Summary: Valid Multi-byte strings whose total byte size is greater than the max char limit cannot be inserted into VARCHAR fields in the PK Key: PHOENIX-3396 URL: https

[jira] [Commented] (PHOENIX-3121) Queries with filter and reverse scan failing when limit is a multiple of scanner cache size

2016-07-27 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396507#comment-15396507 ] Jan Fernando commented on PHOENIX-3121: --- [~lhofhansl] The issue we found was

Re: [DISCUSS] RM for next release

2016-07-07 Thread Jan Fernando
As a consumer of Phoenix, moving to where we have regular patch releases on a predicable cadence that contain bug fixes would be incredibly beneficial. For the most recent few releases we have only needed bug fixes and were not dependent on any of the new features. Therefore having to wait until a

Re: [VOTE] Release of Apache Phoenix 4.7.0-HBase-0.98 RC6

2016-03-07 Thread Jan Fernando
+1 Ran several internal Salesforce tests to validate the jar functionally. On Sun, Mar 6, 2016 at 8:07 PM, Mujtaba Chohan wrote: > +1. Verified performance and backward compatibility looks good as well. > > On Sunday, March 6, 2016, Samarth Jain wrote: > > > +1 > > > > On Sun, Mar 6, 2016 at 11

Re: [VOTE] Release of Apache Phoenix 4.7.0-HBase-0.98 RC1

2016-02-03 Thread Jan Fernando
+1 I ran several of our internal tests and they all pass. On Tue, Feb 2, 2016 at 3:47 PM, Mujtaba Chohan wrote: > +1 > > Verified performance is on par to prior release. > > On Tue, Feb 2, 2016 at 12:09 PM, Thomas D'Silva > wrote: > > > +1 Manually tested transactions. > > > > On Tue, Feb 2, 20

[jira] [Commented] (PHOENIX-2640) Make it possible to kill running queries (and ideally list them too)

2016-01-28 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15122465#comment-15122465 ] Jan Fernando commented on PHOENIX-2640: --- Absolutely agree the Phoenix commu

[jira] [Commented] (PHOENIX-2640) Make it possible to kill running queries (and ideally list them too)

2016-01-28 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15122360#comment-15122360 ] Jan Fernando commented on PHOENIX-2640: --- >From my perspective, the more

[jira] [Resolved] (PHOENIX-2367) Change PhoenixRecordWriter to use execute instead of executeBatch

2015-12-20 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Fernando resolved PHOENIX-2367. --- Resolution: Fixed I have committed the patch to master, 4.x-HBase-0.98, 4.x-HBase-1.0 and

[jira] [Commented] (PHOENIX-2367) Change PhoenixRecordWriter to use execute instead of executeBatch

2015-12-16 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15061327#comment-15061327 ] Jan Fernando commented on PHOENIX-2367: --- [~giacomotaylor]I can get to it

[jira] [Commented] (PHOENIX-2367) Change PhoenixRecordWriter to use execute instead of executeBatch

2015-12-15 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059329#comment-15059329 ] Jan Fernando commented on PHOENIX-2367: --- +1 Looks good to me. >

Re: [ANNOUNCE] Thomas D'Silva added to Apache Phoenix PMC

2015-11-23 Thread Jan Fernando
Congrats Thomas!! > On Nov 22, 2015, at 7:07 PM, Eli Levine wrote: > > Well done, Thomas. Congrats! > >> On Nov 22, 2015, at 4:37 PM, Andrew Purtell wrote: >> >> Congratulations Thomas. >> >>> On Nov 22, 2015, at 11:39 AM, Nick Dimiduk wrote: >>> >>> Congrats Thomas! >>> >>> On Sunday, Novemb

[jira] [Commented] (PHOENIX-2373) Change ReserveNSequence Udf to take in zookeeper and tentantId as param

2015-11-10 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14999208#comment-14999208 ] Jan Fernando commented on PHOENIX-2373: --- Thanks for the contribu

[jira] [Resolved] (PHOENIX-2373) Change ReserveNSequence Udf to take in zookeeper and tentantId as param

2015-11-10 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Fernando resolved PHOENIX-2373. --- Resolution: Fixed > Change ReserveNSequence Udf to take in zookeeper and tentantId as pa

[jira] [Commented] (PHOENIX-2373) Change ReserveNSequence Udf to take in zookeeper and tentantId as param

2015-11-09 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14997753#comment-14997753 ] Jan Fernando commented on PHOENIX-2373: --- [~jamestaylor] In terms of bran

[jira] [Commented] (PHOENIX-2373) Change ReserveNSequence Udf to take in zookeeper and tentantId as param

2015-11-09 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14997741#comment-14997741 ] Jan Fernando commented on PHOENIX-2373: --- [~giacomotaylor] If you are good on

[jira] [Commented] (PHOENIX-2373) Change ReserveNSequence Udf to take in zookeeper and tentantId as param

2015-11-09 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14997343#comment-14997343 ] Jan Fernando commented on PHOENIX-2373: --- + 1 changes look good to me! >

[jira] [Commented] (PHOENIX-2299) Support CURRENT_DATE() in Pherf data upserts

2015-11-05 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14992502#comment-14992502 ] Jan Fernando commented on PHOENIX-2299: --- [~cody.mar...@gmail.com] brings

[jira] [Commented] (PHOENIX-2367) Change PhoenixRecordWriter to use execute instead of executeBatch

2015-11-04 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14990976#comment-14990976 ] Jan Fernando commented on PHOENIX-2367: --- I don't believe there is any pe

Re: PhoenixHbaseStorage to Skip invalid rows

2015-11-03 Thread Jan Fernando
+1 on making this change. Can you file a JIRA for it? On Mon, Nov 2, 2015 at 4:31 PM, Siddhi Mehta wrote: > Hey All, > > I wanted to add a notion of skipping invalid rows for PhoenixHbaseStorage > similar to how the CSVBulkLoad tool has an option of ignoring the bad > rows.I did some work on the

Re: [VOTE] Release of Apache Phoenix 4.6.0-HBase-0.98 RC0

2015-10-22 Thread Jan Fernando
+1 Ran various internal regression tests for our use cases and everything looks good! On Wed, Oct 21, 2015 at 2:34 PM, Mujtaba Chohan wrote: > +1 for release. > > Also verified basic backward compatibility between v4.5.x and v4.6.0 in > addition to performance verification which is on par with p

[jira] [Updated] (PHOENIX-2310) PhoenixConfigurationUtil.getUpsertColumnMetadataList() in Phoenix Mapreduce integration generates incorrect upsert statement for view immediately after issue view DDL

2015-10-08 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Fernando updated PHOENIX-2310: -- Fix Version/s: 4.5.3 > PhoenixConfigurationUtil.getUpsertColumnMetadataList() in Phoe

[jira] [Resolved] (PHOENIX-2310) PhoenixConfigurationUtil.getUpsertColumnMetadataList() in Phoenix Mapreduce integration generates incorrect upsert statement for view immediately after issue view DDL

2015-10-08 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Fernando resolved PHOENIX-2310. --- Resolution: Fixed > PhoenixConfigurationUtil.getUpsertColumnMetadataList() in Phoe

[jira] [Commented] (PHOENIX-2310) PhoenixConfigurationUtil.getUpsertColumnMetadataList() in Phoenix Mapreduce integration generates incorrect upsert statement for view immediately after issue view DDL

2015-10-08 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14948999#comment-14948999 ] Jan Fernando commented on PHOENIX-2310: --- Committed to 4.5 and 4.x branche

[jira] [Updated] (PHOENIX-2310) PhoenixConfigurationUtil.getUpsertColumnMetadataList() in Phoenix Mapreduce integration generates incorrect upsert statement for view immediately after issue view DDL

2015-10-08 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Fernando updated PHOENIX-2310: -- Attachment: PHOENIX-2310-4.5.patch > PhoenixConfigurationUtil.getUpsertColumnMetadataL

[jira] [Commented] (PHOENIX-2310) PhoenixConfigurationUtil.getUpsertColumnMetadataList() in Phoenix Mapreduce integration generates incorrect upsert statement for view immediately after issue view DDL

2015-10-07 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947950#comment-14947950 ] Jan Fernando commented on PHOENIX-2310: --- Committed to master, but the patc

[jira] [Updated] (PHOENIX-2310) PhoenixConfigurationUtil.getUpsertColumnMetadataList() in Phoenix Mapreduce integration generates incorrect upsert statement for view immediately after issue view DDL

2015-10-07 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Fernando updated PHOENIX-2310: -- Attachment: PHOENIX-2310_v2.patch [~jamestaylor] I added the toString() method to

[jira] [Commented] (PHOENIX-2310) PhoenixConfigurationUtil.getUpsertColumnMetadataList() in Phoenix Mapreduce integration generates incorrect upsert statement for view immediately after issue view DDL

2015-10-05 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944513#comment-14944513 ] Jan Fernando commented on PHOENIX-2310: --- [~jamestaylor] One other thought, do

[jira] [Commented] (PHOENIX-2310) PhoenixConfigurationUtil.getUpsertColumnMetadataList() in Phoenix Mapreduce integration generates incorrect upsert statement for view immediately after issue view DDL

2015-10-05 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944510#comment-14944510 ] Jan Fernando commented on PHOENIX-2310: --- Here's a stack trace of when

[jira] [Commented] (PHOENIX-2310) PhoenixConfigurationUtil.getUpsertColumnMetadataList() in Phoenix Mapreduce integration generates incorrect upsert statement for view immediately after issue view DDL

2015-10-05 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944502#comment-14944502 ] Jan Fernando commented on PHOENIX-2310: --- [~jamestaylor] Can you take a loo

[jira] [Updated] (PHOENIX-2310) PhoenixConfigurationUtil.getUpsertColumnMetadataList() in Phoenix Mapreduce integration generates incorrect upsert statement for view immediately after issue view DDL

2015-10-05 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Fernando updated PHOENIX-2310: -- Attachment: PHOENIX-2310-v1.patch > PhoenixConfigurationUtil.getUpsertColumnMetadataList()

[jira] [Created] (PHOENIX-2310) PhoenixConfigurationUtil.getUpsertColumnMetadataList() in Phoenix Mapreduce integration generates incorrect upsert statement for view immediately after issue view DDL

2015-10-05 Thread Jan Fernando (JIRA)
Jan Fernando created PHOENIX-2310: - Summary: PhoenixConfigurationUtil.getUpsertColumnMetadataList() in Phoenix Mapreduce integration generates incorrect upsert statement for view immediately after issue view DDL Key: PHOENIX

[jira] [Resolved] (PHOENIX-2285) phoenix.query.timeoutMs doesn't allow callers to set the timeout to less than 1 second

2015-10-03 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Fernando resolved PHOENIX-2285. --- Resolution: Fixed Fix Version/s: 4.5.3 > phoenix.query.timeoutMs doesn'

[jira] [Commented] (PHOENIX-2285) phoenix.query.timeoutMs doesn't allow callers to set the timeout to less than 1 second

2015-10-02 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14941724#comment-14941724 ] Jan Fernando commented on PHOENIX-2285: --- [~jamestaylor] I committed the patc

[jira] [Commented] (PHOENIX-2285) phoenix.query.timeoutMs doesn't allow callers to set the timeout to less than 1 second

2015-10-01 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14940685#comment-14940685 ] Jan Fernando commented on PHOENIX-2285: --- I'll get the repo setup and ta

Re: [ANNOUNCE] New Apache Phoenix committer - Jan Fernando

2015-09-29 Thread Jan Fernando
Sep 29, 2015 at 11:23 AM, Eli Levine >>> wrote: >>> >>> > On behalf of the Apache Phoenix project I am happy to welcome Jan >>> Fernando >>> > as a committer. Jan has been an active user and contributor to Phoenix >>> in >>> >

[jira] [Comment Edited] (PHOENIX-2285) phoenix.query.timeoutMs doesn't allow callers to set the timeout to less than 1 second

2015-09-28 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933522#comment-14933522 ] Jan Fernando edited comment on PHOENIX-2285 at 9/28/15 4:2

[jira] [Commented] (PHOENIX-2285) phoenix.query.timeoutMs doesn't allow callers to set the timeout to less than 1 second

2015-09-28 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933522#comment-14933522 ] Jan Fernando commented on PHOENIX-2285: --- [~jamestaylor] I uploaded a second

[jira] [Updated] (PHOENIX-2285) phoenix.query.timeoutMs doesn't allow callers to set the timeout to less than 1 second

2015-09-28 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Fernando updated PHOENIX-2285: -- Attachment: PHOENIX-2285-v2.txt > phoenix.query.timeoutMs doesn't allow callers to

[jira] [Commented] (PHOENIX-2285) phoenix.query.timeoutMs doesn't allow callers to set the timeout to less than 1 second

2015-09-24 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14907067#comment-14907067 ] Jan Fernando commented on PHOENIX-2285: --- [~jamestaylor] I've attached a

[jira] [Updated] (PHOENIX-2285) phoenix.query.timeoutMs doesn't allow callers to set the timeout to less than 1 second

2015-09-24 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Fernando updated PHOENIX-2285: -- Attachment: PHOENIX-2285-v1.txt > phoenix.query.timeoutMs doesn't allow callers to

[jira] [Assigned] (PHOENIX-2285) phoenix.query.timeoutMs doesn't allow callers to set the timeout to less than 1 second

2015-09-24 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Fernando reassigned PHOENIX-2285: - Assignee: Jan Fernando > phoenix.query.timeoutMs doesn't allow callers to

[jira] [Created] (PHOENIX-2285) phoenix.query.timeoutMs doesn't allow callers to set the timeout to less than 1 second

2015-09-22 Thread Jan Fernando (JIRA)
Jan Fernando created PHOENIX-2285: - Summary: phoenix.query.timeoutMs doesn't allow callers to set the timeout to less than 1 second Key: PHOENIX-2285 URL: https://issues.apache.org/jira/browse/PHOENIX

Re: [VOTE] Release of Apache Phoenix 4.5.2-HBase-0.98 RC1

2015-09-12 Thread Jan Fernando
+1 I ran a couple of our Pherf scenarios and some other internal tools that validate our query patterns. Looks good! On Fri, Sep 11, 2015 at 4:35 PM, James Taylor wrote: > Hi Everyone, > > This is a call for a vote on Apache Phoenix 4.5.2-HBase-0.98 RC1. This is a > patch release of Phoenix 4,

Re: cut RC for 4.5.2 tomorrow

2015-09-09 Thread Jan Fernando
Not sure whether this qualifies for 4.5.2 or not - I submitted a small fix for the Pherf module (PHOENIX-2227) to allow me to create a representative Pherf scenario to validate the performance of queries that whose performance were fixed by PHOENIX-2194. On Tue, Sep 8, 2015 at 5:43 PM, James Tayl

[jira] [Created] (PHOENIX-2235) [Pherf] Allow users to specify a postfix as well as a prefix for CHAR data types and allow sequence placement to be configurable

2015-09-04 Thread Jan Fernando (JIRA)
Jan Fernando created PHOENIX-2235: - Summary: [Pherf] Allow users to specify a postfix as well as a prefix for CHAR data types and allow sequence placement to be configurable Key: PHOENIX-2235 URL: https

[jira] [Created] (PHOENIX-2234) [Pherf] Add attribute to dataSequence column attribute to support encoding sequence in different formats e.g. base62

2015-09-04 Thread Jan Fernando (JIRA)
Jan Fernando created PHOENIX-2234: - Summary: [Pherf] Add attribute to dataSequence column attribute to support encoding sequence in different formats e.g. base62 Key: PHOENIX-2234 URL: https://issues.apache.org

[jira] [Updated] (PHOENIX-2227) [Pherf] Add ability to execute a DDL statement at the scenario level before any workloads are run

2015-09-04 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Fernando updated PHOENIX-2227: -- Attachment: PHOENIX-2227-v2.patch Uploaded second version of patch adding the comments we

[jira] [Updated] (PHOENIX-2227) [Pherf] Add ability to execute a DDL statement at the scenario level before any workloads are run

2015-09-03 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Fernando updated PHOENIX-2227: -- Attachment: PHOENIX-2227.patch [~cody.mar...@gmail.com] Here's a possible patch for w

[jira] [Created] (PHOENIX-2227) [Pherf] Add ability to execute a DDL statement at the scenario level before any workloads are run

2015-09-03 Thread Jan Fernando (JIRA)
Jan Fernando created PHOENIX-2227: - Summary: [Pherf] Add ability to execute a DDL statement at the scenario level before any workloads are run Key: PHOENIX-2227 URL: https://issues.apache.org/jira/browse/PHOENIX

[jira] [Updated] (PHOENIX-2194) order by should not require all PK fields with = constraint

2015-09-02 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Fernando updated PHOENIX-2194: -- Attachment: PHOENIX-2194-tests2.patch Added another set of tests, this patch supersedes the

[jira] [Comment Edited] (PHOENIX-2194) order by should not require all PK fields with = constraint

2015-09-02 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14728087#comment-14728087 ] Jan Fernando edited comment on PHOENIX-2194 at 9/2/15 9:4

[jira] [Updated] (PHOENIX-2194) order by should not require all PK fields with = constraint

2015-09-02 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Fernando updated PHOENIX-2194: -- Attachment: PHOENIX-2194-tests.patch Attaching some addition IT tests that repro the issues

[jira] [Commented] (PHOENIX-2154) Failure of one mapper should not affect other mappers in MR index build

2015-08-11 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14682234#comment-14682234 ] Jan Fernando commented on PHOENIX-2154: --- +1 to [~elilevine]'s

[jira] [Commented] (PHOENIX-1791) Pherf - Support data creation to multi-tenant views

2015-08-10 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14680325#comment-14680325 ] Jan Fernando commented on PHOENIX-1791: --- [~cody.mar...@gmail.com] Is this

[jira] [Updated] (PHOENIX-1791) Pherf - Support data creation to multi-tenant views

2015-08-06 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Fernando updated PHOENIX-1791: -- Attachment: PHOENIX-1791.patch > Pherf - Support data creation to multi-tenant vi

[jira] [Commented] (PHOENIX-1791) Pherf - Support data creation to multi-tenant views

2015-08-06 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14660849#comment-14660849 ] Jan Fernando commented on PHOENIX-1791: --- [~cody.mar...@gmail.com] I've

[jira] [Commented] (PHOENIX-2149) MAX Value of Sequences not honored when closing Connection between calls to NEXT VALUE FOR

2015-07-27 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14643518#comment-14643518 ] Jan Fernando commented on PHOENIX-2149: --- [~tdsilva] Thanks. Quick questio

Re: [VOTE] Release of Apache Phoenix 4.5.0-HBase-0.98 RC0

2015-07-26 Thread Jan Fernando
+1 Ran various internal regression test suites and no issues found. On Wed, Jul 22, 2015 at 5:28 PM, James Taylor wrote: > Hi Everyone, > > This is a call for a vote on Apache Phoenix 4.5.0-HBase-0.98 RC0. This is > the > next minor release of Phoenix 4, compatible with the 0.98 branch of > Apac

[jira] [Updated] (PHOENIX-2149) MAX Value of Sequences not honored when closing Connection between calls to NEXT VALUE FOR

2015-07-26 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Fernando updated PHOENIX-2149: -- Attachment: PHOENIX-2149.patch [~jamestaylor] Here is a patch file with the fix. I think the

[jira] [Assigned] (PHOENIX-2149) MAX Value of Sequences not honored when closing Connection between calls to NEXT VALUE FOR

2015-07-26 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Fernando reassigned PHOENIX-2149: - Assignee: Jan Fernando (was: Thomas D'Silva) > MAX Value of Sequences not

[jira] [Commented] (PHOENIX-2149) MAX Value of Sequences not honored when closing Connection between calls to NEXT VALUE FOR

2015-07-26 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14641996#comment-14641996 ] Jan Fernando commented on PHOENIX-2149: --- I think the bug is caused by the fac

[jira] [Created] (PHOENIX-2149) MAX Value of Sequences not honored when closing Connection between calls to NEXT VALUE FOR

2015-07-25 Thread Jan Fernando (JIRA)
Jan Fernando created PHOENIX-2149: - Summary: MAX Value of Sequences not honored when closing Connection between calls to NEXT VALUE FOR Key: PHOENIX-2149 URL: https://issues.apache.org/jira/browse/PHOENIX-2149

[jira] [Updated] (PHOENIX-1954) Reserve chunks of numbers for a sequence

2015-07-09 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Fernando updated PHOENIX-1954: -- Attachment: PHOENIX-1954-4.x-HBase-0.98.patch Attaching patch for 4.x-HBase-0.98 branch

[jira] [Updated] (PHOENIX-1954) Reserve chunks of numbers for a sequence

2015-07-09 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Fernando updated PHOENIX-1954: -- Attachment: PHOENIX-1954-wip7-rebase.patch [~jamestaylor] Attached rebased patch that

[jira] [Commented] (PHOENIX-1954) Reserve chunks of numbers for a sequence

2015-07-09 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14621645#comment-14621645 ] Jan Fernando commented on PHOENIX-1954: --- [~jamestaylor] #1 Let me loo

[jira] [Updated] (PHOENIX-1954) Reserve chunks of numbers for a sequence

2015-07-09 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Fernando updated PHOENIX-1954: -- Attachment: PHOENIX-1954-wip6.patch [~jamestaylor] Following from our discussions attached is

[jira] [Comment Edited] (PHOENIX-1954) Reserve chunks of numbers for a sequence

2015-07-09 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14621116#comment-14621116 ] Jan Fernando edited comment on PHOENIX-1954 at 7/9/15 7:2

[jira] [Commented] (PHOENIX-1954) Reserve chunks of numbers for a sequence

2015-07-09 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14621116#comment-14621116 ] Jan Fernando commented on PHOENIX-1954: --- [~jamestaylor] Re (1) This is tur

[jira] [Updated] (PHOENIX-1954) Reserve chunks of numbers for a sequence

2015-07-08 Thread Jan Fernando (JIRA)
[ https://issues.apache.org/jira/browse/PHOENIX-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Fernando updated PHOENIX-1954: -- Attachment: PHOENIX-1954-wip5-rebased.patch [~jamestaylor] Following on from our discussion I

  1   2   >