[jira] [Resolved] (PHOENIX-6370) 4.x branch still includes the phoenix-pig example files

[Istvan Toth (Jira)]

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

Istvan Toth resolved PHOENIX-6370.
--
Fix Version/s: 4.17.0
   Resolution: Fixed

Thanks for the reviews [~dbwong] and [~vjasani]

> 4.x branch still includes the phoenix-pig example files
> ---
>
> Key: PHOENIX-6370
> URL: https://issues.apache.org/jira/browse/PHOENIX-6370
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.16.0
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Trivial
> Fix For: 4.17.0
>
>
> remove them



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

[jira] [Updated] (PHOENIX-6370) 4.x branch still includes the phoenix-pig example files

[Istvan Toth (Jira)]

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

Istvan Toth updated PHOENIX-6370:
-
Affects Version/s: 4.16.0

> 4.x branch still includes the phoenix-pig example files
> ---
>
> Key: PHOENIX-6370
> URL: https://issues.apache.org/jira/browse/PHOENIX-6370
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.16.0
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Trivial
>
> remove them



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

[jira] [Resolved] (PHOENIX-6396) PChar illegal data exception should not contain value

[Xinyi Yan (Jira)]

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

Xinyi Yan resolved PHOENIX-6396.

Resolution: Fixed

> PChar illegal data exception should not contain value
> -
>
> Key: PHOENIX-6396
> URL: https://issues.apache.org/jira/browse/PHOENIX-6396
> Project: Phoenix
>  Issue Type: Improvement
>Reporter: Xinyi Yan
>Assignee: Xinyi Yan
>Priority: Major
> Fix For: 5.1.1, 4.17.0
>
>




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

Re: [VOTE] Release of Apache Phoenix 4.16.0 RC3

[Chinmay Kulkarni]

+1 (Binding)

Tested against hbase-1.3 and hbase-1.6

* Build from source (mvn clean install -DskipTests
-Dhbase.profile=1.3/1.6): OK
* Did some basic DDL, queries, upserts, deletes and everything looked fine:
OK
* Did some upgrade testing: Create tables, views, indices from an old
client, query, upsert. Then upgrade to 4.16 metadata, query, upsert from an
old client, then upgrade the client and query, upsert from a new client: OK
* Verified checksums: OK
* Verified signatures: OK
* mvn clean apache-rat:check: OK

On Sun, Feb 21, 2021 at 7:54 AM Josh Elser  wrote:

> Be sure to update
> https://dist.apache.org/repos/dist/release/phoenix/KEYS with your key
> prior to releasing this.
>
> +1 (binding)
>
> * Sigs/xsums are good
> * No unexpected files in source release
> * rat:check passes
> * Build from src, ran against 1.4.13
>
> On 2/16/21 12:08 AM, Xinyi Yan wrote:
> > Hello Everyone,
> >
> > This is a call for a vote on Apache Phoenix 4.16.0 RC3. This is the next
> > minor release of Phoenix 4, compatible with Apache HBase 1.3, 1.4, 1.5
> > and 1.6.
> >
> > The VOTE will remain open for at least 72 hours.
> >
> > [ ] +1 Release this package as Apache phoenix 4.16.0
> > [ ] -1 Do not release this package because ...
> >
> > The tag to be voted on is 4.16.0RC3
> > https://github.com/apache/phoenix/tree/4.16.0RC3
> >
> > 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-4.16.0RC3
> >
> > For a complete list of changes, see:
> > <
> https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.16.0RC2/CHANGES.md
> >
> >
> https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.16.0RC3/CHANGES.md
> >
> > Artifacts are signed with my "CODE SIGNING KEY":
> > E4882DD3AB711587
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/dev/phoenix/KEYS
> >
> >
> > Thanks,
> > Xinyi
> >
>


-- 
Chinmay Kulkarni

[jira] [Created] (PHOENIX-6396) PChar illegal data exception should not contain value

[Xinyi Yan (Jira)]

Xinyi Yan created PHOENIX-6396:
--

 Summary: PChar illegal data exception should not contain value
 Key: PHOENIX-6396
 URL: https://issues.apache.org/jira/browse/PHOENIX-6396
 Project: Phoenix
  Issue Type: Improvement
Reporter: Xinyi Yan
Assignee: Xinyi Yan
 Fix For: 5.1.1, 4.17.0






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

[jira] [Assigned] (PHOENIX-6395) Reusing Connection instance object instead of creating everytime in PhoenixAccessController class.

[vikas meka (Jira)]

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

vikas meka reassigned PHOENIX-6395:
---

Assignee: vikas meka

> Reusing Connection instance object instead of creating everytime in 
> PhoenixAccessController class. 
> ---
>
> Key: PHOENIX-6395
> URL: https://issues.apache.org/jira/browse/PHOENIX-6395
> Project: Phoenix
>  Issue Type: Bug
>Reporter: vikas meka
>Assignee: vikas meka
>Priority: Major
> Fix For: 4.17.0, 5.2.0
>
>




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

[jira] [Created] (PHOENIX-6395) Reusing Connection instance object instead of creating everytime in PhoenixAccessController class.

[vikas meka (Jira)]

vikas meka created PHOENIX-6395:
---

 Summary: Reusing Connection instance object instead of creating 
everytime in PhoenixAccessController class. 
 Key: PHOENIX-6395
 URL: https://issues.apache.org/jira/browse/PHOENIX-6395
 Project: Phoenix
  Issue Type: Bug
Reporter: vikas meka
 Fix For: 4.17.0, 5.2.0






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

[jira] [Resolved] (PHOENIX-6394) PostCommit Jenkins job detects incorrect HBase profile to rebuild with 2.3 and 2.4

[Istvan Toth (Jira)]

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

Istvan Toth resolved PHOENIX-6394.
--
Fix Version/s: 5.2.0
   5.1.1
   Resolution: Fixed

Committed to master and 5.1

Thanks for the review [~vjasani]

> PostCommit Jenkins job detects incorrect HBase profile to rebuild with 2.3 
> and 2.4
> --
>
> Key: PHOENIX-6394
> URL: https://issues.apache.org/jira/browse/PHOENIX-6394
> Project: Phoenix
>  Issue Type: Task
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Major
> Fix For: 5.1.1, 5.2.0
>
>
> The maven command that should extract the HBase version to rebuild often 
> returns *1.0.1* for the HBase 2.3 and 2.4 profiles



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

[jira] [Resolved] (PHOENIX-6386) Bulkload generates unverified index rows

[Istvan Toth (Jira)]

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

Istvan Toth resolved PHOENIX-6386.
--
Fix Version/s: 5.2.0
   4.17.0
   5.1.1
   Resolution: Fixed

Committed to master, 4.x, and 5.1. Thanks for the review [~vjasani].

[~yanxinyi] even if we don't want to do another RC with this fix, I believe 
that this should go at least in 4.16.1


> Bulkload generates unverified index rows
> 
>
> Key: PHOENIX-6386
> URL: https://issues.apache.org/jira/browse/PHOENIX-6386
> Project: Phoenix
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.1.0, 4.16.0
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Major
> Fix For: 5.1.1, 4.17.0, 5.2.0
>
>
> Bulkload sets the index status cell of the generated global index rows to the 
> default 'x' value.
> As a result, all such indexes are treated as unverified, and the first access 
> will generate index verification load, and be very slow.
> We should generate the index rows with the VERIFIED state.



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