[jira] [Assigned] (PHOENIX-3430) Optimizer not using all columns from secondary index

[ https://issues.apache.org/jira/browse/PHOENIX-3430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swaroopa Kadam reassigned PHOENIX-3430: --- Assignee: Swaroopa Kadam > Optimizer not using all columns from secondary index >

Re: Board report due in ~1 week

Should we use 2.0.5 ( the latest released HBase version )? If PHOENIX-5250 is a blocker we will need to fix it before we can release 5.0.1 (or 5.1). These are the list of bugs that have a fix version of 5.1 :

[jira] [Updated] (PHOENIX-4940) IndexTool should be able to rebuild tenant-owned indexes

[ https://issues.apache.org/jira/browse/PHOENIX-4940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-4940: Fix Version/s: (was: 5.1) 5.1.0 > IndexTool should be able to

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

[ https://issues.apache.org/jira/browse/PHOENIX-4781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-4781: Fix Version/s: (was: 5.1) 5.1.0 > Phoenix client project's jar

[jira] [Updated] (PHOENIX-4345) Error message for incorrect index is not accurate

[ https://issues.apache.org/jira/browse/PHOENIX-4345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-4345: Fix Version/s: (was: 5.1) 5.1.0 > Error message for incorrect

[jira] [Updated] (PHOENIX-5066) The TimeZone is incorrectly used during writing or reading data

[ https://issues.apache.org/jira/browse/PHOENIX-5066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-5066: Fix Version/s: (was: 5.1) 5.1.0 > The TimeZone is incorrectly

[jira] [Updated] (PHOENIX-2265) Disallow creation of view over HBase table if PK not specified

[ https://issues.apache.org/jira/browse/PHOENIX-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-2265: Fix Version/s: (was: 5.1) 5.1.0 > Disallow creation of view over

[jira] [Updated] (PHOENIX-5073) Invalid PIndexState during rolling upgrade from 4.13 to 4.14

[ https://issues.apache.org/jira/browse/PHOENIX-5073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-5073: Fix Version/s: (was: 5.1) 5.1.0 > Invalid PIndexState during

[jira] [Updated] (PHOENIX-5018) Index mutations created by UPSERT SELECT will have wrong timestamps

[ https://issues.apache.org/jira/browse/PHOENIX-5018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-5018: Fix Version/s: (was: 5.1) 5.1.0 > Index mutations created by

[jira] [Updated] (PHOENIX-5089) IndexScrutinyTool should be able to analyze tenant-owned indexes

[ https://issues.apache.org/jira/browse/PHOENIX-5089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-5089: Fix Version/s: (was: 5.1) 5.1.0 > IndexScrutinyTool should be

[jira] [Updated] (PHOENIX-5168) IndexScrutinyTool cannot output to table when analyzing tenant-owned indexes

[ https://issues.apache.org/jira/browse/PHOENIX-5168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-5168: Fix Version/s: (was: 5.1) 5.1.0 > IndexScrutinyTool cannot output

[jira] [Updated] (PHOENIX-5169) Query logger is still initialized for each query when the log level is off

[ https://issues.apache.org/jira/browse/PHOENIX-5169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-5169: Fix Version/s: (was: 5.1) 5.1.0 > Query logger is still

[jira] [Updated] (PHOENIX-5132) View indexes with different owners but of the same base table can be assigned same ViewIndexId

[ https://issues.apache.org/jira/browse/PHOENIX-5132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-5132: Fix Version/s: (was: 5.1) 5.1.0 > View indexes with different

[jira] [Updated] (PHOENIX-5188) IndexedKeyValue should populate KeyValue fields

[ https://issues.apache.org/jira/browse/PHOENIX-5188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-5188: Fix Version/s: (was: 5.1) 5.1.0 > IndexedKeyValue should populate

[jira] [Updated] (PHOENIX-5251) Avoid taking explicit lock by using AtomicReference in PhoenixAccessController class

[ https://issues.apache.org/jira/browse/PHOENIX-5251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-5251: Fix Version/s: (was: 5.1) 5.1.0 > Avoid taking explicit lock by

[jira] [Updated] (PHOENIX-5250) The accumulated wal files can't be cleaned

[ https://issues.apache.org/jira/browse/PHOENIX-5250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-5250: Fix Version/s: 5.1.0 > The accumulated wal files can't be cleaned >

Re: [ANNOUNCE] New Phoenix committer: Mihir Monani

Congratulations, Mihir! On Tue, Apr 30, 2019 at 6:01 PM Ankit Singhal wrote: > Congratulations and Welcome Mihir !! > > On Tue, Apr 30, 2019 at 5:49 PM Andrew Purtell > wrote: > > > Congratulations Mihir. > > > > On Sat, Apr 27, 2019 at 5:42 PM Thomas D'Silva > wrote: > > > > > On behalf of

[jira] [Updated] (PHOENIX-5262) Wrong Result on Salted table with some Variable Length PKs

[ https://issues.apache.org/jira/browse/PHOENIX-5262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Wong updated PHOENIX-5262: - Attachment: PHOENIX-5262v3.patch > Wrong Result on Salted table with some Variable Length PKs

Re: [ANNOUNCE] New Phoenix committer: Mihir Monani

Congratulations and Welcome Mihir !! On Tue, Apr 30, 2019 at 5:49 PM Andrew Purtell wrote: > Congratulations Mihir. > > On Sat, Apr 27, 2019 at 5:42 PM Thomas D'Silva wrote: > > > On behalf of the Apache Phoenix PMC, I am pleased to announce that > > Mihir Monani has accepted our invitation to

Re: [ANNOUNCE] New Phoenix committer: Mihir Monani

Congratulations Mihir. On Sat, Apr 27, 2019 at 5:42 PM Thomas D'Silva wrote: > On behalf of the Apache Phoenix PMC, I am pleased to announce that > Mihir Monani has accepted our invitation to become a committer. > Mihir has done some nice work fixing several bugs related to indexing[1]. > >

[jira] [Assigned] (PHOENIX-1955) Phoenix create table with salt_bucket,then csvload data,index table is null

[ https://issues.apache.org/jira/browse/PHOENIX-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swaroopa Kadam reassigned PHOENIX-1955: --- Assignee: Swaroopa Kadam > Phoenix create table with salt_bucket,then csvload

[jira] [Assigned] (PHOENIX-2882) NPE during View creation for table with secondary index

[ https://issues.apache.org/jira/browse/PHOENIX-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swaroopa Kadam reassigned PHOENIX-2882: --- Assignee: Swaroopa Kadam > NPE during View creation for table with secondary

[jira] [Updated] (PHOENIX-5262) Wrong Result on Salted table with some Variable Length PKs

[ https://issues.apache.org/jira/browse/PHOENIX-5262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Wong updated PHOENIX-5262: - Summary: Wrong Result on Salted table with some Variable Length PKs (was: Wrong Result on

[jira] [Updated] (PHOENIX-5265) Phoenix Test should use gold files for result comparison instead of using hard-corded comparison.

[ https://issues.apache.org/jira/browse/PHOENIX-5265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bin Shi updated PHOENIX-5265: - Description: Currently, in Phoenix Test, the comparison of the returned result and the expected

[jira] [Updated] (PHOENIX-5265) Phoenix Test should use gold files for result comparison instead of using hard-corded comparison.

[ https://issues.apache.org/jira/browse/PHOENIX-5265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bin Shi updated PHOENIX-5265: - Description: Currently, in Phoenix Test, the comparison of the returned result and the expected

[jira] [Created] (PHOENIX-5265) Phoenix Test should use gold files for result comparison instead of using hard-corded comparison.

Bin Shi created PHOENIX-5265: Summary: Phoenix Test should use gold files for result comparison instead of using hard-corded comparison. Key: PHOENIX-5265 URL: https://issues.apache.org/jira/browse/PHOENIX-5265

[jira] [Updated] (PHOENIX-5258) Add support to parse header from the input CSV file as input columns for CsvBulkLoadTool

[ https://issues.apache.org/jira/browse/PHOENIX-5258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Vithani updated PHOENIX-5258: -- Summary: Add support to parse header from the input CSV file as input columns for

[jira] [Updated] (PHOENIX-5258) Add support for header in input CSV for CsvBulkLoadTool

[ https://issues.apache.org/jira/browse/PHOENIX-5258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Vithani updated PHOENIX-5258: -- Description: Currently, CsvBulkLoadTool does not support reading header from the

[DISCUSS] Next Phoenix 5.x release (was "Board report due in ~1 week")

Let's leave the other thread for the board report, please. I've changed the subject as such. Thanks for volunteering to be RM. I'm of the opinion that we should just update to the latest HBase 2.0.x line. The compatibility assertions from HBase should make this a no-op for us to change

Re: [ANNOUNCE] New Phoenix committer: Mihir Monani

Congratulations and welcome Mihir! 在 2019-04-30 14:35:54，"Jaanai Zhang" 写道： >congrats! Mihir. > > > Jaanai Zhang > Best regards! > > > >Mihir Monani 于2019年4月30日周二 下午1:13写道： > >> Thanks Thomas and Apache Phoenix Community. :) >> >> On Sun, Apr

Re: [ANNOUNCE] New Phoenix committer: Mihir Monani

congrats! Mihir. Jaanai Zhang Best regards! Mihir Monani 于2019年4月30日周二 下午1:13写道： > Thanks Thomas and Apache Phoenix Community. :) > > On Sun, Apr 28, 2019 at 6:12 AM Thomas D'Silva wrote: > > > On behalf of the Apache Phoenix PMC, I am pleased

Re: Board report due in ~1 week

I will try doing release 5.0.1. Tow things need to confirm: 1. According to the thread[1], a new Phoenix 5.0.1 will support HBase 2.0.2, right? As far as I know, some improvements of HBase 2.0.2 will cause some critical issues, for example, https://issues.apache.org/jira/browse/PHOENIX-5250

[jira] [Updated] (PHOENIX-5250) The accumulated wal files can't be cleaned

[ https://issues.apache.org/jira/browse/PHOENIX-5250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaanai updated PHOENIX-5250: Affects Version/s: (was: 5.0.0) > The accumulated wal files can't be cleaned >