Re: [DISCUSS] Releasing Phoenix-thirdparty 1.0
+1 On Fri, Oct 2, 2020, 8:34 AM Ankit Singhal wrote: > Sounds good to me. > > On Wed, Sep 30, 2020 at 9:48 AM Istvan Toth wrote: > > > Hi! > > > > We have been using phoenix-thirdparty snapshots in omid for a few weeks, > > and in phoenix (master) for about a week, and so far we haven't found any > > issues stemming from using Phoenix-thirdparty (effectively thirdparty > > Guava, the only current component). > > > > I think that we are ready to release Phoenix-thirdparty 1.0 now. > > > > My current plan is to cut an rc0 sometime next week, unless problems > arise, > > or someone voices an objection. > > > > Looking forward to hearing your opinion and feedback. > > > > regards > > Istvan > > >
Re: [DISCUSS] Releasing Phoenix-thirdparty 1.0
Sounds good to me. On Wed, Sep 30, 2020 at 9:48 AM Istvan Toth wrote: > Hi! > > We have been using phoenix-thirdparty snapshots in omid for a few weeks, > and in phoenix (master) for about a week, and so far we haven't found any > issues stemming from using Phoenix-thirdparty (effectively thirdparty > Guava, the only current component). > > I think that we are ready to release Phoenix-thirdparty 1.0 now. > > My current plan is to cut an rc0 sometime next week, unless problems arise, > or someone voices an objection. > > Looking forward to hearing your opinion and feedback. > > regards > Istvan >
[jira] [Created] (PHOENIX-6172) Updating VIEW_INDEX_ID column type and ts in Syscat with a 4.16 upgrade script
Xinyi Yan created PHOENIX-6172: -- Summary: Updating VIEW_INDEX_ID column type and ts in Syscat with a 4.16 upgrade script Key: PHOENIX-6172 URL: https://issues.apache.org/jira/browse/PHOENIX-6172 Project: Phoenix Issue Type: Improvement Affects Versions: 4.15.0 Reporter: Xinyi Yan Fix For: 4.16.0 Updating VIEW_INDEX_ID column type and ts in Syscat with a 4.16 upgrade script by using HBase put. Making sure the HBase row ts reflects the 4.16 version. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6169) IT suite never finishes on 4.x with HBase 1.3 or 1.4
[
https://issues.apache.org/jira/browse/PHOENIX-6169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth resolved PHOENIX-6169.
--
Fix Version/s: 5.1.0
Resolution: Fixed
Pushed to 4.x and master.
Thanks for the review [~ckulkarni].
> IT suite never finishes on 4.x with HBase 1.3 or 1.4
>
>
> Key: PHOENIX-6169
> URL: https://issues.apache.org/jira/browse/PHOENIX-6169
> Project: Phoenix
> Issue Type: Bug
> Components: core
>Affects Versions: 4.16.0
> Environment: ASF Jenkins (at least)
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Blocker
> Fix For: 5.1.0, 4.16.0
>
>
> running {{mvn verify}} on the current 4.x branch will hang indefinetly.
> Apart from making it impossible to run all tests, and get a successful test
> run, this also results in Yetus not being able to post precommit check
> results.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-6169) IT suite never finishes on 4.x with HBase 1.3 or 1.4
[
https://issues.apache.org/jira/browse/PHOENIX-6169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kulkarni updated PHOENIX-6169:
--
Fix Version/s: (was: 5.1.0)
> IT suite never finishes on 4.x with HBase 1.3 or 1.4
>
>
> Key: PHOENIX-6169
> URL: https://issues.apache.org/jira/browse/PHOENIX-6169
> Project: Phoenix
> Issue Type: Bug
> Components: core
>Affects Versions: 4.16.0
> Environment: ASF Jenkins (at least)
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Blocker
> Fix For: 4.16.0
>
>
> running {{mvn verify}} on the current 4.x branch will hang indefinetly.
> Apart from making it impossible to run all tests, and get a successful test
> run, this also results in Yetus not being able to post precommit check
> results.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-6169) IT suite never finishes on 4.x with HBase 1.3 or 1.4
[
https://issues.apache.org/jira/browse/PHOENIX-6169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kulkarni updated PHOENIX-6169:
--
Fix Version/s: 4.16.0
5.1.0
> IT suite never finishes on 4.x with HBase 1.3 or 1.4
>
>
> Key: PHOENIX-6169
> URL: https://issues.apache.org/jira/browse/PHOENIX-6169
> Project: Phoenix
> Issue Type: Bug
> Components: core
>Affects Versions: 4.16.0
> Environment: ASF Jenkins (at least)
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Blocker
> Fix For: 5.1.0, 4.16.0
>
>
> running {{mvn verify}} on the current 4.x branch will hang indefinetly.
> Apart from making it impossible to run all tests, and get a successful test
> run, this also results in Yetus not being able to post precommit check
> results.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (PHOENIX-6170) PHOENIX_TTL spec should in seconds instead of milliseconds
[ https://issues.apache.org/jira/browse/PHOENIX-6170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob Isaac reassigned PHOENIX-6170: Assignee: Jacob Isaac > PHOENIX_TTL spec should in seconds instead of milliseconds > -- > > Key: PHOENIX-6170 > URL: https://issues.apache.org/jira/browse/PHOENIX-6170 > Project: Phoenix > Issue Type: Sub-task >Reporter: Jacob Isaac >Assignee: Jacob Isaac >Priority: Major > > When defining the PHOENIX_TTL spec it should be specified in seconds, which > is also how HBase TTL value is set. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6170) PHOENIX_TTL spec should in seconds instead of milliseconds
[ https://issues.apache.org/jira/browse/PHOENIX-6170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob Isaac updated PHOENIX-6170: - Parent: PHOENIX-3725 Issue Type: Sub-task (was: Improvement) > PHOENIX_TTL spec should in seconds instead of milliseconds > -- > > Key: PHOENIX-6170 > URL: https://issues.apache.org/jira/browse/PHOENIX-6170 > Project: Phoenix > Issue Type: Sub-task >Reporter: Jacob Isaac >Priority: Major > > When defining the PHOENIX_TTL spec it should be specified in seconds, which > is also how HBase TTL value is set. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6171) Child views should not be allowed to override the parent view PHOENIX_TTL attribute.
Jacob Isaac created PHOENIX-6171: Summary: Child views should not be allowed to override the parent view PHOENIX_TTL attribute. Key: PHOENIX-6171 URL: https://issues.apache.org/jira/browse/PHOENIX-6171 Project: Phoenix Issue Type: Sub-task Reporter: Jacob Isaac Assignee: Jacob Isaac -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6170) PHOENIX_TTL spec should in seconds instead of milliseconds
Jacob Isaac created PHOENIX-6170: Summary: PHOENIX_TTL spec should in seconds instead of milliseconds Key: PHOENIX-6170 URL: https://issues.apache.org/jira/browse/PHOENIX-6170 Project: Phoenix Issue Type: Improvement Reporter: Jacob Isaac When defining the PHOENIX_TTL spec it should be specified in seconds, which is also how HBase TTL value is set. -- This message was sent by Atlassian Jira (v8.3.4#803005)
