[jira] [Commented] (PHOENIX-116) Phoenix array integer types overlap with existing java.sql.Types

[ https://issues.apache.org/jira/browse/PHOENIX-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923647#comment-13923647 ] ramkrishna.s.vasudevan commented on PHOENIX-116: [~giacomotay...@gmail.co

[jira] [Updated] (PHOENIX-116) Phoenix array integer types overlap with existing java.sql.Types

[ https://issues.apache.org/jira/browse/PHOENIX-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated PHOENIX-116: --- Attachment: PHOENIX-116_1.patch Same patch, ensured that it applies on the l

Re: branching plan and cutting a 3.0 RC

+1 HBase could conceivably make changes in 0.98 that would cause a 3.0 (0.96) and a 4.0 (0.98) branch to diverge a bit. That's an outside chance - something to be avoided on the HBase side - but it seems reasonable to future proof against that possibility. > On Mar 7, 2014, at 9:39 AM, Enis S

[jira] [Commented] (PHOENIX-116) Phoenix array integer types overlap with existing java.sql.Types

[ https://issues.apache.org/jira/browse/PHOENIX-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923547#comment-13923547 ] ramkrishna.s.vasudevan commented on PHOENIX-116: Sure.. Let me check this

[jira] [Updated] (PHOENIX-116) Phoenix array integer types overlap with existing java.sql.Types

[ https://issues.apache.org/jira/browse/PHOENIX-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-116: - Fix Version/s: 3.0.0 > Phoenix array integer types overlap with existing java.sql.Types > --

[jira] [Commented] (PHOENIX-116) Phoenix array integer types overlap with existing java.sql.Types

[ https://issues.apache.org/jira/browse/PHOENIX-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923471#comment-13923471 ] James Taylor commented on PHOENIX-116: -- +1. Good catch, [~gabriel.reid], thanks. [~r

[jira] [Assigned] (PHOENIX-116) Phoenix array integer types overlap with existing java.sql.Types

[ https://issues.apache.org/jira/browse/PHOENIX-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor reassigned PHOENIX-116: Assignee: ramkrishna.s.vasudevan > Phoenix array integer types overlap with existing java.

[jira] [Commented] (PHOENIX-119) Removed unnecessary Expression.getByteSize() method

[ https://issues.apache.org/jira/browse/PHOENIX-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923462#comment-13923462 ] Hudson commented on PHOENIX-119: FAILURE: Integrated in Apache Phoenix - Branch:master #1

Re: branching plan and cutting a 3.0 RC

+1 on Jeffrey's plan. We probably want to have feature parity between 3.0 and 4.0, that is why it makes sense to have 3 active branches, rather than have only master as 4.0. This way we can ensure that all features in 3.x will be there in 4.x, the only difference will be about the supported HBase

[jira] [Commented] (PHOENIX-118) Type mismatch error on upsert for unsigned_date and date

[ https://issues.apache.org/jira/browse/PHOENIX-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923358#comment-13923358 ] Mujtaba Chohan commented on PHOENIX-118: Narrowed it down, making a unsigned_date

[jira] [Updated] (PHOENIX-119) Removed unnecessary Expression.getByteSize() method

[ https://issues.apache.org/jira/browse/PHOENIX-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-119: - Attachment: expr-cleanup.patch > Removed unnecessary Expression.getByteSize() method > -

[jira] [Created] (PHOENIX-119) Removed unnecessary Expression.getByteSize() method

James Taylor created PHOENIX-119: Summary: Removed unnecessary Expression.getByteSize() method Key: PHOENIX-119 URL: https://issues.apache.org/jira/browse/PHOENIX-119 Project: Phoenix Issue T

Re: branching plan and cutting a 3.0 RC

+1 Could we do the following? 1) Merge all the changes from master till the point we branch off 3.0 into 4.0 branch 2) Merge 4.0 branch back to Master 3) Bump up Master branch version to 4.1.0 4) Developers need check in new features into master branch always and fixes to all three branches simi

[jira] [Commented] (PHOENIX-118) Type mismatch error on upsert for unsigned_date and date

[ https://issues.apache.org/jira/browse/PHOENIX-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923327#comment-13923327 ] James Taylor commented on PHOENIX-118: -- I'm having a hard time reproducing this. Her

[jira] [Commented] (PHOENIX-111) Improve intra-region parallelization

[ https://issues.apache.org/jira/browse/PHOENIX-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923311#comment-13923311 ] Lars Hofhansl commented on PHOENIX-111: --- #1 is totally a must, should be simple #2

Re: branching plan and cutting a 3.0 RC

+1 --- Jesse Yates @jesse_yates jyates.github.com On Thu, Mar 6, 2014 at 3:43 PM, James Taylor wrote: > Hey All, > I'd like to branch master to 3.0 so that 4.0 can become the master branch. > There are a couple of outstanding changes that I'd like to complete today, > but if th

branching plan and cutting a 3.0 RC

Hey All, I'd like to branch master to 3.0 so that 4.0 can become the master branch. There are a couple of outstanding changes that I'd like to complete today, but if there are no objections, I'd like to cut this branch tonight. After this point and after Jeffrey catches 4.0 up to 3.0, developers wi

[jira] [Commented] (PHOENIX-63) Can't add null value to a secondary indexed table

[ https://issues.apache.org/jira/browse/PHOENIX-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923261#comment-13923261 ] Hudson commented on PHOENIX-63: --- SUCCESS: Integrated in Apache Phoenix - Branch:master #115

[jira] [Commented] (PHOENIX-117) Creating a sequence with CACHE LONG.MAX_VALUE fails

[ https://issues.apache.org/jira/browse/PHOENIX-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923228#comment-13923228 ] James Taylor commented on PHOENIX-117: -- Actually, I'll make the change - thanks for

[jira] [Commented] (PHOENIX-117) Creating a sequence with CACHE LONG.MAX_VALUE fails

[ https://issues.apache.org/jira/browse/PHOENIX-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923214#comment-13923214 ] James Taylor commented on PHOENIX-117: -- Please send a patch. Thanks! > Creating a s

[jira] [Commented] (PHOENIX-76) Fix perf regression due to PHOENIX-29

[ https://issues.apache.org/jira/browse/PHOENIX-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923211#comment-13923211 ] Lars Hofhansl commented on PHOENIX-76: -- Also checkout this comment: https://issues.ap

[jira] [Created] (PHOENIX-118) Type mismatch error on upsert for unsigned_date and date

Mujtaba Chohan created PHOENIX-118: -- Summary: Type mismatch error on upsert for unsigned_date and date Key: PHOENIX-118 URL: https://issues.apache.org/jira/browse/PHOENIX-118 Project: Phoenix

[jira] [Commented] (PHOENIX-99) Automatic white list based upgrade from 2.2 to 3.0

[ https://issues.apache.org/jira/browse/PHOENIX-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923156#comment-13923156 ] Mujtaba Chohan commented on PHOENIX-99: --- Created https://issues.apache.org/jira/brow

[jira] [Commented] (PHOENIX-117) Creating a sequence with CACHE LONG.MAX_VALUE fails

[ https://issues.apache.org/jira/browse/PHOENIX-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923137#comment-13923137 ] Samarth Jain commented on PHOENIX-117: -- I used that in a JDBC statement. conn.creat

[jira] [Reopened] (PHOENIX-117) Creating a sequence with CACHE LONG.MAX_VALUE fails

[ https://issues.apache.org/jira/browse/PHOENIX-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain reopened PHOENIX-117: -- > Creating a sequence with CACHE LONG.MAX_VALUE fails > --

[jira] [Commented] (PHOENIX-99) Automatic white list based upgrade from 2.2 to 3.0

[ https://issues.apache.org/jira/browse/PHOENIX-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923131#comment-13923131 ] James Taylor commented on PHOENIX-99: - Good find. That's a bug. That should still work

[jira] [Resolved] (PHOENIX-117) Creating a sequence with CACHE LONG.MAX_VALUE fails

[ https://issues.apache.org/jira/browse/PHOENIX-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-117. -- Resolution: Not A Problem You can't use LONG.MAX_VALUE in SQL. It needs to be a number. Try 9

[jira] [Commented] (PHOENIX-99) Automatic white list based upgrade from 2.2 to 3.0

[ https://issues.apache.org/jira/browse/PHOENIX-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923126#comment-13923126 ] Mujtaba Chohan commented on PHOENIX-99: --- upsert into TEST values (TO_DATE('2013-01-0

[jira] [Commented] (PHOENIX-99) Automatic white list based upgrade from 2.2 to 3.0

[ https://issues.apache.org/jira/browse/PHOENIX-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923105#comment-13923105 ] James Taylor commented on PHOENIX-99: - Can you post the upsert statement, please? > A

[jira] [Commented] (PHOENIX-99) Automatic white list based upgrade from 2.2 to 3.0

[ https://issues.apache.org/jira/browse/PHOENIX-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923078#comment-13923078 ] Mujtaba Chohan commented on PHOENIX-99: --- Running the same upsert statement which was

[jira] [Commented] (PHOENIX-99) Automatic white list based upgrade from 2.2 to 3.0

[ https://issues.apache.org/jira/browse/PHOENIX-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923068#comment-13923068 ] James Taylor commented on PHOENIX-99: - No, because we never allowed a negative timesta

[jira] [Updated] (PHOENIX-117) Creating a sequence with CACHE LONG.MAX_VALUE fails

[ https://issues.apache.org/jira/browse/PHOENIX-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-117: - Description: Statement: CREATE SEQUENCE ABC CACHE LONG.MAX_VALUE fails with the stacktrace: {co

[jira] [Updated] (PHOENIX-117) Creating a sequence with CACHE LONG.MAX_VALUE fails

[ https://issues.apache.org/jira/browse/PHOENIX-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-117: - Description: Statement: CREATE SEQUENCE ABC CACHE LONG.MAX_VALUE fails with the stacktrace: {co

[jira] [Created] (PHOENIX-117) Creating a sequence with CACHE LONG.MAX_VALUE fails

Samarth Jain created PHOENIX-117: Summary: Creating a sequence with CACHE LONG.MAX_VALUE fails Key: PHOENIX-117 URL: https://issues.apache.org/jira/browse/PHOENIX-117 Project: Phoenix Issue T

[jira] [Commented] (PHOENIX-99) Automatic white list based upgrade from 2.2 to 3.0

[ https://issues.apache.org/jira/browse/PHOENIX-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923045#comment-13923045 ] Mujtaba Chohan commented on PHOENIX-99: --- For whitelisted table, wouldn't type change

[jira] [Resolved] (PHOENIX-49) ArrayIndexOutOfBoundsException when creating index

[ https://issues.apache.org/jira/browse/PHOENIX-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue resolved PHOENIX-49. Resolution: Fixed > ArrayIndexOutOfBoundsException when creating index > --

[jira] [Commented] (PHOENIX-99) Automatic white list based upgrade from 2.2 to 3.0

[ https://issues.apache.org/jira/browse/PHOENIX-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13922753#comment-13922753 ] James Taylor commented on PHOENIX-99: - For (2), just add a DEFAULT_COLUMN_FAMILY='_0'

[jira] [Updated] (PHOENIX-116) Phoenix array integer types overlap with existing java.sql.Types

[ https://issues.apache.org/jira/browse/PHOENIX-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabriel Reid updated PHOENIX-116: - Attachment: PHOENIX-116.patch Patch to use a custom base value (3000) for the type constant for

[jira] [Commented] (PHOENIX-99) Automatic white list based upgrade from 2.2 to 3.0

[ https://issues.apache.org/jira/browse/PHOENIX-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13922679#comment-13922679 ] Mujtaba Chohan commented on PHOENIX-99: --- 1. All salesforce.* coprocessors are now re

[jira] [Created] (PHOENIX-116) Phoenix array integer types overlap with existing java.sql.Types

Gabriel Reid created PHOENIX-116: Summary: Phoenix array integer types overlap with existing java.sql.Types Key: PHOENIX-116 URL: https://issues.apache.org/jira/browse/PHOENIX-116 Project: Phoenix

[jira] [Commented] (PHOENIX-115) IN clause doesn't return the matching rows in the order they were given in the clause

[ https://issues.apache.org/jira/browse/PHOENIX-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13922207#comment-13922207 ] James Taylor commented on PHOENIX-115: -- The rows are not supposed to be returned in

[jira] [Resolved] (PHOENIX-115) IN clause doesn't return the matching rows in the order they were given in the clause

[ https://issues.apache.org/jira/browse/PHOENIX-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-115. -- Resolution: Not A Problem > IN clause doesn't return the matching rows in the order they were

[jira] [Updated] (PHOENIX-115) IN clause doesn't return the matching rows in the order they were given in the clause

[ https://issues.apache.org/jira/browse/PHOENIX-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth updated PHOENIX-115: Description: Consider the following query: SELECT * FROM TEST_TABLE WHERE TEST_ID IN ('9FIxxoT',

[jira] [Created] (PHOENIX-115) IN clause doesn't return the matching rows in the order they were given in the clause

Samarth created PHOENIX-115: --- Summary: IN clause doesn't return the matching rows in the order they were given in the clause Key: PHOENIX-115 URL: https://issues.apache.org/jira/browse/PHOENIX-115 Project:

[jira] [Commented] (PHOENIX-113) Enable usage of ClientKeyValue on for indexing on server

[ https://issues.apache.org/jira/browse/PHOENIX-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13922153#comment-13922153 ] Hudson commented on PHOENIX-113: FAILURE: Integrated in Apache Phoenix - Branch:master #1

[jira] [Commented] (PHOENIX-114) Add Hints so that user can select whether to use "avoid seek optimization" or not

[ https://issues.apache.org/jira/browse/PHOENIX-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13922154#comment-13922154 ] Hudson commented on PHOENIX-114: FAILURE: Integrated in Apache Phoenix - Branch:master #1