[jira] [Updated] (PHOENIX-4781) Phoenix client project's jar naming convention causes maven-deploy-plugin to fail

[Karan Mehta (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karan Mehta updated PHOENIX-4781:
-
Attachment: PHOENIX-4781.001.patch

> Phoenix client project's jar naming convention causes maven-deploy-plugin to 
> fail
> -
>
> Key: PHOENIX-4781
> URL: https://issues.apache.org/jira/browse/PHOENIX-4781
> Project: Phoenix
>  Issue Type: Improvement
>Reporter: Karan Mehta
>Priority: Major
> Attachments: PHOENIX-4781.001.patch
>
>
> `maven-deploy-plugin` is used for deploying built artifacts to repository 
> provided by `distributionManagement` tag. The name of files that need to be 
> uploaded are either derived from pom file of the project or it generates an 
> temporary one on its own.
> For `phoenix-client` project, we essentially create a shaded uber jar that 
> contains all dependencies and provide the project pom file for the plugin to 
> work. `maven-jar-plugin` is disabled for the project, hence the shade plugin 
> essentially packages the jar. The final name of the shaded jar is defined as 
> `phoenix-${project.version}-client`, which is different from how the standard 
> maven convention based on pom file (artifact and group id) is 
> `phoenix-client-${project.version}`
> This causes `maven-deploy-plugin` to fail since it is unable to find any 
> artifacts to be published.
> `maven-install-plugin` works correctly and hence it installs correct jar in 
> local repo.
> The same is effective for `phoenix-pig` project as well. However we require 
> the require jar for that project in the repo. I am not even sure why we 
> create shaded jar for that project.
> I will put up a 3 liner patch for the same.
> Any thoughts? [~sergey.soldatov] [~elserj]
> Files before change (first col is size):
> {code:java}
> 103487701 Jun 13 22:47 
> phoenix-4.14.0-HBase-1.3-sfdc-1.0.14-SNAPSHOT-client.jar{code}
> Files after change (first col is size):
> {code:java}
> 3640 Jun 13 21:23 
> original-phoenix-client-4.14.0-HBase-1.3-sfdc-1.0.14-SNAPSHOT.jar
> 103487702 Jun 13 21:24 
> phoenix-client-4.14.0-HBase-1.3-sfdc-1.0.14-SNAPSHOT.jar{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (PHOENIX-4781) Phoenix client project's jar naming convention causes maven-deploy-plugin to fail

[Karan Mehta (JIRA)]

Karan Mehta created PHOENIX-4781:


 Summary: Phoenix client project's jar naming convention causes 
maven-deploy-plugin to fail
 Key: PHOENIX-4781
 URL: https://issues.apache.org/jira/browse/PHOENIX-4781
 Project: Phoenix
  Issue Type: Improvement
Reporter: Karan Mehta


`maven-deploy-plugin` is used for deploying built artifacts to repository 
provided by `distributionManagement` tag. The name of files that need to be 
uploaded are either derived from pom file of the project or it generates an 
temporary one on its own.

For `phoenix-client` project, we essentially create a shaded uber jar that 
contains all dependencies and provide the project pom file for the plugin to 
work. `maven-jar-plugin` is disabled for the project, hence the shade plugin 
essentially packages the jar. The final name of the shaded jar is defined as 
`phoenix-${project.version}-client`, which is different from how the standard 
maven convention based on pom file (artifact and group id) is 
`phoenix-client-${project.version}`

This causes `maven-deploy-plugin` to fail since it is unable to find any 
artifacts to be published.

`maven-install-plugin` works correctly and hence it installs correct jar in 
local repo.

The same is effective for `phoenix-pig` project as well. However we require the 
require jar for that project in the repo. I am not even sure why we create 
shaded jar for that project.

I will put up a 3 liner patch for the same.

Any thoughts? [~sergey.soldatov] [~elserj]

Files before change (first col is size):
{code:java}
103487701 Jun 13 22:47 
phoenix-4.14.0-HBase-1.3-sfdc-1.0.14-SNAPSHOT-client.jar{code}
Files after change (first col is size):
{code:java}
3640 Jun 13 21:23 
original-phoenix-client-4.14.0-HBase-1.3-sfdc-1.0.14-SNAPSHOT.jar
103487702 Jun 13 21:24 
phoenix-client-4.14.0-HBase-1.3-sfdc-1.0.14-SNAPSHOT.jar{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (PHOENIX-3533) Remove IMMUTABLE_ROWS TableProperty

[Geoffrey Jacoby (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16511392#comment-16511392
 ] 

Geoffrey Jacoby commented on PHOENIX-3533:
--

The problem with doing this is that it potentially breaks any schema management 
our users are doing. For example, if an operator wants to spin up a second 
cluster, and does so using the exact DDL that created the first cluster, it 
would either fail, or create a mutable table, which isn't what the operator 
wants.

Any reason why the engine can't read IMMUTABLE_ROWS=true from the DDL and 
transparently rewrite the query to CREATE IMMUTABLE TABLE? 

At the very least, I'd think we'd want a clear deprecation path, similar to 
what HBase does where an API is publicly deprecated in one release and then 
removed in the following. 

Also, if CREATE IMMUTABLE TABLE exists (and isn't just a planned feature), the 
docs don't mention it.

> Remove IMMUTABLE_ROWS TableProperty
> ---
>
> Key: PHOENIX-3533
> URL: https://issues.apache.org/jira/browse/PHOENIX-3533
> Project: Phoenix
>  Issue Type: Task
>Reporter: Thomas D'Silva
>Priority: Major
> Fix For: 4.15.0
>
>
> Using CREATE IMMUTABLE TABLE ... should be the only way to specify a table is 
> immutable, and this property cannot be altered. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (PHOENIX-4195) PHOENIX-4195 Deleting view rows with extended PKs through the base table silently fails

[Geoffrey Jacoby (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16511254#comment-16511254
 ] 

Geoffrey Jacoby commented on PHOENIX-4195:
--

[~tdsilva] - OK, so how best to get the hasChildViews flag? Would this be part 
of the big SysCat rewrite in PHOENIX-3534, something that would come after, or 
something that could be done beforehand?

Also, if this is going to be done, I think PHOENIX-4779 becomes really 
important, because some use cases will want to forbid views from being created 
in order to preserve their ability to use mutations from global connections. 

> PHOENIX-4195 Deleting view rows with extended PKs through the base table 
> silently fails
> ---
>
> Key: PHOENIX-4195
> URL: https://issues.apache.org/jira/browse/PHOENIX-4195
> Project: Phoenix
>  Issue Type: Bug
>Reporter: Thomas D'Silva
>Assignee: Geoffrey Jacoby
>Priority: Major
> Attachments: test.diff
>
>
> The attached test fails.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[VOTE] Release of Apache Phoenix 5.0.0 RC0

[rajeshb...@apache.org]

Hello Everyone,

This is a call for a vote on Apache Phoenix 5.0.0 RC0. This is the next
major release
of Phoenix compatible with the 2.0 branch of Apache HBase(2.0.0+).  The
release
includes both a source-only release and a convenience binary release.

This release has feature parity with HBase 2.0.0 version.

Here is are few highlights of Phoenix 5.0.0 over Phoenix 4.14.0 recently
released.
1) Refactored coprocessor implementations as for the new coprocessor design
changes in HBase 2.0[1 
].
2) Replaced many deprecated classes/interfaces related to admin, table,
descriptor,  region,
regioninfo, connection, cell, scan and mapreduce with new ones[2
].
3) Hive and Spark integration works with latest versions of Hive(3.0.0) and
Spark respectively[3 ][4
].

The source tarball, including signatures, digests, etc can be found at:
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-5.0.0-HBase-2.0-rc0/src
The binary artifacts can be found at:
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-5.0.0-HBase-2.0-rc0/bin

Release artifacts are signed with the following key:
https://pgp.mit.edu/pks/lookup?op=get=0x318FD86BAAEDBD7B
https://dist.apache.org/repos/dist/dev/phoenix/KEYS

The hash and tag to be voted upon:
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v5.0.0-HBase-2.0-rc0
*https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=shortlog;h=refs/tags/v5.0.0-HBase-2.0-rc0
*


Vote will be open for at least 72 hours. Please vote:

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

[1] https://issues.apache.org/jira/browse/PHOENIX-4338
[2] https://issues.apache.org/jira/browse/PHOENIX-4297
[3] https://issues.apache.org/jira/browse/PHOENIX-4423
[4] https://issues.apache.org/jira/browse/PHOENIX-4527

Thanks,
The Apache Phoenix Team

[jira] [Commented] (PHOENIX-4610) Converge 4.x and 5.x branches

[Rajeshbabu Chintaguntla (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-4610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16510866#comment-16510866
 ] 

Rajeshbabu Chintaguntla commented on PHOENIX-4610:
--

5.x branch has all the commits other than PHOENIX-4528(has dependency of HBase) 
so just moved out of 5.0.0.

> Converge 4.x and 5.x branches
> -
>
> Key: PHOENIX-4610
> URL: https://issues.apache.org/jira/browse/PHOENIX-4610
> Project: Phoenix
>  Issue Type: Task
>Reporter: Josh Elser
>Assignee: Rajeshbabu Chintaguntla
>Priority: Major
> Fix For: 4.15.0
>
>
> We have a quite a few improvements which have landed on the 4.x branches 
> which have missed the 5.x branch due to its earlier instability. Rajeshbabu 
> volunteered offline to me to start this onerous task.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (PHOENIX-4750) Resolve server customizers and provide them to Avatica

[Rajeshbabu Chintaguntla (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rajeshbabu Chintaguntla updated PHOENIX-4750:
-
Fix Version/s: (was: 5.0.0)
   4.15.0

> Resolve server customizers and provide them to Avatica
> --
>
> Key: PHOENIX-4750
> URL: https://issues.apache.org/jira/browse/PHOENIX-4750
> Project: Phoenix
>  Issue Type: Improvement
>Reporter: Alex Araujo
>Assignee: Alex Araujo
>Priority: Major
> Fix For: 4.15.0
>
> Attachments: PHOENIX-4750.patch
>
>
> CALCITE-2284 allows finer grained customization of the underlying Avatica 
> HttpServer.
> Resolve server customizers on the PQS classpath and provide them to the 
> HttpServer builder.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (PHOENIX-4741) Shade disruptor dependency

[Rajeshbabu Chintaguntla (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rajeshbabu Chintaguntla updated PHOENIX-4741:
-
Fix Version/s: (was: 5.0.0)
   (was: 4.14.0)
   4.15.0

> Shade disruptor dependency 
> ---
>
> Key: PHOENIX-4741
> URL: https://issues.apache.org/jira/browse/PHOENIX-4741
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.14.0, 5.0.0
>Reporter: Jungtaek Lim
>Assignee: Ankit Singhal
>Priority: Major
> Fix For: 4.15.0
>
>
> We should shade disruptor dependency to avoid conflict with the versions used 
> by the other framework like storm , hive etc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (PHOENIX-3533) Remove IMMUTABLE_ROWS TableProperty

[Rajeshbabu Chintaguntla (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rajeshbabu Chintaguntla updated PHOENIX-3533:
-
Fix Version/s: (was: 5.0.0)
   4.15.0

> Remove IMMUTABLE_ROWS TableProperty
> ---
>
> Key: PHOENIX-3533
> URL: https://issues.apache.org/jira/browse/PHOENIX-3533
> Project: Phoenix
>  Issue Type: Task
>Reporter: Thomas D'Silva
>Priority: Major
> Fix For: 4.15.0
>
>
> Using CREATE IMMUTABLE TABLE ... should be the only way to specify a table is 
> immutable, and this property cannot be altered. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (PHOENIX-4610) Converge 4.x and 5.x branches

[Rajeshbabu Chintaguntla (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rajeshbabu Chintaguntla updated PHOENIX-4610:
-
Fix Version/s: 4.15.0

> Converge 4.x and 5.x branches
> -
>
> Key: PHOENIX-4610
> URL: https://issues.apache.org/jira/browse/PHOENIX-4610
> Project: Phoenix
>  Issue Type: Task
>Reporter: Josh Elser
>Assignee: Rajeshbabu Chintaguntla
>Priority: Major
> Fix For: 4.15.0
>
>
> We have a quite a few improvements which have landed on the 4.x branches 
> which have missed the 5.x branch due to its earlier instability. Rajeshbabu 
> volunteered offline to me to start this onerous task.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (PHOENIX-4200) QualifierFilter from HBase to be implemented

[Rajeshbabu Chintaguntla (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rajeshbabu Chintaguntla updated PHOENIX-4200:
-
Fix Version/s: (was: 5.0.0)
   4.15.0

> QualifierFilter from HBase to be implemented
> 
>
> Key: PHOENIX-4200
> URL: https://issues.apache.org/jira/browse/PHOENIX-4200
> Project: Phoenix
>  Issue Type: Improvement
>Affects Versions: 4.9.0, 4.10.0, 4.11.0
>Reporter: Priyansh Saxena
>Priority: Major
> Fix For: 4.15.0
>
>   Original Estimate: 672h
>  Remaining Estimate: 672h
>
> Currently, it is not possible to filter columns from a table using an 
> SQL-like query in Phoenix. This impairs the use of Phoenix as an SQL layer 
> over HBase where wide column-family approach is being used and/or the 
> column-names are dynamic.
> Need to determine how to handle and display dynamic column-names.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (PHOENIX-4565) IndexScrutinyToolIT is failing

[Rajeshbabu Chintaguntla (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rajeshbabu Chintaguntla updated PHOENIX-4565:
-
Fix Version/s: (was: 5.0.0)

> IndexScrutinyToolIT is failing
> --
>
> Key: PHOENIX-4565
> URL: https://issues.apache.org/jira/browse/PHOENIX-4565
> Project: Phoenix
>  Issue Type: Bug
>Reporter: Josh Elser
>Priority: Critical
> Attachments: PHOENIX-4565.2.patch, PHOENIX-4565.patch
>
>
> {noformat}
> [ERROR] 
> testScrutinyWhileTakingWrites[0](org.apache.phoenix.end2end.IndexScrutinyToolIT)
>   Time elapsed: 12.494 s  <<< FAILURE!
> java.lang.AssertionError: expected:<1000> but was:<996>
>     at 
> org.apache.phoenix.end2end.IndexScrutinyToolIT.testScrutinyWhileTakingWrites(IndexScrutinyToolIT.java:253)
> [ERROR] 
> testScrutinyWhileTakingWrites[1](org.apache.phoenix.end2end.IndexScrutinyToolIT)
>   Time elapsed: 7.437 s  <<< FAILURE!
> java.lang.AssertionError: expected:<1000> but was:<997>
>     at 
> org.apache.phoenix.end2end.IndexScrutinyToolIT.testScrutinyWhileTakingWrites(IndexScrutinyToolIT.java:253)
> [ERROR] 
> testScrutinyWhileTakingWrites[2](org.apache.phoenix.end2end.IndexScrutinyToolIT)
>   Time elapsed: 12.195 s  <<< FAILURE!
> java.lang.AssertionError: expected:<1000> but was:<999>
>     at 
> org.apache.phoenix.end2end.IndexScrutinyToolIT.testScrutinyWhileTakingWrites(IndexScrutinyToolIT.java:253)
> {noformat}
> Saw this on a {{mvn verify}} of 5.x. I don't know if we expect this one to be 
> broken or not -- I didn't see an open issue tracking it.
> Is this one we should get fixed before shipping an alpha/beta? My opinion 
> would be: unless it is a trivial/simple fix, we should get it for the next 
> release.
> [~sergey.soldatov], [~an...@apache.org], [~rajeshbabu].



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (PHOENIX-4610) Converge 4.x and 5.x branches

[Rajeshbabu Chintaguntla (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rajeshbabu Chintaguntla updated PHOENIX-4610:
-
Fix Version/s: (was: 5.0.0)

> Converge 4.x and 5.x branches
> -
>
> Key: PHOENIX-4610
> URL: https://issues.apache.org/jira/browse/PHOENIX-4610
> Project: Phoenix
>  Issue Type: Task
>Reporter: Josh Elser
>Assignee: Rajeshbabu Chintaguntla
>Priority: Major
>
> We have a quite a few improvements which have landed on the 4.x branches 
> which have missed the 5.x branch due to its earlier instability. Rajeshbabu 
> volunteered offline to me to start this onerous task.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (PHOENIX-4524) Remove Flume dependency from Phoenix-Kafka plugin

[Rajeshbabu Chintaguntla (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rajeshbabu Chintaguntla updated PHOENIX-4524:
-
Fix Version/s: (was: 5.0.0)

> Remove Flume dependency from Phoenix-Kafka plugin
> -
>
> Key: PHOENIX-4524
> URL: https://issues.apache.org/jira/browse/PHOENIX-4524
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.12.0
>Reporter: Artem Ervits
>Priority: Blocker
>
> Phoenix Kafka plugin heavily depends on Phoenix Flume Plugin which in turn 
> depends on Apache Flume. This jira is proposed to remove Flume dependency 
> from Phoenix-Kafka plugin.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (PHOENIX-4378) Unable to set KEEP_DELETED_CELLS to true on RS scanner

[Rajeshbabu Chintaguntla (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rajeshbabu Chintaguntla updated PHOENIX-4378:
-
Fix Version/s: (was: 5.0.0)

> Unable to set KEEP_DELETED_CELLS to true on RS scanner
> --
>
> Key: PHOENIX-4378
> URL: https://issues.apache.org/jira/browse/PHOENIX-4378
> Project: Phoenix
>  Issue Type: Bug
>Reporter: Ankit Singhal
>Assignee: Ankit Singhal
>Priority: Major
>  Labels: HBase-2.0
>
> [~jamestaylor], 
> It seems we may need to fix PHOENIX-4277 differently for HBase 2.0 as we can 
> only update TTL and maxVersions now in preStoreScannerOpen and cannot return 
> a new StoreScanner with updated scanInfo.
> for reference:
> [1]https://issues.apache.org/jira/browse/PHOENIX-4318?focusedCommentId=16249943=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16249943



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (PHOENIX-4396) Use setPriority method instead of relying on RpcController configuration

[Rajeshbabu Chintaguntla (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rajeshbabu Chintaguntla updated PHOENIX-4396:
-
Fix Version/s: (was: 5.0.0)

> Use setPriority method instead of relying on RpcController configuration
> 
>
> Key: PHOENIX-4396
> URL: https://issues.apache.org/jira/browse/PHOENIX-4396
> Project: Phoenix
>  Issue Type: Bug
>Reporter: Ankit Singhal
>Priority: Major
>  Labels: HBase-2.0
>
> use setPriority method(implemented as a part of HBASE-15816) for RPC calls.
> Related to PHOENIX-3994



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (PHOENIX-4482) Fix WALReplayWithIndexWritesAndCompressedWALIT failing with ClassCastException

[Rajeshbabu Chintaguntla (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rajeshbabu Chintaguntla updated PHOENIX-4482:
-
Fix Version/s: (was: 5.0.0)

> Fix WALReplayWithIndexWritesAndCompressedWALIT failing with ClassCastException
> --
>
> Key: PHOENIX-4482
> URL: https://issues.apache.org/jira/browse/PHOENIX-4482
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Rajeshbabu Chintaguntla
>Assignee: Rajeshbabu Chintaguntla
>Priority: Major
>  Labels: HBase-2.0
> Attachments: PHOENIX-4482.patch
>
>
> {noformat}
> ERROR] 
> testReplayEditsWrittenViaHRegion(org.apache.hadoop.hbase.regionserver.wal.WALReplayWithIndexWritesAndCompressedWALIT)
>   Time elapsed: 82.455 s  <<< ERROR!
> java.lang.ClassCastException: 
> org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL cannot be cast to 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog
> at 
> org.apache.hadoop.hbase.regionserver.wal.WALReplayWithIndexWritesAndCompressedWALIT.createWAL(WALReplayWithIndexWritesAndCompressedWALIT.java:274)
> at 
> org.apache.hadoop.hbase.regionserver.wal.WALReplayWithIndexWritesAndCompressedWALIT.testReplayEditsWrittenViaHRegion(WALReplayWithIndexWritesAndCompressedWALIT.java:192)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (PHOENIX-4535) Index in array data type is inconsistent.

[Rajeshbabu Chintaguntla (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rajeshbabu Chintaguntla updated PHOENIX-4535:
-
Fix Version/s: (was: 5.0.0)

> Index in array data type is inconsistent. 
> --
>
> Key: PHOENIX-4535
> URL: https://issues.apache.org/jira/browse/PHOENIX-4535
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.13.0, 5.0.0
>Reporter: Romil Choksi
>Priority: Major
>  Labels: HBase-2.0
>
> We allow using zero indexes for elements in array column and returns null by 
> accident. 
> A simple test case to reproduce:
> {noformat}
> Properties props = PropertiesUtil.deepCopy(TEST_PROPERTIES);
> Connection conn = DriverManager.getConnection(getUrl(), props);
> conn.createStatement().execute("create table A(ID INTEGER PRIMARY 
> KEY, array_id VARCHAR[])");
> conn.createStatement().execute("upsert into A values (1, 
> ARRAY['test','test2','test3'])");
> conn.commit();
> ResultSet rs = conn.createStatement().executeQuery("select 
> array_id[0], array_id[1] from A");
> while(rs.next()) {
> System.out.println(rs.getString(1));
> System.out.println(rs.getString(2));
> }
> {noformat}
> The result for 4.x branches would be {null, 'test'} and it would fail with an 
> exception for 5.x.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (PHOENIX-4470) Fix tests of type ParallelStatsDisabledTest

[Rajeshbabu Chintaguntla (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rajeshbabu Chintaguntla resolved PHOENIX-4470.
--
Resolution: Fixed

> Fix tests of type ParallelStatsDisabledTest 
> 
>
> Key: PHOENIX-4470
> URL: https://issues.apache.org/jira/browse/PHOENIX-4470
> Project: Phoenix
>  Issue Type: Bug
>Reporter: Ankit Singhal
>Assignee: Ankit Singhal
>Priority: Major
>  Labels: HBase-2.0
> Fix For: 5.0.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)