date:20210504

[jira] [Updated] (PHOENIX-6453) Possible ArrayIndexOutOfBoundsException while preparing scan start key with multiple key range queries

2021-05-04 Thread Rajeshbabu Chintaguntla (Jira)



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

Rajeshbabu Chintaguntla updated PHOENIX-6453:
-
Priority: Blocker  (was: Major)

> Possible ArrayIndexOutOfBoundsException while preparing scan start key with 
> multiple key range queries
> --
>
> Key: PHOENIX-6453
> URL: https://issues.apache.org/jira/browse/PHOENIX-6453
> Project: Phoenix
>  Issue Type: Bug
>Reporter: Rajeshbabu Chintaguntla
>Assignee: Rajeshbabu Chintaguntla
>Priority: Blocker
> Fix For: 4.17.0, 5.1.2
>
>
> There is possible AIOOE when there are multiple key range conditions on 
> columns in a query.
> {noformat}
> java.lang.ArrayIndexOutOfBoundsException: 25
>   at org.apache.phoenix.util.ScanUtil.setKey(ScanUtil.java:474)
>   at org.apache.phoenix.util.ScanUtil.setKey(ScanUtil.java:408)
>   at org.apache.phoenix.util.ScanUtil.getKey(ScanUtil.java:380)
>   at org.apache.phoenix.util.ScanUtil.getMinKey(ScanUtil.java:353)
>   at org.apache.phoenix.compile.ScanRanges.create(ScanRanges.java:134)
>   at 
> org.apache.phoenix.compile.WhereOptimizer.pushKeyExpressionsToScan(WhereOptimizer.java:355)
>   at 
> org.apache.phoenix.compile.WhereCompiler.compile(WhereCompiler.java:171)
>   at 
> org.apache.phoenix.compile.WhereCompiler.compile(WhereCompiler.java:118)
>   at 
> org.apache.phoenix.compile.QueryCompiler.compileSingleFlatQuery(QueryCompiler.java:747)
>   at 
> org.apache.phoenix.compile.QueryCompiler.compileSingleQuery(QueryCompiler.java:674)
>   at 
> org.apache.phoenix.compile.QueryCompiler.compileSelect(QueryCompiler.java:251)
>   at 
> org.apache.phoenix.compile.QueryCompiler.compile(QueryCompiler.java:178)
>   at 
> org.apache.phoenix.jdbc.PhoenixStatement$ExecutableSelectStatement.compilePlan(PhoenixStatement.java:501)
>   at 
> org.apache.phoenix.jdbc.PhoenixStatement$ExecutableSelectStatement.compilePlan(PhoenixStatement.java:464)
>   at 
> org.apache.phoenix.jdbc.PhoenixStatement$1.call(PhoenixStatement.java:306)
>   at 
> org.apache.phoenix.jdbc.PhoenixStatement$1.call(PhoenixStatement.java:295)
>   at org.apache.phoenix.call.CallRunner.run(CallRunner.java:53)
>   at 
> org.apache.phoenix.jdbc.PhoenixStatement.executeQuery(PhoenixStatement.java:294)
>   at 
> org.apache.phoenix.jdbc.PhoenixStatement.executeQuery(PhoenixStatement.java:287)
>   at 
> org.apache.phoenix.jdbc.PhoenixStatement.execute(PhoenixStatement.java:1930)
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (PHOENIX-6453) Possible ArrayIndexOutOfBoundsException while preparing scan start key with multiple key range queries

2021-05-04 Thread Rajeshbabu Chintaguntla (Jira)



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

Rajeshbabu Chintaguntla updated PHOENIX-6453:
-
Fix Version/s: 5.1.2
   4.17.0

> Possible ArrayIndexOutOfBoundsException while preparing scan start key with 
> multiple key range queries
> --
>
> Key: PHOENIX-6453
> URL: https://issues.apache.org/jira/browse/PHOENIX-6453
> Project: Phoenix
>  Issue Type: Bug
>Reporter: Rajeshbabu Chintaguntla
>Assignee: Rajeshbabu Chintaguntla
>Priority: Major
> Fix For: 4.17.0, 5.1.2
>
>
> There is possible AIOOE when there are multiple key range conditions on 
> columns in a query.
> {noformat}
> java.lang.ArrayIndexOutOfBoundsException: 25
>   at org.apache.phoenix.util.ScanUtil.setKey(ScanUtil.java:474)
>   at org.apache.phoenix.util.ScanUtil.setKey(ScanUtil.java:408)
>   at org.apache.phoenix.util.ScanUtil.getKey(ScanUtil.java:380)
>   at org.apache.phoenix.util.ScanUtil.getMinKey(ScanUtil.java:353)
>   at org.apache.phoenix.compile.ScanRanges.create(ScanRanges.java:134)
>   at 
> org.apache.phoenix.compile.WhereOptimizer.pushKeyExpressionsToScan(WhereOptimizer.java:355)
>   at 
> org.apache.phoenix.compile.WhereCompiler.compile(WhereCompiler.java:171)
>   at 
> org.apache.phoenix.compile.WhereCompiler.compile(WhereCompiler.java:118)
>   at 
> org.apache.phoenix.compile.QueryCompiler.compileSingleFlatQuery(QueryCompiler.java:747)
>   at 
> org.apache.phoenix.compile.QueryCompiler.compileSingleQuery(QueryCompiler.java:674)
>   at 
> org.apache.phoenix.compile.QueryCompiler.compileSelect(QueryCompiler.java:251)
>   at 
> org.apache.phoenix.compile.QueryCompiler.compile(QueryCompiler.java:178)
>   at 
> org.apache.phoenix.jdbc.PhoenixStatement$ExecutableSelectStatement.compilePlan(PhoenixStatement.java:501)
>   at 
> org.apache.phoenix.jdbc.PhoenixStatement$ExecutableSelectStatement.compilePlan(PhoenixStatement.java:464)
>   at 
> org.apache.phoenix.jdbc.PhoenixStatement$1.call(PhoenixStatement.java:306)
>   at 
> org.apache.phoenix.jdbc.PhoenixStatement$1.call(PhoenixStatement.java:295)
>   at org.apache.phoenix.call.CallRunner.run(CallRunner.java:53)
>   at 
> org.apache.phoenix.jdbc.PhoenixStatement.executeQuery(PhoenixStatement.java:294)
>   at 
> org.apache.phoenix.jdbc.PhoenixStatement.executeQuery(PhoenixStatement.java:287)
>   at 
> org.apache.phoenix.jdbc.PhoenixStatement.execute(PhoenixStatement.java:1930)
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (PHOENIX-6271) Effective DDL generated by SchemaExtractionTool should maintain the order of PK and other columns

2021-05-04 Thread Swaroopa Kadam (Jira)



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

Swaroopa Kadam resolved PHOENIX-6271.
-
Resolution: Fixed

> Effective DDL generated by SchemaExtractionTool should maintain the order of 
> PK and other columns
> -
>
> Key: PHOENIX-6271
> URL: https://issues.apache.org/jira/browse/PHOENIX-6271
> Project: Phoenix
>  Issue Type: Improvement
>Reporter: Swaroopa Kadam
>Assignee: Swaroopa Kadam
>Priority: Minor
> Fix For: 5.1.1, 4.16.1
>
>
> SchemaExtractionTool is used to generate effective DDL which can be then 
> compared with the DDL on the cluster to perform schema monitoring. 
> This won't affect the monitoring part but would be good to have the PR order 
> in place so that effective DDL can be used for creating the entity for the 
> first time in a new environment.
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[VOTE] Release of Apache Tephra 0.16.1 RC1

2021-05-04 Thread Viraj Jasani

Please vote on this Apache phoenix tephra release candidate,
phoenix-tephra-0.16.1RC1

The VOTE will remain open for at least 72 hours.

[ ] +1 Release this package as Apache phoenix tephra 0.16.1
[ ] -1 Do not release this package because ...

The tag to be voted on is 0.16.1RC1:

  https://github.com/apache/phoenix-tephra/tree/0.16.1RC1

The release files, including signatures, digests, as well as CHANGES.md
and RELEASENOTES.md included in this RC can be found at:

  https://dist.apache.org/repos/dist/dev/phoenix/phoenix-tephra-0.16.1RC1/

Maven artifacts are available in a staging repository at:

  https://repository.apache.org/content/repositories/orgapachephoenix-1233/

Artifacts were signed with the 1C8ADFD5 key which can be found in:

  https://dist.apache.org/repos/dist/release/phoenix/KEYS

To learn more about Apache phoenix tephra, please see

  https://tephra.incubator.apache.org/

Thanks,
Your Phoenix Release Manager

Re: [VOTE] Release of Apache Tephra 0.16.1

2021-05-04 Thread Viraj Jasani

Sinking this RC and creating new RC, will initiate Vote thread soon.
There is no new commit included in new RC hence no functional change.


On Tue, 4 May 2021 at 2:16 PM, Viraj Jasani  wrote:

> This is really surprising, I did see both repositories (Tephra 0.16.1 and
> Phoenix 4.16.1) when I sent this vote mail.
> I think we might have to sink this RC (Phoenix 4.16.1 as well) and create
> new one (without any changes) and manually close repository and only after
> sufficient votes are in, release them manually. Does it sound good?
>
>
> On Tue, 4 May 2021 at 12:56 PM, Istvan Toth 
> wrote:
>
>> I cannot see orgapachephoenix-1232
>> in  https://repository.apache.org/#stagingRepositories
>>
>> I'm not sure if it's normal, or if you need to *close* the repository
>> first.
>>
>> (BTW I cannot see any staging repository for 4.16.1 there either )
>>
>> Istvan
>>
>> On Thu, Apr 29, 2021 at 3:56 AM Xinyi Yan  wrote:
>>
>> > +1
>> >
>> > Build from source and unit tests pass(mvn clean verify).
>> >
>> > On Wed, Apr 28, 2021 at 12:27 AM Viraj Jasani 
>> wrote:
>> >
>> > > Please vote on this Apache phoenix tephra release candidate,
>> > > phoenix-tephra-0.16.1RC0
>> > >
>> > > The VOTE will remain open for at least 72 hours.
>> > >
>> > > [ ] +1 Release this package as Apache phoenix tephra 0.16.1
>> > > [ ] -1 Do not release this package because ...
>> > >
>> > > The tag to be voted on is 0.16.1RC0:
>> > >
>> > >   https://github.com/apache/phoenix-tephra/tree/0.16.1RC0
>> > >
>> > > The release files, including signatures, digests, as well as
>> CHANGES.md
>> > > and RELEASENOTES.md included in this RC can be found at:
>> > >
>> > >
>> >
>> https://dist.apache.org/repos/dist/dev/phoenix/phoenix-tephra-0.16.1RC0/
>> > >
>> > > Maven artifacts are available in a staging repository at:
>> > >
>> > >   https://repository.apache.org/#stagingRepositories
>> > >   (orgapachephoenix-1232)
>> > >
>> > > Artifacts were signed with the 1C8ADFD5 key which can be found in:
>> > >
>> > >   https://dist.apache.org/repos/dist/release/phoenix/KEYS
>> > >
>> > > To learn more about Apache phoenix tephra, please see
>> > >
>> > >   https://tephra.incubator.apache.org/
>> > >
>> > > Thanks,
>> > > Your Phoenix Release Manager
>> > >
>> > >
>> >
>>
>>
>> --
>> *István Tóth* | Staff Software Engineer
>> st...@cloudera.com 
>> [image: Cloudera] 
>> [image: Cloudera on Twitter]  [image:
>> Cloudera on Facebook]  [image:
>> Cloudera
>> on LinkedIn] 
>> 
>> --
>>
>

Re: [VOTE] Release of Apache Tephra 0.16.1

2021-05-04 Thread Viraj Jasani

This is really surprising, I did see both repositories (Tephra 0.16.1 and
Phoenix 4.16.1) when I sent this vote mail.
I think we might have to sink this RC (Phoenix 4.16.1 as well) and create
new one (without any changes) and manually close repository and only after
sufficient votes are in, release them manually. Does it sound good?


On Tue, 4 May 2021 at 12:56 PM, Istvan Toth 
wrote:

> I cannot see orgapachephoenix-1232
> in  https://repository.apache.org/#stagingRepositories
>
> I'm not sure if it's normal, or if you need to *close* the repository
> first.
>
> (BTW I cannot see any staging repository for 4.16.1 there either )
>
> Istvan
>
> On Thu, Apr 29, 2021 at 3:56 AM Xinyi Yan  wrote:
>
> > +1
> >
> > Build from source and unit tests pass(mvn clean verify).
> >
> > On Wed, Apr 28, 2021 at 12:27 AM Viraj Jasani 
> wrote:
> >
> > > Please vote on this Apache phoenix tephra release candidate,
> > > phoenix-tephra-0.16.1RC0
> > >
> > > The VOTE will remain open for at least 72 hours.
> > >
> > > [ ] +1 Release this package as Apache phoenix tephra 0.16.1
> > > [ ] -1 Do not release this package because ...
> > >
> > > The tag to be voted on is 0.16.1RC0:
> > >
> > >   https://github.com/apache/phoenix-tephra/tree/0.16.1RC0
> > >
> > > The release files, including signatures, digests, as well as CHANGES.md
> > > and RELEASENOTES.md included in this RC can be found at:
> > >
> > >
> > https://dist.apache.org/repos/dist/dev/phoenix/phoenix-tephra-0.16.1RC0/
> > >
> > > Maven artifacts are available in a staging repository at:
> > >
> > >   https://repository.apache.org/#stagingRepositories
> > >   (orgapachephoenix-1232)
> > >
> > > Artifacts were signed with the 1C8ADFD5 key which can be found in:
> > >
> > >   https://dist.apache.org/repos/dist/release/phoenix/KEYS
> > >
> > > To learn more about Apache phoenix tephra, please see
> > >
> > >   https://tephra.incubator.apache.org/
> > >
> > > Thanks,
> > > Your Phoenix Release Manager
> > >
> > >
> >
>
>
> --
> *István Tóth* | Staff Software Engineer
> st...@cloudera.com 
> [image: Cloudera] 
> [image: Cloudera on Twitter]  [image:
> Cloudera on Facebook]  [image: Cloudera
> on LinkedIn] 
> 
> --
>

[jira] [Resolved] (PHOENIX-6443) Update Connectors Phoenix dependency to 5.1.1

2021-05-04 Thread Istvan Toth (Jira)



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

Istvan Toth resolved PHOENIX-6443.
--
Resolution: Fixed

Committed.
Thanks for the thorough review [~richardantal]

> Update Connectors Phoenix dependency to 5.1.1
> -
>
> Key: PHOENIX-6443
> URL: https://issues.apache.org/jira/browse/PHOENIX-6443
> Project: Phoenix
>  Issue Type: Task
>  Components: connectors
>Affects Versions: connectors-6.0.0
>Reporter: Richárd Antal
>Assignee: Istvan Toth
>Priority: Major
> Fix For: connectors-6.0.0
>
>
> Phoenix-connectors still use phoenix 5.1.0 snapshot, It should be updated to 
> 5.1.1 (or 5.2.0 snapshot when that is available).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [VOTE] Release of Apache Tephra 0.16.1

2021-05-04 Thread Istvan Toth

I cannot see orgapachephoenix-1232
in  https://repository.apache.org/#stagingRepositories

I'm not sure if it's normal, or if you need to *close* the repository first.

(BTW I cannot see any staging repository for 4.16.1 there either )

Istvan

On Thu, Apr 29, 2021 at 3:56 AM Xinyi Yan  wrote:

> +1
>
> Build from source and unit tests pass(mvn clean verify).
>
> On Wed, Apr 28, 2021 at 12:27 AM Viraj Jasani  wrote:
>
> > Please vote on this Apache phoenix tephra release candidate,
> > phoenix-tephra-0.16.1RC0
> >
> > The VOTE will remain open for at least 72 hours.
> >
> > [ ] +1 Release this package as Apache phoenix tephra 0.16.1
> > [ ] -1 Do not release this package because ...
> >
> > The tag to be voted on is 0.16.1RC0:
> >
> >   https://github.com/apache/phoenix-tephra/tree/0.16.1RC0
> >
> > The release files, including signatures, digests, as well as CHANGES.md
> > and RELEASENOTES.md included in this RC can be found at:
> >
> >
> https://dist.apache.org/repos/dist/dev/phoenix/phoenix-tephra-0.16.1RC0/
> >
> > Maven artifacts are available in a staging repository at:
> >
> >   https://repository.apache.org/#stagingRepositories
> >   (orgapachephoenix-1232)
> >
> > Artifacts were signed with the 1C8ADFD5 key which can be found in:
> >
> >   https://dist.apache.org/repos/dist/release/phoenix/KEYS
> >
> > To learn more about Apache phoenix tephra, please see
> >
> >   https://tephra.incubator.apache.org/
> >
> > Thanks,
> > Your Phoenix Release Manager
> >
> >
>


-- 
*István Tóth* | Staff Software Engineer
st...@cloudera.com 
[image: Cloudera] 
[image: Cloudera on Twitter]  [image:
Cloudera on Facebook]  [image: Cloudera
on LinkedIn] 

--

[jira] [Updated] (PHOENIX-6453) Possible ArrayIndexOutOfBoundsException while preparing scan start key with multiple key range queries

[jira] [Updated] (PHOENIX-6453) Possible ArrayIndexOutOfBoundsException while preparing scan start key with multiple key range queries

[jira] [Resolved] (PHOENIX-6271) Effective DDL generated by SchemaExtractionTool should maintain the order of PK and other columns

[VOTE] Release of Apache Tephra 0.16.1 RC1

Re: [VOTE] Release of Apache Tephra 0.16.1

Re: [VOTE] Release of Apache Tephra 0.16.1

[jira] [Resolved] (PHOENIX-6443) Update Connectors Phoenix dependency to 5.1.1

Re: [VOTE] Release of Apache Tephra 0.16.1

8 matches

Site Navigation

Mail list logo

Footer information