Re: [VOTE] Graduate into the Phoenix project
+1 On Wed, Oct 30, 2019 at 12:21 PM Alan Gates wrote: > I propose that the Tephra project leave the incubator and become part of > the Phoenix project. The Phoenix project has proposed to incorporate both > Omid and Tephra as sub-projects. Phoenix will take over administration of > the Tephra repo. Any Tephra committers that request committership in > Phoenix will be granted it.[1] > > Here's my +1 on the proposal. This vote will remain open for 72 hours. > > Alan. > > 1. > > https://lists.apache.org/thread.html/29111aa8b59fe38ca11d6ca2f029009c437ed6986d6dcf2fb6fc5b2f@%3Cdev.phoenix.apache.org%3E >
[jira] [Commented] (TEPHRA-301) Support HBase 1.5.x
[ https://issues.apache.org/jira/browse/TEPHRA-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16873621#comment-16873621 ] James Taylor commented on TEPHRA-301: - In the past, if there's no need for changes to the compat module for a given HBase release, no compat module is created. Copy/pasting the entire compat module just creates extra work when changes are required to compat modules. > Support HBase 1.5.x > --- > > Key: TEPHRA-301 > URL: https://issues.apache.org/jira/browse/TEPHRA-301 > Project: Tephra > Issue Type: Bug >Reporter: Lars Hofhansl >Assignee: Lars Hofhansl >Priority: Major > Attachments: 301-full.txt, 301.txt > > > I have a half-baked patch to support HBase 1.5. > Going to post it here soon. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Proposed Jun19 incubator report for Tephra
+1 On Tue, Jun 4, 2019 at 4:36 PM Terence Yim wrote: > +1 from me > > On Tue, Jun 4, 2019 at 4:35 PM Andreas Neumann wrote: > > > All, please see the proposed report for this month. It's a bit of a last > > notice as it is due to day, so please send me feedback if I got anything > > wrong. > > Cheers -Andreas > > > > Tephra is a system for providing globally consistent transactions on top > of > > Apache HBase and other storage engines. > > > > Tephra has been incubating since 2016-03-07. > > > > Most important unfinished issues to address before graduating: > > 1. Improve community engagement > > 2. Increase adoption > > > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be > aware > > of? > > - None at this time. > > > > How has the community developed since the last report? > > - 4 new JIRAs filed since the last report > > > > How has the project developed since the last report? > > - Working on 0.16.0-incubating release > > - Working on HBase 1.5 and 2.1 support > > > > How would you assess the podling's maturity? Please feel free to add your > > own commentary. > > - [ ] Initial setup > > - [ ] Working towards first release > > - [x] Community building > > - [ ] Nearing graduation > > - [ ] Other: > > > > Date of last release: > > - 2018-09-04 > > > > When were the last committers or PPMC members elected? > > - None since coming to incubation > > > > Have your mentors been helpful? Have your mentors been helpful and > > responsive or are things falling through the cracks? In the latter case, > > please list any open issues that need to be addressed. > > - Mentors are helpful and responsive. We do only have two mentors. > > > > Signed-off-by: > > - [ ] (tephra) Alan Gates Comments: > > - [ ] (tephra) James Taylor Comments: > > >
[jira] [Commented] (TEPHRA-300) Tephra coprocessors do not close passed scanner
[ https://issues.apache.org/jira/browse/TEPHRA-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16855174#comment-16855174 ] James Taylor commented on TEPHRA-300: - +1 > Tephra coprocessors do not close passed scanner > --- > > Key: TEPHRA-300 > URL: https://issues.apache.org/jira/browse/TEPHRA-300 > Project: Tephra > Issue Type: Bug >Reporter: Lars Hofhansl >Assignee: Lars Hofhansl >Priority: Major > Attachments: 300-v2.txt, 300.txt > > > With HBase 1.5+ this leads to incorrect reference counting on opened HFile > resulting in those to never get archived. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TEPHRA-299) Executing a large batch delete is very slow
[ https://issues.apache.org/jira/browse/TEPHRA-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16855173#comment-16855173 ] James Taylor commented on TEPHRA-299: - +1 > Executing a large batch delete is very slow > --- > > Key: TEPHRA-299 > URL: https://issues.apache.org/jira/browse/TEPHRA-299 > Project: Tephra > Issue Type: Bug >Affects Versions: 0.15.0-incubating >Reporter: Lars Hofhansl >Assignee: Lars Hofhansl >Priority: Major > Attachments: 299-DOES-NOT_WORK.txt, 299-client-v2.txt, > 299-client-v3.txt, 299-client.txt, 299-complete.txt > > > I noticed that batch deletes are quire slow. In the profiler I found that > almost all of the time is spent in > org.apache.hadoop.hbase.regionserver.wal.FSHLog.blockOnSync(). > Looking at TransactionProcessor.preDelete it is obvious why: > The batch delete is translated into *single* puts that are added to the > region one by one, so each time the WAL is flushed. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (TEPHRA-295) Sync KEYS in master with dist.apache.org/repos/dist/dev/incubator/tephra/KEYS
[ https://issues.apache.org/jira/browse/TEPHRA-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor reassigned TEPHRA-295: --- Assignee: James Taylor (was: Poorna Chandra) > Sync KEYS in master with dist.apache.org/repos/dist/dev/incubator/tephra/KEYS > - > > Key: TEPHRA-295 > URL: https://issues.apache.org/jira/browse/TEPHRA-295 > Project: Tephra > Issue Type: Improvement > Reporter: James Taylor > Assignee: James Taylor >Priority: Major > Fix For: 0.15.0-incubating > > Attachments: TEPHRA-295.patch > > > [~alangates] noticed that the KEYS file in master is not in sync with the one > in [https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS.] Should it > be? If yes, please review attached patch, [~poornachandra]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEPHRA-295) Sync KEYS in master with dist.apache.org/repos/dist/dev/incubator/tephra/KEYS
[ https://issues.apache.org/jira/browse/TEPHRA-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-295: Fix Version/s: 0.15.0-incubating > Sync KEYS in master with dist.apache.org/repos/dist/dev/incubator/tephra/KEYS > - > > Key: TEPHRA-295 > URL: https://issues.apache.org/jira/browse/TEPHRA-295 > Project: Tephra > Issue Type: Improvement > Reporter: James Taylor > Assignee: James Taylor >Priority: Major > Fix For: 0.15.0-incubating > > Attachments: TEPHRA-295.patch > > > [~alangates] noticed that the KEYS file in master is not in sync with the one > in [https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS.] Should it > be? If yes, please review attached patch, [~poornachandra]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (TEPHRA-295) Sync KEYS in master with dist.apache.org/repos/dist/dev/incubator/tephra/KEYS
[ https://issues.apache.org/jira/browse/TEPHRA-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved TEPHRA-295. - Resolution: Fixed > Sync KEYS in master with dist.apache.org/repos/dist/dev/incubator/tephra/KEYS > - > > Key: TEPHRA-295 > URL: https://issues.apache.org/jira/browse/TEPHRA-295 > Project: Tephra > Issue Type: Improvement > Reporter: James Taylor > Assignee: James Taylor >Priority: Major > Fix For: 0.15.0-incubating > > Attachments: TEPHRA-295.patch > > > [~alangates] noticed that the KEYS file in master is not in sync with the one > in [https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS.] Should it > be? If yes, please review attached patch, [~poornachandra]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[RESULT][VOTE] Release of Apache Tephra-0.15.0-incubating [rc1]
The vote is now closed and passes with 3 +1s and 1 +0. I'll start the vote on the incubator general list next. Thanks, James On Fri, Aug 24, 2018 at 10:50 AM, James Taylor wrote: > +1 > > All unit tests passing > No more timeouts in Phoenix transactional unit tests > > I've filed TEPHRA-296 for the rat check failure, but more discussion is > needed to determine the best fix. I've marked it as a blocker for the next > release. > > Thanks, > James > > On Thu, Aug 23, 2018 at 9:19 PM, Thomas D'Silva > wrote: > >> +1 >> >> Ran transaction related tests using the rc and they all passed. >> >> On Tue, Aug 21, 2018 at 12:10 PM, Alan Gates >> wrote: >> >> > Having the keys in the dist area and not in Tephra's github is fine. I >> > misunderstood which KEYS file you were referencing. Maybe the one in >> the >> > Tephra repo should be removed. >> > >> > I agree that Tephra doesn't need the licenses if it's not shipping the >> > code. >> > >> > Alan. >> > >> > On Tue, Aug 21, 2018 at 11:26 AM James Taylor >> > wrote: >> > >> > > Thanks for checking it out, Alan. I checked in my public key info >> > here[1], >> > > but I'll commit to master branch as well. Based on Josh's email from >> > prior >> > > release vote [2], it looks like the rat check is failing for the >> > following >> > > files: >> > > >> > > >> > > apache-tephra-0.14.0-incubating/tephra-distribution/licenses/Aopa.PL >> > > apache-tephra-0.14.0-incubating/tephra-distribution/licenses/Asm.BSD >> > > apache-tephra-0.14.0-incubating/tephra-distribution/ >> licenses/JLine.BSD >> > > apache-tephra-0.14.0-incubating/tephra-distribution/ >> licenses/Logback.EPL >> > > apache-tephra-0.14.0-incubating/tephra-distribution/NOTICE_BINARY >> > > >> > > >> > > Since Tephra does a source-only release, I don't think the >> NOTICE_BINARY >> > is >> > > necessary. Same with the licenses - not sure we need those either. >> We're >> > > not including any source code from those projects - those would just >> be >> > > pulled in through maven when built. >> > > >> > > Thoughts? >> > > James >> > > >> > > [1] https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS >> > > [2] >> > > >> > > https://lists.apache.org/thread.html/fed5c54f775fda7a2e7393095f8d16 >> > a7e439e8c51b7b1be7619fd283@%3Cgeneral.incubator.apache.org%3E >> > > >> > > >> > > On Tue, Aug 21, 2018 at 10:49 AM, Alan Gates >> > wrote: >> > > >> > > > Which version of the KEYS file did you add it to? I don't see a >> change >> > > to >> > > > the KEYS file in master or the 0.15.0 branch. >> > > > >> > > > Also, at this point I'm +0 on this release, as the rat check still >> > fails, >> > > > which I complained about on the last release vote. As indicated by >> the >> > > +0 >> > > > you don't have to fix this to release, but you do to get my vote. :) >> > > > >> > > > Alan. >> > > > >> > > > On Mon, Aug 20, 2018 at 10:49 PM Poorna Chandra >> > > wrote: >> > > > >> > > > > +1 >> > > > > >> > > > > On Mon, Aug 20, 2018 at 11:45 PM James Taylor < >> > jamestay...@apache.org> >> > > > > wrote: >> > > > > >> > > > > > Thanks for reviewing, Poorna. Yes, my code signing key has >> changed. >> > > > I've >> > > > > > removed the MD5 file from the source distribution and added my >> new >> > > code >> > > > > > signing key to the KEYS file. >> > > > > > >> > > > > > James >> > > > > > >> > > > > > On Sat, Aug 18, 2018 at 7:38 PM, Poorna Chandra < >> poo...@apache.org >> > > >> > > > > wrote: >> > > > > > >> > > > > > > -1 >> > > > > > > >> > > > > > > - Checked build and test >> > > > > > > - Checked signature and checksums >> > > > > > > - Checked LICENSE, NOTICE and DISCLAIMER >> > >
Re: [VOTE] Release of Apache Tephra-0.15.0-incubating [rc1]
+1 All unit tests passing No more timeouts in Phoenix transactional unit tests I've filed TEPHRA-296 for the rat check failure, but more discussion is needed to determine the best fix. I've marked it as a blocker for the next release. Thanks, James On Thu, Aug 23, 2018 at 9:19 PM, Thomas D'Silva wrote: > +1 > > Ran transaction related tests using the rc and they all passed. > > On Tue, Aug 21, 2018 at 12:10 PM, Alan Gates wrote: > > > Having the keys in the dist area and not in Tephra's github is fine. I > > misunderstood which KEYS file you were referencing. Maybe the one in the > > Tephra repo should be removed. > > > > I agree that Tephra doesn't need the licenses if it's not shipping the > > code. > > > > Alan. > > > > On Tue, Aug 21, 2018 at 11:26 AM James Taylor > > wrote: > > > > > Thanks for checking it out, Alan. I checked in my public key info > > here[1], > > > but I'll commit to master branch as well. Based on Josh's email from > > prior > > > release vote [2], it looks like the rat check is failing for the > > following > > > files: > > > > > > > > > apache-tephra-0.14.0-incubating/tephra-distribution/licenses/Aopa.PL > > > apache-tephra-0.14.0-incubating/tephra-distribution/licenses/Asm.BSD > > > apache-tephra-0.14.0-incubating/tephra-distribution/licenses/JLine.BSD > > > apache-tephra-0.14.0-incubating/tephra-distribution/licenses/Logback. > EPL > > > apache-tephra-0.14.0-incubating/tephra-distribution/NOTICE_BINARY > > > > > > > > > Since Tephra does a source-only release, I don't think the > NOTICE_BINARY > > is > > > necessary. Same with the licenses - not sure we need those either. > We're > > > not including any source code from those projects - those would just be > > > pulled in through maven when built. > > > > > > Thoughts? > > > James > > > > > > [1] https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS > > > [2] > > > > > > https://lists.apache.org/thread.html/fed5c54f775fda7a2e7393095f8d16 > > a7e439e8c51b7b1be7619fd283@%3Cgeneral.incubator.apache.org%3E > > > > > > > > > On Tue, Aug 21, 2018 at 10:49 AM, Alan Gates > > wrote: > > > > > > > Which version of the KEYS file did you add it to? I don't see a > change > > > to > > > > the KEYS file in master or the 0.15.0 branch. > > > > > > > > Also, at this point I'm +0 on this release, as the rat check still > > fails, > > > > which I complained about on the last release vote. As indicated by > the > > > +0 > > > > you don't have to fix this to release, but you do to get my vote. :) > > > > > > > > Alan. > > > > > > > > On Mon, Aug 20, 2018 at 10:49 PM Poorna Chandra > > > wrote: > > > > > > > > > +1 > > > > > > > > > > On Mon, Aug 20, 2018 at 11:45 PM James Taylor < > > jamestay...@apache.org> > > > > > wrote: > > > > > > > > > > > Thanks for reviewing, Poorna. Yes, my code signing key has > changed. > > > > I've > > > > > > removed the MD5 file from the source distribution and added my > new > > > code > > > > > > signing key to the KEYS file. > > > > > > > > > > > > James > > > > > > > > > > > > On Sat, Aug 18, 2018 at 7:38 PM, Poorna Chandra < > poo...@apache.org > > > > > > > > wrote: > > > > > > > > > > > > > -1 > > > > > > > > > > > > > > - Checked build and test > > > > > > > - Checked signature and checksums > > > > > > > - Checked LICENSE, NOTICE and DISCLAIMER > > > > > > > - Checked release tag and hash > > > > > > > > > > > > > > A couple of things need to be fixed - > > > > > > > 1. The code signing key is different than what is in the KEYS > > file > > > > and > > > > > > > people.apache.org/keys (BE0F in the KEYS file vs DC24 used to > > > sign). > > > > > Did > > > > > > > your code signing key change? If so, please add it to the KEYS > > > file. > > > > > > > 2. The release distribution policy [1] has been changed to say > > the > > &g
[jira] [Updated] (TEPHRA-296) Prevent tephra-distribution from being included in source release
[ https://issues.apache.org/jira/browse/TEPHRA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-296: Priority: Blocker (was: Major) > Prevent tephra-distribution from being included in source release > - > > Key: TEPHRA-296 > URL: https://issues.apache.org/jira/browse/TEPHRA-296 > Project: Tephra > Issue Type: Improvement > Reporter: James Taylor >Assignee: Poorna Chandra >Priority: Blocker > Fix For: 0.16.0-incubating > > Attachments: TEPHRA-296.patch > > > Since Tephra is only doing a source release, there's no need to include > anything inside of the tephra-distribution directory in the release tar ball. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEPHRA-296) Prevent tephra-distribution from being included in source release
[ https://issues.apache.org/jira/browse/TEPHRA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-296: Fix Version/s: (was: 0.15.0-incubating) 0.16.0-incubating > Prevent tephra-distribution from being included in source release > - > > Key: TEPHRA-296 > URL: https://issues.apache.org/jira/browse/TEPHRA-296 > Project: Tephra > Issue Type: Improvement > Reporter: James Taylor >Assignee: Poorna Chandra >Priority: Major > Fix For: 0.16.0-incubating > > Attachments: TEPHRA-296.patch > > > Since Tephra is only doing a source release, there's no need to include > anything inside of the tephra-distribution directory in the release tar ball. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TEPHRA-296) Prevent tephra-distribution from being included in source release
[ https://issues.apache.org/jira/browse/TEPHRA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16589290#comment-16589290 ] James Taylor commented on TEPHRA-296: - How about for this release, we just do the simple fix of ignoring tehpra-distribution so we can get the release out? Then we can follow up with a new maven profile. > Prevent tephra-distribution from being included in source release > - > > Key: TEPHRA-296 > URL: https://issues.apache.org/jira/browse/TEPHRA-296 > Project: Tephra > Issue Type: Improvement > Reporter: James Taylor >Assignee: Poorna Chandra >Priority: Major > Fix For: 0.15.0-incubating > > Attachments: TEPHRA-296.patch > > > Since Tephra is only doing a source release, there's no need to include > anything inside of the tephra-distribution directory in the release tar ball. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (TEPHRA-296) Prevent tephra-distribution from being included in source release
[ https://issues.apache.org/jira/browse/TEPHRA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16587923#comment-16587923 ] James Taylor edited comment on TEPHRA-296 at 8/21/18 7:50 PM: -- Please review, [~poornachandra]. See email list conversation here[1] for some background. We could alternatively just remove the tephra-distribution directory rather than exclude it as it's not currently needed. [1] [https://lists.apache.org/thread.html/f643e0529e9028b4ff52b00b301601f726e5464debda80051d05afd2@%3Cdev.tephra.apache.org%3E] was (Author: jamestaylor): Please review, [~poornachandra]. See email list conversation here[1] for some background. [1] https://lists.apache.org/thread.html/f643e0529e9028b4ff52b00b301601f726e5464debda80051d05afd2@%3Cdev.tephra.apache.org%3E > Prevent tephra-distribution from being included in source release > - > > Key: TEPHRA-296 > URL: https://issues.apache.org/jira/browse/TEPHRA-296 > Project: Tephra > Issue Type: Improvement > Reporter: James Taylor >Assignee: Poorna Chandra >Priority: Major > Fix For: 0.15.0-incubating > > Attachments: TEPHRA-296.patch > > > Since Tephra is only doing a source release, there's no need to include > anything inside of the tephra-distribution directory in the release tar ball. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEPHRA-296) Prevent tephra-distribution from being included in source release
[ https://issues.apache.org/jira/browse/TEPHRA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-296: Attachment: (was: TEPHRA-296.patch) > Prevent tephra-distribution from being included in source release > - > > Key: TEPHRA-296 > URL: https://issues.apache.org/jira/browse/TEPHRA-296 > Project: Tephra > Issue Type: Improvement > Reporter: James Taylor >Assignee: Poorna Chandra >Priority: Major > Fix For: 0.15.0-incubating > > Attachments: TEPHRA-296.patch > > > Since Tephra is only doing a source release, there's no need to include > anything inside of the tephra-distribution directory in the release tar ball. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEPHRA-296) Prevent tephra-distribution from being included in source release
[ https://issues.apache.org/jira/browse/TEPHRA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-296: Attachment: TEPHRA-296.patch > Prevent tephra-distribution from being included in source release > - > > Key: TEPHRA-296 > URL: https://issues.apache.org/jira/browse/TEPHRA-296 > Project: Tephra > Issue Type: Improvement > Reporter: James Taylor >Assignee: Poorna Chandra >Priority: Major > Fix For: 0.15.0-incubating > > Attachments: TEPHRA-296.patch > > > Since Tephra is only doing a source release, there's no need to include > anything inside of the tephra-distribution directory in the release tar ball. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEPHRA-296) Prevent tephra-distribution from being included in source release
[ https://issues.apache.org/jira/browse/TEPHRA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-296: Fix Version/s: 0.15.0-incubating > Prevent tephra-distribution from being included in source release > - > > Key: TEPHRA-296 > URL: https://issues.apache.org/jira/browse/TEPHRA-296 > Project: Tephra > Issue Type: Improvement > Reporter: James Taylor >Assignee: Poorna Chandra >Priority: Major > Fix For: 0.15.0-incubating > > Attachments: TEPHRA-296.patch > > > Since Tephra is only doing a source release, there's no need to include > anything inside of the tephra-distribution directory in the release tar ball. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TEPHRA-296) Prevent tephra-distribution from being included in source release
[ https://issues.apache.org/jira/browse/TEPHRA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16587923#comment-16587923 ] James Taylor commented on TEPHRA-296: - Please review, [~poornachandra]. See email list conversation here[1] for some background. [1] https://lists.apache.org/thread.html/f643e0529e9028b4ff52b00b301601f726e5464debda80051d05afd2@%3Cdev.tephra.apache.org%3E > Prevent tephra-distribution from being included in source release > - > > Key: TEPHRA-296 > URL: https://issues.apache.org/jira/browse/TEPHRA-296 > Project: Tephra > Issue Type: Improvement > Reporter: James Taylor >Assignee: Poorna Chandra >Priority: Major > Fix For: 0.15.0-incubating > > Attachments: TEPHRA-296.patch > > > Since Tephra is only doing a source release, there's no need to include > anything inside of the tephra-distribution directory in the release tar ball. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEPHRA-296) Prevent tephra-distribution from being included in source release
[ https://issues.apache.org/jira/browse/TEPHRA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-296: Attachment: TEPHRA-296.patch > Prevent tephra-distribution from being included in source release > - > > Key: TEPHRA-296 > URL: https://issues.apache.org/jira/browse/TEPHRA-296 > Project: Tephra > Issue Type: Improvement > Reporter: James Taylor >Assignee: Poorna Chandra >Priority: Major > Attachments: TEPHRA-296.patch > > > Since Tephra is only doing a source release, there's no need to include > anything inside of the tephra-distribution directory in the release tar ball. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (TEPHRA-296) Prevent tephra-distribution from being included in source release
James Taylor created TEPHRA-296: --- Summary: Prevent tephra-distribution from being included in source release Key: TEPHRA-296 URL: https://issues.apache.org/jira/browse/TEPHRA-296 Project: Tephra Issue Type: Improvement Reporter: James Taylor Assignee: Poorna Chandra Since Tephra is only doing a source release, there's no need to include anything inside of the tephra-distribution directory in the release tar ball. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEPHRA-295) Sync KEYS in master with dist.apache.org/repos/dist/dev/incubator/tephra/KEYS
[ https://issues.apache.org/jira/browse/TEPHRA-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-295: Attachment: TEPHRA-295.patch > Sync KEYS in master with dist.apache.org/repos/dist/dev/incubator/tephra/KEYS > - > > Key: TEPHRA-295 > URL: https://issues.apache.org/jira/browse/TEPHRA-295 > Project: Tephra > Issue Type: Improvement > Reporter: James Taylor >Assignee: Poorna Chandra >Priority: Major > Attachments: TEPHRA-295.patch > > > [~alangates] noticed that the KEYS file in master is not in sync with the one > in [https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS.] Should it > be? If yes, please review attached patch, [~poornachandra]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (TEPHRA-295) Sync KEYS in master with dist.apache.org/repos/dist/dev/incubator/tephra/KEYS
James Taylor created TEPHRA-295: --- Summary: Sync KEYS in master with dist.apache.org/repos/dist/dev/incubator/tephra/KEYS Key: TEPHRA-295 URL: https://issues.apache.org/jira/browse/TEPHRA-295 Project: Tephra Issue Type: Improvement Reporter: James Taylor Assignee: Poorna Chandra [~alangates] noticed that the KEYS file in master is not in sync with the one in [https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS.] Should it be? If yes, please review attached patch, [~poornachandra]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: [VOTE] Release of Apache Tephra-0.15.0-incubating [rc1]
Thanks for checking it out, Alan. I checked in my public key info here[1], but I'll commit to master branch as well. Based on Josh's email from prior release vote [2], it looks like the rat check is failing for the following files: apache-tephra-0.14.0-incubating/tephra-distribution/licenses/Aopa.PL apache-tephra-0.14.0-incubating/tephra-distribution/licenses/Asm.BSD apache-tephra-0.14.0-incubating/tephra-distribution/licenses/JLine.BSD apache-tephra-0.14.0-incubating/tephra-distribution/licenses/Logback.EPL apache-tephra-0.14.0-incubating/tephra-distribution/NOTICE_BINARY Since Tephra does a source-only release, I don't think the NOTICE_BINARY is necessary. Same with the licenses - not sure we need those either. We're not including any source code from those projects - those would just be pulled in through maven when built. Thoughts? James [1] https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS [2] https://lists.apache.org/thread.html/fed5c54f775fda7a2e7393095f8d16a7e439e8c51b7b1be7619fd283@%3Cgeneral.incubator.apache.org%3E On Tue, Aug 21, 2018 at 10:49 AM, Alan Gates wrote: > Which version of the KEYS file did you add it to? I don't see a change to > the KEYS file in master or the 0.15.0 branch. > > Also, at this point I'm +0 on this release, as the rat check still fails, > which I complained about on the last release vote. As indicated by the +0 > you don't have to fix this to release, but you do to get my vote. :) > > Alan. > > On Mon, Aug 20, 2018 at 10:49 PM Poorna Chandra wrote: > > > +1 > > > > On Mon, Aug 20, 2018 at 11:45 PM James Taylor > > wrote: > > > > > Thanks for reviewing, Poorna. Yes, my code signing key has changed. > I've > > > removed the MD5 file from the source distribution and added my new code > > > signing key to the KEYS file. > > > > > > James > > > > > > On Sat, Aug 18, 2018 at 7:38 PM, Poorna Chandra > > wrote: > > > > > > > -1 > > > > > > > > - Checked build and test > > > > - Checked signature and checksums > > > > - Checked LICENSE, NOTICE and DISCLAIMER > > > > - Checked release tag and hash > > > > > > > > A couple of things need to be fixed - > > > > 1. The code signing key is different than what is in the KEYS file > and > > > > people.apache.org/keys (BE0F in the KEYS file vs DC24 used to sign). > > Did > > > > your code signing key change? If so, please add it to the KEYS file. > > > > 2. The release distribution policy [1] has been changed to say the > > > release > > > > should not supply MD5 checksum file. > > > > > > > > Thanks, > > > > Poorna > > > > > > > > [1] - https://www.apache.org/dev/release-distribution#sigs-and-sums > > > > > > > > On Thu, Aug 16, 2018 at 11:00 PM, James Taylor < > jamestay...@apache.org > > > > > > > wrote: > > > > > > > > > Hi all, > > > > > > > > > > This is a call for a vote on releasing Apache Tephra > > 0.15.0-incubating, > > > > > release candidate 1. This is the eighth release of Tephra. > > > > > > > > > > The source tarball, including signatures, digests, etc. can be > found > > > at: > > > > > https://dist.apache.org/repos/dist/dev/incubator/tephra/0. > > > > > 15.0-incubating-rc1/src > > > > > > > > > > The tag to be voted upon is v0.15.0-incubating: > > > > > https://git-wip-us.apache.org/repos/asf?p=incubator-tephra. > > > > > git;a=shortlog;h=refs/tags/v0.15.0-incubating > > > > > > > > > > The release hash is fe4885003dfbc8fcfc2d0ae4192a109b03eaebe5: > > > > > https://git-wip-us.apache.org/repos/asf?p=incubator-tephra. > > > > git;a=commit;h= > > > > > fe4885003dfbc8fcfc2d0ae4192a109b03eaebe5 > > > > > > > > > > The Nexus Staging URL: > > > > > > > > https://repository.apache.org/content/repositories/ > orgapachetephra-1012 > > > > > > > > > > Release artifacts are signed with the following key: > > > > > http://people.apache.org/keys/committer/jamestaylor > > > > > > > > > > KEYS file available: > > > > > https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS > > > > > > > > > > For information about the contents of this release, see: > > > > > https://dist.apache.org/repos/dist/dev/incubator/tephra/0. > > > > > 15.0-incubating-rc1/CHANGES.txt > > > > > > > > > > Please vote on releasing this package as Apache Tephra > > > 0.15.0-incubating > > > > > > > > > > The vote will be open for at least 72 hours. > > > > > > > > > > [ ] +1 Release this package as Apache Tephra 0.15.0-incubating > > > > > [ ] +0 no opinion > > > > > [ ] -1 Do not release this package because ... > > > > > > > > > > Thanks, > > > > > James > > > > > > > > > > > > > > >
Re: [VOTE] Release of Apache Tephra-0.15.0-incubating [rc1]
Thanks for reviewing, Poorna. Yes, my code signing key has changed. I've removed the MD5 file from the source distribution and added my new code signing key to the KEYS file. James On Sat, Aug 18, 2018 at 7:38 PM, Poorna Chandra wrote: > -1 > > - Checked build and test > - Checked signature and checksums > - Checked LICENSE, NOTICE and DISCLAIMER > - Checked release tag and hash > > A couple of things need to be fixed - > 1. The code signing key is different than what is in the KEYS file and > people.apache.org/keys (BE0F in the KEYS file vs DC24 used to sign). Did > your code signing key change? If so, please add it to the KEYS file. > 2. The release distribution policy [1] has been changed to say the release > should not supply MD5 checksum file. > > Thanks, > Poorna > > [1] - https://www.apache.org/dev/release-distribution#sigs-and-sums > > On Thu, Aug 16, 2018 at 11:00 PM, James Taylor > wrote: > > > Hi all, > > > > This is a call for a vote on releasing Apache Tephra 0.15.0-incubating, > > release candidate 1. This is the eighth release of Tephra. > > > > The source tarball, including signatures, digests, etc. can be found at: > > https://dist.apache.org/repos/dist/dev/incubator/tephra/0. > > 15.0-incubating-rc1/src > > > > The tag to be voted upon is v0.15.0-incubating: > > https://git-wip-us.apache.org/repos/asf?p=incubator-tephra. > > git;a=shortlog;h=refs/tags/v0.15.0-incubating > > > > The release hash is fe4885003dfbc8fcfc2d0ae4192a109b03eaebe5: > > https://git-wip-us.apache.org/repos/asf?p=incubator-tephra. > git;a=commit;h= > > fe4885003dfbc8fcfc2d0ae4192a109b03eaebe5 > > > > The Nexus Staging URL: > > https://repository.apache.org/content/repositories/orgapachetephra-1012 > > > > Release artifacts are signed with the following key: > > http://people.apache.org/keys/committer/jamestaylor > > > > KEYS file available: > > https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS > > > > For information about the contents of this release, see: > > https://dist.apache.org/repos/dist/dev/incubator/tephra/0. > > 15.0-incubating-rc1/CHANGES.txt > > > > Please vote on releasing this package as Apache Tephra 0.15.0-incubating > > > > The vote will be open for at least 72 hours. > > > > [ ] +1 Release this package as Apache Tephra 0.15.0-incubating > > [ ] +0 no opinion > > [ ] -1 Do not release this package because ... > > > > Thanks, > > James > > >
[VOTE] Release of Apache Tephra-0.15.0-incubating [rc1]
Hi all, This is a call for a vote on releasing Apache Tephra 0.15.0-incubating, release candidate 1. This is the eighth release of Tephra. The source tarball, including signatures, digests, etc. can be found at: https://dist.apache.org/repos/dist/dev/incubator/tephra/0.15.0-incubating-rc1/src The tag to be voted upon is v0.15.0-incubating: https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=shortlog;h=refs/tags/v0.15.0-incubating The release hash is fe4885003dfbc8fcfc2d0ae4192a109b03eaebe5: https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=commit;h=fe4885003dfbc8fcfc2d0ae4192a109b03eaebe5 The Nexus Staging URL: https://repository.apache.org/content/repositories/orgapachetephra-1012 Release artifacts are signed with the following key: http://people.apache.org/keys/committer/jamestaylor KEYS file available: https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS For information about the contents of this release, see: https://dist.apache.org/repos/dist/dev/incubator/tephra/0.15.0-incubating-rc1/CHANGES.txt Please vote on releasing this package as Apache Tephra 0.15.0-incubating The vote will be open for at least 72 hours. [ ] +1 Release this package as Apache Tephra 0.15.0-incubating [ ] +0 no opinion [ ] -1 Do not release this package because ... Thanks, James
[jira] [Updated] (TEPHRA-264) When transaction size limits are exceeded, the error message should indicate what configuration to change in order to increase the limit
[ https://issues.apache.org/jira/browse/TEPHRA-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-264: Fix Version/s: (was: 0.15.0-incubating) 0.16.0-incubating > When transaction size limits are exceeded, the error message should indicate > what configuration to change in order to increase the limit > > > Key: TEPHRA-264 > URL: https://issues.apache.org/jira/browse/TEPHRA-264 > Project: Tephra > Issue Type: Improvement > Components: core >Affects Versions: 0.13.0-incubating >Reporter: Andreas Neumann >Assignee: Andreas Neumann >Priority: Major > Fix For: 0.16.0-incubating > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEPHRA-204) Document invalid transaction list pruning
[ https://issues.apache.org/jira/browse/TEPHRA-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-204: Fix Version/s: (was: 0.15.0-incubating) 0.16.0-incubating > Document invalid transaction list pruning > - > > Key: TEPHRA-204 > URL: https://issues.apache.org/jira/browse/TEPHRA-204 > Project: Tephra > Issue Type: Sub-task >Reporter: Poorna Chandra >Assignee: Poorna Chandra >Priority: Major > Fix For: 0.16.0-incubating > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEPHRA-269) Protect the Transaction Manager against misconfigured clients using rate limits
[ https://issues.apache.org/jira/browse/TEPHRA-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-269: Fix Version/s: (was: 0.15.0-incubating) 0.16.0-incubating > Protect the Transaction Manager against misconfigured clients using rate > limits > --- > > Key: TEPHRA-269 > URL: https://issues.apache.org/jira/browse/TEPHRA-269 > Project: Tephra > Issue Type: New Feature > Components: core >Reporter: Poorna Chandra >Assignee: Poorna Chandra >Priority: Major > Fix For: 0.16.0-incubating > > Attachments: Ensure QoS in Transaction Manager by rate limiting > client requests.pdf > > > We have seen cases where misconfigured clients can overwhelm the system by > making expensive requests (like invalidating transactions). By the time > admins figure out there is a misconfigured client and take corrective action, > thousands of invalid transactions can be created in a very short period of > time. It would be useful to have a way to limit the number of invalid > transactions that a client can create in given time. > I'll send out a design document for this soon. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEPHRA-265) Tephra Guice License
[ https://issues.apache.org/jira/browse/TEPHRA-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-265: Fix Version/s: (was: 0.15.0-incubating) 0.16.0-incubating > Tephra Guice License > > > Key: TEPHRA-265 > URL: https://issues.apache.org/jira/browse/TEPHRA-265 > Project: Tephra > Issue Type: Bug >Affects Versions: 0.13.0-incubating >Reporter: Gokul Gunasekaran >Assignee: Gokul Gunasekaran >Priority: Major > Fix For: 0.16.0-incubating > > > The NOTICE for Guice in 0.13.0-incubating release contains (which was added > as part of the fix for TEPHRA-231): > Apache Tephra includes Guice v3.0 and Guice Assisted Inject v3.0. Tephra > elects to include this software in this distribution under the Apache License. > You can obtain a copy of the License at: > http://apache.org/licenses/LICENSE-2.0 > Instead, it should contain the exact content from the NOTICE of the Guice > JAR. > Google Guice - Core Library > Copyright 2006-2011 Google, Inc. > This product includes software developed at > The Apache Software Foundation (http://www.apache.org/). > http://mail-archives.apache.org/mod_mbox/incubator-general/201709.mbox/%3CCAOqetn-zPeOanD1fVZHVsjfwqn5qnmN9WXWjb1jDJAE8JgQ_Zg%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEPHRA-283) Skip install step of travis
[ https://issues.apache.org/jira/browse/TEPHRA-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-283: Fix Version/s: (was: 0.15.0-incubating) 0.14.0-incubating > Skip install step of travis > --- > > Key: TEPHRA-283 > URL: https://issues.apache.org/jira/browse/TEPHRA-283 > Project: Tephra > Issue Type: Bug >Reporter: Ankit Singhal >Assignee: Ankit Singhal >Priority: Major > Fix For: 0.14.0-incubating > > > we can skip installation step of travis as it will unnecessarily run "mvn > install" for all the modules for every job. > This is also needed where we need to exclude to some modules from jdk7 build -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: [DISCUSS] start vote for 0.15.0-incubating release
If someone could create an 0.16.0-incubating tag in JIRA so I could move the unresolved JIRAs there, that'd be much appreciated. Also, looks like JIRA thinks 0.14.0-incubating was never released - would be good to update that as well. Thanks, James On Tue, Aug 14, 2018 at 12:02 AM, Poorna Chandra wrote: > Sounds good, James. I have no objections. > > Thanks, > Poorna > > > > On Sun, Aug 12, 2018 at 9:11 PM, James Taylor > wrote: > > > I'd like to do an 0.15.0-incubating release as it has a few fixes we need > > for Phoenix: TEPHRA-294 which completes some unfinished work to replace > > HTableInterface with Table for 1.3 and 1.4 compat modules; TEPHRA-292 > which > > increases (and makes configurable) a timeout to prevent tests in Phoenix > > from flapping; and TEPHRA-291 to fix the NOTICE file copyright. > > > > Any objections on me starting a vote? > > > > Thanks, > > James > > >
[jira] [Commented] (TEPHRA-283) Skip install step of travis
[ https://issues.apache.org/jira/browse/TEPHRA-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16581222#comment-16581222 ] James Taylor commented on TEPHRA-283: - Was this ever completed, [~an...@apache.org]? If so, please resolve it. > Skip install step of travis > --- > > Key: TEPHRA-283 > URL: https://issues.apache.org/jira/browse/TEPHRA-283 > Project: Tephra > Issue Type: Bug >Reporter: Ankit Singhal >Assignee: Ankit Singhal >Priority: Major > Fix For: 0.15.0-incubating > > > we can skip installation step of travis as it will unnecessarily run "mvn > install" for all the modules for every job. > This is also needed where we need to exclude to some modules from jdk7 build -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (TEPHRA-268) Replace usage of all HBase deprecated APIs
[ https://issues.apache.org/jira/browse/TEPHRA-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved TEPHRA-268. - Resolution: Fixed Fixed as part of TEPHRA-272. > Replace usage of all HBase deprecated APIs > -- > > Key: TEPHRA-268 > URL: https://issues.apache.org/jira/browse/TEPHRA-268 > Project: Tephra > Issue Type: Bug > Reporter: James Taylor >Assignee: Ankit Singhal >Priority: Major > Labels: HBase-2.0 > Fix For: 0.14.0-incubating > > > Tephra still uses many deprecated APIs in HBase. Until this is changed, > Tephra won't work on HBase 2.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEPHRA-268) Replace usage of all HBase deprecated APIs
[ https://issues.apache.org/jira/browse/TEPHRA-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-268: Fix Version/s: (was: 0.15.0-incubating) 0.14.0-incubating > Replace usage of all HBase deprecated APIs > -- > > Key: TEPHRA-268 > URL: https://issues.apache.org/jira/browse/TEPHRA-268 > Project: Tephra > Issue Type: Bug > Reporter: James Taylor >Assignee: Ankit Singhal >Priority: Major > Labels: HBase-2.0 > Fix For: 0.14.0-incubating > > > Tephra still uses many deprecated APIs in HBase. Until this is changed, > Tephra won't work on HBase 2.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (TEPHRA-284) Fix tephra compat dependency in tephra example module for HBase 1.4
[ https://issues.apache.org/jira/browse/TEPHRA-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor closed TEPHRA-284. --- Resolution: Duplicate Fixed as part of TEPHRA-294 > Fix tephra compat dependency in tephra example module for HBase 1.4 > --- > > Key: TEPHRA-284 > URL: https://issues.apache.org/jira/browse/TEPHRA-284 > Project: Tephra > Issue Type: Bug >Affects Versions: 0.14.0-incubating >Reporter: Ankit Singhal >Assignee: Ankit Singhal >Priority: Major > Fix For: 0.15.0-incubating > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (TEPHRA-294) Update TransactionAwareTable to implement interface of Table for 1.3 and 1.4
[ https://issues.apache.org/jira/browse/TEPHRA-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved TEPHRA-294. - Resolution: Fixed > Update TransactionAwareTable to implement interface of Table for 1.3 and 1.4 > > > Key: TEPHRA-294 > URL: https://issues.apache.org/jira/browse/TEPHRA-294 > Project: Tephra > Issue Type: Improvement > Reporter: James Taylor > Assignee: James Taylor >Priority: Major > Fix For: 0.15.0-incubating > > Attachments: TEPHRA-294.patch > > > Remove use of HTableInterface in 1.3 and 1.4 compat module -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (TEPHRA-291) Notice file is outdated
[ https://issues.apache.org/jira/browse/TEPHRA-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor closed TEPHRA-291. --- Resolution: Fixed Assignee: James Taylor (was: Poorna Chandra) > Notice file is outdated > --- > > Key: TEPHRA-291 > URL: https://issues.apache.org/jira/browse/TEPHRA-291 > Project: Tephra > Issue Type: Bug >Affects Versions: 0.13.0-incubating >Reporter: Andreas Neumann >Assignee: James Taylor >Priority: Blocker > Fix For: 0.15.0-incubating > > Attachments: TEPHRA-291.patch, TEPHRA-291_v2.patch > > > It still states a copyright 2016, when it should be updated to 2016-2018. > Making this a blocker for 0.15 so that it cannot slip through the cracks. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TEPHRA-291) Notice file is outdated
[ https://issues.apache.org/jira/browse/TEPHRA-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16580743#comment-16580743 ] James Taylor commented on TEPHRA-291: - This one look ok, [~poornachandra]? > Notice file is outdated > --- > > Key: TEPHRA-291 > URL: https://issues.apache.org/jira/browse/TEPHRA-291 > Project: Tephra > Issue Type: Bug >Affects Versions: 0.13.0-incubating >Reporter: Andreas Neumann >Assignee: Poorna Chandra >Priority: Blocker > Fix For: 0.15.0-incubating > > Attachments: TEPHRA-291.patch, TEPHRA-291_v2.patch > > > It still states a copyright 2016, when it should be updated to 2016-2018. > Making this a blocker for 0.15 so that it cannot slip through the cracks. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[DISCUSS] start vote for 0.15.0-incubating release
I'd like to do an 0.15.0-incubating release as it has a few fixes we need for Phoenix: TEPHRA-294 which completes some unfinished work to replace HTableInterface with Table for 1.3 and 1.4 compat modules; TEPHRA-292 which increases (and makes configurable) a timeout to prevent tests in Phoenix from flapping; and TEPHRA-291 to fix the NOTICE file copyright. Any objections on me starting a vote? Thanks, James
[jira] [Commented] (TEPHRA-291) Notice file is outdated
[ https://issues.apache.org/jira/browse/TEPHRA-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16577807#comment-16577807 ] James Taylor commented on TEPHRA-291: - Please review the v2 patch, [~anew]. > Notice file is outdated > --- > > Key: TEPHRA-291 > URL: https://issues.apache.org/jira/browse/TEPHRA-291 > Project: Tephra > Issue Type: Bug >Affects Versions: 0.13.0-incubating >Reporter: Andreas Neumann >Assignee: Poorna Chandra >Priority: Blocker > Fix For: 0.15.0-incubating > > Attachments: TEPHRA-291.patch, TEPHRA-291_v2.patch > > > It still states a copyright 2016, when it should be updated to 2016-2018. > Making this a blocker for 0.15 so that it cannot slip through the cracks. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEPHRA-291) Notice file is outdated
[ https://issues.apache.org/jira/browse/TEPHRA-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-291: Attachment: TEPHRA-291_v2.patch > Notice file is outdated > --- > > Key: TEPHRA-291 > URL: https://issues.apache.org/jira/browse/TEPHRA-291 > Project: Tephra > Issue Type: Bug >Affects Versions: 0.13.0-incubating >Reporter: Andreas Neumann >Assignee: Poorna Chandra >Priority: Blocker > Fix For: 0.15.0-incubating > > Attachments: TEPHRA-291.patch, TEPHRA-291_v2.patch > > > It still states a copyright 2016, when it should be updated to 2016-2018. > Making this a blocker for 0.15 so that it cannot slip through the cracks. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TEPHRA-294) Update TransactionAwareTable to implement interface of Table for 1.3 and 1.4
[ https://issues.apache.org/jira/browse/TEPHRA-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16577801#comment-16577801 ] James Taylor commented on TEPHRA-294: - Please review, [~poornachandra]. > Update TransactionAwareTable to implement interface of Table for 1.3 and 1.4 > > > Key: TEPHRA-294 > URL: https://issues.apache.org/jira/browse/TEPHRA-294 > Project: Tephra > Issue Type: Improvement > Reporter: James Taylor > Assignee: James Taylor >Priority: Major > Fix For: 0.15.0-incubating > > Attachments: TEPHRA-294.patch > > > Remove use of HTableInterface in 1.3 and 1.4 compat module -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEPHRA-294) Update TransactionAwareTable to implement interface of Table for 1.3 and 1.4
[ https://issues.apache.org/jira/browse/TEPHRA-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-294: Attachment: TEPHRA-294.patch > Update TransactionAwareTable to implement interface of Table for 1.3 and 1.4 > > > Key: TEPHRA-294 > URL: https://issues.apache.org/jira/browse/TEPHRA-294 > Project: Tephra > Issue Type: Improvement > Reporter: James Taylor > Assignee: James Taylor >Priority: Major > Fix For: 0.15.0-incubating > > Attachments: TEPHRA-294.patch > > > Remove use of HTableInterface in 1.3 and 1.4 compat module -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEPHRA-294) Update TransactionAwareTable to implement interface of Table for 1.3 and 1.4
[ https://issues.apache.org/jira/browse/TEPHRA-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-294: Attachment: (was: TEPHRA-294.patch) > Update TransactionAwareTable to implement interface of Table for 1.3 and 1.4 > > > Key: TEPHRA-294 > URL: https://issues.apache.org/jira/browse/TEPHRA-294 > Project: Tephra > Issue Type: Improvement > Reporter: James Taylor > Assignee: James Taylor >Priority: Major > Fix For: 0.15.0-incubating > > Attachments: TEPHRA-294.patch > > > Remove use of HTableInterface in 1.3 and 1.4 compat module -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEPHRA-294) Update TransactionAwareTable to implement interface of Table for 1.3 and 1.4
[ https://issues.apache.org/jira/browse/TEPHRA-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-294: Attachment: TEPHRA-294.patch > Update TransactionAwareTable to implement interface of Table for 1.3 and 1.4 > > > Key: TEPHRA-294 > URL: https://issues.apache.org/jira/browse/TEPHRA-294 > Project: Tephra > Issue Type: Improvement > Reporter: James Taylor > Assignee: James Taylor >Priority: Major > Fix For: 0.15.0-incubating > > Attachments: TEPHRA-294.patch > > > Remove use of HTableInterface in 1.3 and 1.4 compat module -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEPHRA-294) Update TransactionAwareTable to implement interface of Table for 1.3 and 1.4
[ https://issues.apache.org/jira/browse/TEPHRA-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-294: Fix Version/s: 0.15.0-incubating > Update TransactionAwareTable to implement interface of Table for 1.3 and 1.4 > > > Key: TEPHRA-294 > URL: https://issues.apache.org/jira/browse/TEPHRA-294 > Project: Tephra > Issue Type: Improvement > Reporter: James Taylor > Assignee: James Taylor >Priority: Major > Fix For: 0.15.0-incubating > > > Remove use of HTableInterface in 1.3 and 1.4 compat module -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (TEPHRA-294) Update TransactionAwareTable to implement interface of Table for 1.3 and 1.4
James Taylor created TEPHRA-294: --- Summary: Update TransactionAwareTable to implement interface of Table for 1.3 and 1.4 Key: TEPHRA-294 URL: https://issues.apache.org/jira/browse/TEPHRA-294 Project: Tephra Issue Type: Improvement Reporter: James Taylor Assignee: James Taylor Remove use of HTableInterface in 1.3 and 1.4 compat module -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (TEPHRA-292) Make client discovery timeout higher and configurable
[ https://issues.apache.org/jira/browse/TEPHRA-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved TEPHRA-292. - Resolution: Fixed > Make client discovery timeout higher and configurable > - > > Key: TEPHRA-292 > URL: https://issues.apache.org/jira/browse/TEPHRA-292 > Project: Tephra > Issue Type: Bug > Reporter: James Taylor > Assignee: James Taylor >Priority: Major > Fix For: 0.15.0-incubating > > Attachments: TEPHRA-292.patch > > > Many of the Phoenix transaction tests have intermittent failures due to the > client discovery timeout being too short. We should make the default higher > and make the setting configurable. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEPHRA-292) Make client discovery timeout higher and configurable
[ https://issues.apache.org/jira/browse/TEPHRA-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-292: Attachment: TEPHRA-292.patch > Make client discovery timeout higher and configurable > - > > Key: TEPHRA-292 > URL: https://issues.apache.org/jira/browse/TEPHRA-292 > Project: Tephra > Issue Type: Bug > Reporter: James Taylor > Assignee: James Taylor >Priority: Major > Fix For: 0.15.0-incubating > > Attachments: TEPHRA-292.patch > > > Many of the Phoenix transaction tests have intermittent failures due to the > client discovery timeout being too short. We should make the default higher > and make the setting configurable. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TEPHRA-292) Make client discovery timeout higher and configurable
[ https://issues.apache.org/jira/browse/TEPHRA-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16514206#comment-16514206 ] James Taylor commented on TEPHRA-292: - Please review, [~poornachandra] or others. > Make client discovery timeout higher and configurable > - > > Key: TEPHRA-292 > URL: https://issues.apache.org/jira/browse/TEPHRA-292 > Project: Tephra > Issue Type: Bug > Reporter: James Taylor > Assignee: James Taylor >Priority: Major > Fix For: 0.15.0-incubating > > Attachments: TEPHRA-292.patch > > > Many of the Phoenix transaction tests have intermittent failures due to the > client discovery timeout being too short. We should make the default higher > and make the setting configurable. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEPHRA-292) Make client discovery timeout higher and configurable
[ https://issues.apache.org/jira/browse/TEPHRA-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-292: Description: Many of the Phoenix transaction tests have intermittent failures due to the client discovery timeout being too short. We should make the default higher and make the setting configurable. (was: Many of the Phoenix transaction tests are failing due to the client discovery timeout being too short. We should make the default higher and make the setting configurable.) > Make client discovery timeout higher and configurable > - > > Key: TEPHRA-292 > URL: https://issues.apache.org/jira/browse/TEPHRA-292 > Project: Tephra > Issue Type: Bug > Reporter: James Taylor > Assignee: James Taylor >Priority: Major > Fix For: 0.15.0-incubating > > > Many of the Phoenix transaction tests have intermittent failures due to the > client discovery timeout being too short. We should make the default higher > and make the setting configurable. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (TEPHRA-292) Make client discovery timeout higher and configurable
James Taylor created TEPHRA-292: --- Summary: Make client discovery timeout higher and configurable Key: TEPHRA-292 URL: https://issues.apache.org/jira/browse/TEPHRA-292 Project: Tephra Issue Type: Bug Reporter: James Taylor Assignee: James Taylor Fix For: 0.15.0-incubating Many of the Phoenix transaction tests are failing due to the client discovery timeout being too short. We should make the default higher and make the setting configurable. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Proposed incubator podling report for June 2018
How about adding mention of 0.14.0 release under the “How has the project developed since the last report?” section? On Tue, Jun 5, 2018 at 5:36 PM Andreas Neumann wrote: > Hi All, > > Please review the draft of the incubator reportand let me know if any > changes are needed. I will otherwise add it to the wiki tomorrow (which is > the due date). > > Thanks, -Andreas > > > Tephra > > Tephra is a system for providing globally consistent transactions on top of > Apache HBase and other storage engines. > > Tephra has been incubating since 2016-03-07. > > Two most important issues to address in the move towards graduation: > > 1. Improve community engagement > 2. Increase adoption > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be > aware of? > > - None at this time. > > How has the community developed since the last report? > > - 7 new JIRAs filed since the last report > > How has the project developed since the last report? > > - Working on 0.15.0-incubating release > - Added support for HBase 2.0 (new major version of HBase) > > How would you assess the podling's maturity? > Please feel free to add your own commentary. > > [ ] Initial setup > [ ] Working towards first release > [x] Community building > [ ] Nearing graduation > [ ] Other: > > Date of last release: > > 2018-05-30 > > When were the last committers or PPMC members elected? > > - None since coming to incubation > > Signed-off-by: > > [ ](tephra) Alan Gates > Comments: > [ ](tephra) Andrew Purtell > Comments: > [ ](tephra) James Taylor > Comments: > [ ](tephra) Lars Hofhansl > Comments: > > IPMC/Shepherd notes: >
[ANNOUNCE] Apache Tephra-0.14.0-incubating released
Hi All, The Apache Tephra team is excited to announce the latest release of Apache Tephra-0.14.0-incubating. This is the seventh release of Apache Tephra. Apache Tephra is a transaction engine for distributed data stores like Apache HBase. It provides ACID semantics for concurrent data operations that span over region boundaries in HBase using Optimistic Concurrency Control. The release artifacts are available at http://www.apache.org/dyn/closer.cgi/incubator/tephra/0.14.0-incubating/src Maven artifacts have also been made available on repository.apache.org. We would like to thank all the contributors that made this release possible. Thanks, The Apache Tephra (incubating) Team = *Disclaimer* Apache Tephra is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the name of Apache Incubator PMC. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.
[jira] [Commented] (TEPHRA-291) Notice file is outdated
[ https://issues.apache.org/jira/browse/TEPHRA-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483285#comment-16483285 ] James Taylor commented on TEPHRA-291: - Not sure, but I don't think I've seen that in other projects. > Notice file is outdated > --- > > Key: TEPHRA-291 > URL: https://issues.apache.org/jira/browse/TEPHRA-291 > Project: Tephra > Issue Type: Bug >Affects Versions: 0.13.0-incubating >Reporter: Andreas Neumann >Assignee: Poorna Chandra >Priority: Blocker > Fix For: 0.15.0-incubating > > Attachments: TEPHRA-291.patch > > > It still states a copyright 2016, when it should be updated to 2016-2018. > Making this a blocker for 0.15 so that it cannot slip through the cracks. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEPHRA-291) Notice file is outdated
[ https://issues.apache.org/jira/browse/TEPHRA-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-291: Attachment: TEPHRA-291.patch > Notice file is outdated > --- > > Key: TEPHRA-291 > URL: https://issues.apache.org/jira/browse/TEPHRA-291 > Project: Tephra > Issue Type: Bug >Affects Versions: 0.13.0-incubating >Reporter: Andreas Neumann >Assignee: Poorna Chandra >Priority: Blocker > Fix For: 0.15.0-incubating > > Attachments: TEPHRA-291.patch > > > It still states a copyright 2016, when it should be updated to 2016-2018. > Making this a blocker for 0.15 so that it cannot slip through the cracks. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TEPHRA-291) Notice file is outdated
[ https://issues.apache.org/jira/browse/TEPHRA-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483166#comment-16483166 ] James Taylor commented on TEPHRA-291: - Please review patch, [~anew]. > Notice file is outdated > --- > > Key: TEPHRA-291 > URL: https://issues.apache.org/jira/browse/TEPHRA-291 > Project: Tephra > Issue Type: Bug >Affects Versions: 0.13.0-incubating >Reporter: Andreas Neumann >Assignee: Poorna Chandra >Priority: Blocker > Fix For: 0.15.0-incubating > > Attachments: TEPHRA-291.patch > > > It still states a copyright 2016, when it should be updated to 2016-2018. > Making this a blocker for 0.15 so that it cannot slip through the cracks. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[RESULT][VOTE] Release of Apache Tephra-0.14.0-incubating [rc1]
The vote is now closed and passes with 3 +1 votes and no +0 or -1 votes. I'll start the vote on the general list now. Thanks, James On Mon, May 21, 2018 at 3:17 PM, James Taylor <jamestay...@apache.org> wrote: > +1 > > On Mon, May 21, 2018 at 8:45 AM, Andreas Neumann <a...@apache.org> wrote: > >> OK sounds like a plan. >> >> +1 >> >> -Andreas >> >> On Mon, May 21, 2018 at 8:35 AM, James Taylor <jamestay...@apache.org> >> wrote: >> >> > I think that’s a small enough thing that it should be fine for this >> > release. Would be good to file a JIRA so it's remembered for the next >> > release. >> > >> > On Mon, May 21, 2018 at 7:42 AM Andreas Neumann <a...@apache.org> >> wrote: >> > >> > > Thanks for updating the KEYS. >> > > >> > > - validated all checksums >> > > - ran build and tests >> > > - checked LICENSE, NOTICE and DISCLAIMER >> > > >> > > My only concern is that the NOTICE still states "Copyright 2016". I am >> > not >> > > sure whether that is serious enough to hold the release? I do remember >> > that >> > > this has been brought up in previous releases. >> > > Opinions? >> > > >> > > Thanks -Andreas. >> > > >> > > >> > > On Mon, May 21, 2018 at 7:06 AM, Poorna Chandra <poo...@apache.org> >> > wrote: >> > > >> > > > +1 >> > > > >> > > > - Checked build and test >> > > > - Checked signature and checksums >> > > > - Checked LICENSE, NOTICE and DISCLAIMER >> > > > - Checked release tag and hash >> > > > >> > > > Thanks, >> > > > Poorna. >> > > > >> > > > >> > > > On Fri, May 18, 2018 at 11:35 PM, James Taylor < >> jamestay...@apache.org >> > > >> > > > wrote: >> > > > >> > > > > I've added my PGP public key to >> > > > > https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS. >> > > Artifacts >> > > > > are >> > > > > signed with my "CODE SIGNING KEY": 308FBEE06088BE0F. Sorry for any >> > > > > confusion. >> > > > > >> > > > > On Fri, May 18, 2018 at 4:02 PM, Andreas Neumann <a...@apache.org >> > >> > > > wrote: >> > > > > >> > > > > > +0 >> > > > > > >> > > > > > - sha512 checksum matcnes >> > > > > > - md5 checksum matches >> > > > > > - I cannot verify the signature because the KEYS file does not >> seem >> > > to >> > > > > > contain your public key. Can you add your keys to it? >> > > > > > >> > > > > > Also, I am surprised that in Changes.txt, HBase-1.4 support is >> > listed >> > > > as >> > > > > a >> > > > > > new feature, whereas HBase-2.0 support is merely an improvement >> :) >> > > > > > >> > > > > > Best -Andreas >> > > > > > >> > > > > > On Fri, May 18, 2018 at 2:10 PM, James Taylor < >> > > jamestay...@apache.org> >> > > > > > wrote: >> > > > > > >> > > > > > > Hi all, >> > > > > > > >> > > > > > > This is a call for a vote on releasing Apache Tephra >> > > > 0.14.0-incubating, >> > > > > > > release candidate 1. This is the seventh release of Tephra. >> > > > > > > >> > > > > > > The source tarball, including signatures, digests, etc. can be >> > > found >> > > > > at: >> > > > > > > https://dist.apache.org/repos/dist/dev/incubator/tephra/0. >> > > > > > 14.0-incubating >> > > > > > > -rc1/src >> > > > > > > >> > > > > > > The tag to be voted upon is v0.14.0-incubating: >> > > > > > > https://git-wip-us.apache.org/repos/asf?p=incubator-tephra. >> > > > > > > git;a=shortlog;h=refs/tags/v >> > > > > > > 0.14.0-incubating >> > > > > > > >> > > > > > > The release hash is e93942adae0ece286157a8f6a2e5c63b53669e03: >> > > > > > > https://git-wip-us.apache.org/repos/asf?p=incubator-tephra. >> > > > > > git;a=commit;h= >> > > > > > > e93942adae0ece286157a8f6a2e5c63b53669e03 >> > > > > > > >> > > > > > > The Nexus Staging URL: >> > > > > > > >> > > > > https://repository.apache.org/content/repositories/ >> > > orgapachetephra-1011 >> > > > > > > >> > > > > > > Release artifacts are signed with the following key: >> > > > > > > http://people.apache.org/keys/committer/jamestaylor >> > > > > > > >> > > > > > > KEYS file available: >> > > > > > > https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS >> > > > > > > >> > > > > > > For information about the contents of this release, see: >> > > > > > > https://dist.apache.org/repos/dist/dev/incubator/tephra/0. >> > > > > > > 14.0-incubating-rc1/CHANGES.txt >> > > > > > > >> > > > > > > Please vote on releasing this package as Apache Tephra >> > > > > 0.14.0-incubating >> > > > > > > >> > > > > > > The vote will be open for 72 hours. >> > > > > > > >> > > > > > > [ ] +1 Release this package as Apache Tephra 0.14.0-incubating >> > > > > > > [ ] +0 no opinion >> > > > > > > [ ] -1 Do not release this package because ... >> > > > > > > >> > > > > > > Thanks, >> > > > > > > James >> > > > > > > >> > > > > > >> > > > > >> > > > >> > > >> > >> > >
Re: [VOTE] Release of Apache Tephra-0.14.0-incubating [rc1]
+1 On Mon, May 21, 2018 at 8:45 AM, Andreas Neumann <a...@apache.org> wrote: > OK sounds like a plan. > > +1 > > -Andreas > > On Mon, May 21, 2018 at 8:35 AM, James Taylor <jamestay...@apache.org> > wrote: > > > I think that’s a small enough thing that it should be fine for this > > release. Would be good to file a JIRA so it's remembered for the next > > release. > > > > On Mon, May 21, 2018 at 7:42 AM Andreas Neumann <a...@apache.org> wrote: > > > > > Thanks for updating the KEYS. > > > > > > - validated all checksums > > > - ran build and tests > > > - checked LICENSE, NOTICE and DISCLAIMER > > > > > > My only concern is that the NOTICE still states "Copyright 2016". I am > > not > > > sure whether that is serious enough to hold the release? I do remember > > that > > > this has been brought up in previous releases. > > > Opinions? > > > > > > Thanks -Andreas. > > > > > > > > > On Mon, May 21, 2018 at 7:06 AM, Poorna Chandra <poo...@apache.org> > > wrote: > > > > > > > +1 > > > > > > > > - Checked build and test > > > > - Checked signature and checksums > > > > - Checked LICENSE, NOTICE and DISCLAIMER > > > > - Checked release tag and hash > > > > > > > > Thanks, > > > > Poorna. > > > > > > > > > > > > On Fri, May 18, 2018 at 11:35 PM, James Taylor < > jamestay...@apache.org > > > > > > > wrote: > > > > > > > > > I've added my PGP public key to > > > > > https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS. > > > Artifacts > > > > > are > > > > > signed with my "CODE SIGNING KEY": 308FBEE06088BE0F. Sorry for any > > > > > confusion. > > > > > > > > > > On Fri, May 18, 2018 at 4:02 PM, Andreas Neumann <a...@apache.org> > > > > wrote: > > > > > > > > > > > +0 > > > > > > > > > > > > - sha512 checksum matcnes > > > > > > - md5 checksum matches > > > > > > - I cannot verify the signature because the KEYS file does not > seem > > > to > > > > > > contain your public key. Can you add your keys to it? > > > > > > > > > > > > Also, I am surprised that in Changes.txt, HBase-1.4 support is > > listed > > > > as > > > > > a > > > > > > new feature, whereas HBase-2.0 support is merely an improvement > :) > > > > > > > > > > > > Best -Andreas > > > > > > > > > > > > On Fri, May 18, 2018 at 2:10 PM, James Taylor < > > > jamestay...@apache.org> > > > > > > wrote: > > > > > > > > > > > > > Hi all, > > > > > > > > > > > > > > This is a call for a vote on releasing Apache Tephra > > > > 0.14.0-incubating, > > > > > > > release candidate 1. This is the seventh release of Tephra. > > > > > > > > > > > > > > The source tarball, including signatures, digests, etc. can be > > > found > > > > > at: > > > > > > > https://dist.apache.org/repos/dist/dev/incubator/tephra/0. > > > > > > 14.0-incubating > > > > > > > -rc1/src > > > > > > > > > > > > > > The tag to be voted upon is v0.14.0-incubating: > > > > > > > https://git-wip-us.apache.org/repos/asf?p=incubator-tephra. > > > > > > > git;a=shortlog;h=refs/tags/v > > > > > > > 0.14.0-incubating > > > > > > > > > > > > > > The release hash is e93942adae0ece286157a8f6a2e5c63b53669e03: > > > > > > > https://git-wip-us.apache.org/repos/asf?p=incubator-tephra. > > > > > > git;a=commit;h= > > > > > > > e93942adae0ece286157a8f6a2e5c63b53669e03 > > > > > > > > > > > > > > The Nexus Staging URL: > > > > > > > > > > > > https://repository.apache.org/content/repositories/ > > > orgapachetephra-1011 > > > > > > > > > > > > > > Release artifacts are signed with the following key: > > > > > > > http://people.apache.org/keys/committer/jamestaylor > > > > > > > > > > > > > > KEYS file available: > > > > > > > https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS > > > > > > > > > > > > > > For information about the contents of this release, see: > > > > > > > https://dist.apache.org/repos/dist/dev/incubator/tephra/0. > > > > > > > 14.0-incubating-rc1/CHANGES.txt > > > > > > > > > > > > > > Please vote on releasing this package as Apache Tephra > > > > > 0.14.0-incubating > > > > > > > > > > > > > > The vote will be open for 72 hours. > > > > > > > > > > > > > > [ ] +1 Release this package as Apache Tephra 0.14.0-incubating > > > > > > > [ ] +0 no opinion > > > > > > > [ ] -1 Do not release this package because ... > > > > > > > > > > > > > > Thanks, > > > > > > > James > > > > > > > > > > > > > > > > > > > > > > > > > > > >
Re: [VOTE] Release of Apache Tephra-0.14.0-incubating [rc1]
I think that’s a small enough thing that it should be fine for this release. Would be good to file a JIRA so it's remembered for the next release. On Mon, May 21, 2018 at 7:42 AM Andreas Neumann <a...@apache.org> wrote: > Thanks for updating the KEYS. > > - validated all checksums > - ran build and tests > - checked LICENSE, NOTICE and DISCLAIMER > > My only concern is that the NOTICE still states "Copyright 2016". I am not > sure whether that is serious enough to hold the release? I do remember that > this has been brought up in previous releases. > Opinions? > > Thanks -Andreas. > > > On Mon, May 21, 2018 at 7:06 AM, Poorna Chandra <poo...@apache.org> wrote: > > > +1 > > > > - Checked build and test > > - Checked signature and checksums > > - Checked LICENSE, NOTICE and DISCLAIMER > > - Checked release tag and hash > > > > Thanks, > > Poorna. > > > > > > On Fri, May 18, 2018 at 11:35 PM, James Taylor <jamestay...@apache.org> > > wrote: > > > > > I've added my PGP public key to > > > https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS. > Artifacts > > > are > > > signed with my "CODE SIGNING KEY": 308FBEE06088BE0F. Sorry for any > > > confusion. > > > > > > On Fri, May 18, 2018 at 4:02 PM, Andreas Neumann <a...@apache.org> > > wrote: > > > > > > > +0 > > > > > > > > - sha512 checksum matcnes > > > > - md5 checksum matches > > > > - I cannot verify the signature because the KEYS file does not seem > to > > > > contain your public key. Can you add your keys to it? > > > > > > > > Also, I am surprised that in Changes.txt, HBase-1.4 support is listed > > as > > > a > > > > new feature, whereas HBase-2.0 support is merely an improvement :) > > > > > > > > Best -Andreas > > > > > > > > On Fri, May 18, 2018 at 2:10 PM, James Taylor < > jamestay...@apache.org> > > > > wrote: > > > > > > > > > Hi all, > > > > > > > > > > This is a call for a vote on releasing Apache Tephra > > 0.14.0-incubating, > > > > > release candidate 1. This is the seventh release of Tephra. > > > > > > > > > > The source tarball, including signatures, digests, etc. can be > found > > > at: > > > > > https://dist.apache.org/repos/dist/dev/incubator/tephra/0. > > > > 14.0-incubating > > > > > -rc1/src > > > > > > > > > > The tag to be voted upon is v0.14.0-incubating: > > > > > https://git-wip-us.apache.org/repos/asf?p=incubator-tephra. > > > > > git;a=shortlog;h=refs/tags/v > > > > > 0.14.0-incubating > > > > > > > > > > The release hash is e93942adae0ece286157a8f6a2e5c63b53669e03: > > > > > https://git-wip-us.apache.org/repos/asf?p=incubator-tephra. > > > > git;a=commit;h= > > > > > e93942adae0ece286157a8f6a2e5c63b53669e03 > > > > > > > > > > The Nexus Staging URL: > > > > > > > > https://repository.apache.org/content/repositories/ > orgapachetephra-1011 > > > > > > > > > > Release artifacts are signed with the following key: > > > > > http://people.apache.org/keys/committer/jamestaylor > > > > > > > > > > KEYS file available: > > > > > https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS > > > > > > > > > > For information about the contents of this release, see: > > > > > https://dist.apache.org/repos/dist/dev/incubator/tephra/0. > > > > > 14.0-incubating-rc1/CHANGES.txt > > > > > > > > > > Please vote on releasing this package as Apache Tephra > > > 0.14.0-incubating > > > > > > > > > > The vote will be open for 72 hours. > > > > > > > > > > [ ] +1 Release this package as Apache Tephra 0.14.0-incubating > > > > > [ ] +0 no opinion > > > > > [ ] -1 Do not release this package because ... > > > > > > > > > > Thanks, > > > > > James > > > > > > > > > > > > > > >
Re: [VOTE] Release of Apache Tephra-0.14.0-incubating [rc1]
I've added my PGP public key to https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS. Artifacts are signed with my "CODE SIGNING KEY": 308FBEE06088BE0F. Sorry for any confusion. On Fri, May 18, 2018 at 4:02 PM, Andreas Neumann <a...@apache.org> wrote: > +0 > > - sha512 checksum matcnes > - md5 checksum matches > - I cannot verify the signature because the KEYS file does not seem to > contain your public key. Can you add your keys to it? > > Also, I am surprised that in Changes.txt, HBase-1.4 support is listed as a > new feature, whereas HBase-2.0 support is merely an improvement :) > > Best -Andreas > > On Fri, May 18, 2018 at 2:10 PM, James Taylor <jamestay...@apache.org> > wrote: > > > Hi all, > > > > This is a call for a vote on releasing Apache Tephra 0.14.0-incubating, > > release candidate 1. This is the seventh release of Tephra. > > > > The source tarball, including signatures, digests, etc. can be found at: > > https://dist.apache.org/repos/dist/dev/incubator/tephra/0. > 14.0-incubating > > -rc1/src > > > > The tag to be voted upon is v0.14.0-incubating: > > https://git-wip-us.apache.org/repos/asf?p=incubator-tephra. > > git;a=shortlog;h=refs/tags/v > > 0.14.0-incubating > > > > The release hash is e93942adae0ece286157a8f6a2e5c63b53669e03: > > https://git-wip-us.apache.org/repos/asf?p=incubator-tephra. > git;a=commit;h= > > e93942adae0ece286157a8f6a2e5c63b53669e03 > > > > The Nexus Staging URL: > > https://repository.apache.org/content/repositories/orgapachetephra-1011 > > > > Release artifacts are signed with the following key: > > http://people.apache.org/keys/committer/jamestaylor > > > > KEYS file available: > > https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS > > > > For information about the contents of this release, see: > > https://dist.apache.org/repos/dist/dev/incubator/tephra/0. > > 14.0-incubating-rc1/CHANGES.txt > > > > Please vote on releasing this package as Apache Tephra 0.14.0-incubating > > > > The vote will be open for 72 hours. > > > > [ ] +1 Release this package as Apache Tephra 0.14.0-incubating > > [ ] +0 no opinion > > [ ] -1 Do not release this package because ... > > > > Thanks, > > James > > >
[VOTE] Release of Apache Tephra-0.14.0-incubating [rc1]
Hi all, This is a call for a vote on releasing Apache Tephra 0.14.0-incubating, release candidate 1. This is the seventh release of Tephra. The source tarball, including signatures, digests, etc. can be found at: https://dist.apache.org/repos/dist/dev/incubator/tephra/0.14.0-incubating -rc1/src The tag to be voted upon is v0.14.0-incubating: https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=shortlog;h=refs/tags/v 0.14.0-incubating The release hash is e93942adae0ece286157a8f6a2e5c63b53669e03: https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=commit;h=e93942adae0ece286157a8f6a2e5c63b53669e03 The Nexus Staging URL: https://repository.apache.org/content/repositories/orgapachetephra-1011 Release artifacts are signed with the following key: http://people.apache.org/keys/committer/jamestaylor KEYS file available: https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS For information about the contents of this release, see: https://dist.apache.org/repos/dist/dev/incubator/tephra/0.14.0-incubating-rc1/CHANGES.txt Please vote on releasing this package as Apache Tephra 0.14.0-incubating The vote will be open for 72 hours. [ ] +1 Release this package as Apache Tephra 0.14.0-incubating [ ] +0 no opinion [ ] -1 Do not release this package because ... Thanks, James
[jira] [Updated] (TEPHRA-268) Replace usage of all HBase deprecated APIs
[ https://issues.apache.org/jira/browse/TEPHRA-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-268: Issue Type: Bug (was: Sub-task) Parent: (was: TEPHRA-272) > Replace usage of all HBase deprecated APIs > -- > > Key: TEPHRA-268 > URL: https://issues.apache.org/jira/browse/TEPHRA-268 > Project: Tephra > Issue Type: Bug > Reporter: James Taylor >Assignee: Ankit Singhal >Priority: Major > Labels: HBase-2.0 > Fix For: 0.15.0-incubating > > > Tephra still uses many deprecated APIs in HBase. Until this is changed, > Tephra won't work on HBase 2.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEPHRA-265) Tephra Guice License
[ https://issues.apache.org/jira/browse/TEPHRA-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-265: Fix Version/s: (was: 0.14.0-incubating) 0.15.0-incubating > Tephra Guice License > > > Key: TEPHRA-265 > URL: https://issues.apache.org/jira/browse/TEPHRA-265 > Project: Tephra > Issue Type: Bug >Affects Versions: 0.13.0-incubating >Reporter: Gokul Gunasekaran >Assignee: Gokul Gunasekaran >Priority: Major > Fix For: 0.15.0-incubating > > > The NOTICE for Guice in 0.13.0-incubating release contains (which was added > as part of the fix for TEPHRA-231): > Apache Tephra includes Guice v3.0 and Guice Assisted Inject v3.0. Tephra > elects to include this software in this distribution under the Apache License. > You can obtain a copy of the License at: > http://apache.org/licenses/LICENSE-2.0 > Instead, it should contain the exact content from the NOTICE of the Guice > JAR. > Google Guice - Core Library > Copyright 2006-2011 Google, Inc. > This product includes software developed at > The Apache Software Foundation (http://www.apache.org/). > http://mail-archives.apache.org/mod_mbox/incubator-general/201709.mbox/%3CCAOqetn-zPeOanD1fVZHVsjfwqn5qnmN9WXWjb1jDJAE8JgQ_Zg%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEPHRA-264) When transaction size limits are exceeded, the error message should indicate what configuration to change in order to increase the limit
[ https://issues.apache.org/jira/browse/TEPHRA-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-264: Fix Version/s: (was: 0.14.0-incubating) 0.15.0-incubating > When transaction size limits are exceeded, the error message should indicate > what configuration to change in order to increase the limit > > > Key: TEPHRA-264 > URL: https://issues.apache.org/jira/browse/TEPHRA-264 > Project: Tephra > Issue Type: Improvement > Components: core >Affects Versions: 0.13.0-incubating >Reporter: Andreas Neumann >Assignee: Andreas Neumann >Priority: Major > Fix For: 0.15.0-incubating > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEPHRA-283) Skip install step of travis
[ https://issues.apache.org/jira/browse/TEPHRA-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-283: Fix Version/s: (was: 0.14.0-incubating) 0.15.0-incubating > Skip install step of travis > --- > > Key: TEPHRA-283 > URL: https://issues.apache.org/jira/browse/TEPHRA-283 > Project: Tephra > Issue Type: Bug >Reporter: Ankit Singhal >Assignee: Ankit Singhal >Priority: Major > Fix For: 0.15.0-incubating > > > we can skip installation step of travis as it will unnecessarily run "mvn > install" for all the modules for every job. > This is also needed where we need to exclude to some modules from jdk7 build -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEPHRA-284) Fix tephra compat dependency in tephra example module for HBase 1.4
[ https://issues.apache.org/jira/browse/TEPHRA-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-284: Fix Version/s: (was: 0.14.0-incubating) 0.15.0-incubating > Fix tephra compat dependency in tephra example module for HBase 1.4 > --- > > Key: TEPHRA-284 > URL: https://issues.apache.org/jira/browse/TEPHRA-284 > Project: Tephra > Issue Type: Bug >Affects Versions: 0.14.0-incubating >Reporter: Ankit Singhal >Assignee: Ankit Singhal >Priority: Major > Fix For: 0.15.0-incubating > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEPHRA-265) Tephra Guice License
[ https://issues.apache.org/jira/browse/TEPHRA-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-265: Attachment: (was: TEPHRA-265.patch) > Tephra Guice License > > > Key: TEPHRA-265 > URL: https://issues.apache.org/jira/browse/TEPHRA-265 > Project: Tephra > Issue Type: Bug >Affects Versions: 0.13.0-incubating >Reporter: Gokul Gunasekaran >Assignee: Gokul Gunasekaran >Priority: Major > Fix For: 0.14.0-incubating > > > The NOTICE for Guice in 0.13.0-incubating release contains (which was added > as part of the fix for TEPHRA-231): > Apache Tephra includes Guice v3.0 and Guice Assisted Inject v3.0. Tephra > elects to include this software in this distribution under the Apache License. > You can obtain a copy of the License at: > http://apache.org/licenses/LICENSE-2.0 > Instead, it should contain the exact content from the NOTICE of the Guice > JAR. > Google Guice - Core Library > Copyright 2006-2011 Google, Inc. > This product includes software developed at > The Apache Software Foundation (http://www.apache.org/). > http://mail-archives.apache.org/mod_mbox/incubator-general/201709.mbox/%3CCAOqetn-zPeOanD1fVZHVsjfwqn5qnmN9WXWjb1jDJAE8JgQ_Zg%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TEPHRA-265) Tephra Guice License
[ https://issues.apache.org/jira/browse/TEPHRA-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480987#comment-16480987 ] James Taylor commented on TEPHRA-265: - Actually, just noticed the pull request. This is only necessary if you were to do a binary release, right? > Tephra Guice License > > > Key: TEPHRA-265 > URL: https://issues.apache.org/jira/browse/TEPHRA-265 > Project: Tephra > Issue Type: Bug >Affects Versions: 0.13.0-incubating >Reporter: Gokul Gunasekaran >Assignee: Gokul Gunasekaran >Priority: Major > Fix For: 0.14.0-incubating > > Attachments: TEPHRA-265.patch > > > The NOTICE for Guice in 0.13.0-incubating release contains (which was added > as part of the fix for TEPHRA-231): > Apache Tephra includes Guice v3.0 and Guice Assisted Inject v3.0. Tephra > elects to include this software in this distribution under the Apache License. > You can obtain a copy of the License at: > http://apache.org/licenses/LICENSE-2.0 > Instead, it should contain the exact content from the NOTICE of the Guice > JAR. > Google Guice - Core Library > Copyright 2006-2011 Google, Inc. > This product includes software developed at > The Apache Software Foundation (http://www.apache.org/). > http://mail-archives.apache.org/mod_mbox/incubator-general/201709.mbox/%3CCAOqetn-zPeOanD1fVZHVsjfwqn5qnmN9WXWjb1jDJAE8JgQ_Zg%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TEPHRA-265) Tephra Guice License
[ https://issues.apache.org/jira/browse/TEPHRA-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480980#comment-16480980 ] James Taylor commented on TEPHRA-265: - Please review the patch, [~gokulavasan] or [~poornachandra]. > Tephra Guice License > > > Key: TEPHRA-265 > URL: https://issues.apache.org/jira/browse/TEPHRA-265 > Project: Tephra > Issue Type: Bug >Affects Versions: 0.13.0-incubating >Reporter: Gokul Gunasekaran >Assignee: Gokul Gunasekaran >Priority: Major > Fix For: 0.14.0-incubating > > Attachments: TEPHRA-265.patch > > > The NOTICE for Guice in 0.13.0-incubating release contains (which was added > as part of the fix for TEPHRA-231): > Apache Tephra includes Guice v3.0 and Guice Assisted Inject v3.0. Tephra > elects to include this software in this distribution under the Apache License. > You can obtain a copy of the License at: > http://apache.org/licenses/LICENSE-2.0 > Instead, it should contain the exact content from the NOTICE of the Guice > JAR. > Google Guice - Core Library > Copyright 2006-2011 Google, Inc. > This product includes software developed at > The Apache Software Foundation (http://www.apache.org/). > http://mail-archives.apache.org/mod_mbox/incubator-general/201709.mbox/%3CCAOqetn-zPeOanD1fVZHVsjfwqn5qnmN9WXWjb1jDJAE8JgQ_Zg%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEPHRA-265) Tephra Guice License
[ https://issues.apache.org/jira/browse/TEPHRA-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-265: Attachment: TEPHRA-265.patch > Tephra Guice License > > > Key: TEPHRA-265 > URL: https://issues.apache.org/jira/browse/TEPHRA-265 > Project: Tephra > Issue Type: Bug >Affects Versions: 0.13.0-incubating >Reporter: Gokul Gunasekaran >Assignee: Gokul Gunasekaran >Priority: Major > Fix For: 0.14.0-incubating > > Attachments: TEPHRA-265.patch > > > The NOTICE for Guice in 0.13.0-incubating release contains (which was added > as part of the fix for TEPHRA-231): > Apache Tephra includes Guice v3.0 and Guice Assisted Inject v3.0. Tephra > elects to include this software in this distribution under the Apache License. > You can obtain a copy of the License at: > http://apache.org/licenses/LICENSE-2.0 > Instead, it should contain the exact content from the NOTICE of the Guice > JAR. > Google Guice - Core Library > Copyright 2006-2011 Google, Inc. > This product includes software developed at > The Apache Software Foundation (http://www.apache.org/). > http://mail-archives.apache.org/mod_mbox/incubator-general/201709.mbox/%3CCAOqetn-zPeOanD1fVZHVsjfwqn5qnmN9WXWjb1jDJAE8JgQ_Zg%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (TEPHRA-286) AbstractTransactionAwareTable.ActionChange equals method always returns false
[ https://issues.apache.org/jira/browse/TEPHRA-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved TEPHRA-286. - Resolution: Fixed > AbstractTransactionAwareTable.ActionChange equals method always returns false > - > > Key: TEPHRA-286 > URL: https://issues.apache.org/jira/browse/TEPHRA-286 > Project: Tephra > Issue Type: Bug > Reporter: James Taylor > Assignee: James Taylor >Priority: Major > Fix For: 0.14.0-incubating > > Attachments: TEPHRA-286_v1.patch, TEPHRA-286_v2.patch, > TEPHRA-286_v3.patch, TEPHRA-286_v4.patch > > > The AbstractTransactionAwareTable.ActionChange class uses Objects.equals to > compare byte[] which will always return false (unless the two arrays are ==). > It should be changed to use Bytes.equals instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: release for 0.14.0?
Ready for a release yet, Poorna? Thanks, James On Tue, May 1, 2018 at 8:06 PM, Poorna Chandra <poo...@apache.org> wrote: > Although HBase 2.0 was released yesterday, I'm not able to find the HBase > 2.0 jars in Maven Central. The release may have to wait for the HBase 2.0 > jars to be available. > > Also found a new blocker that breaks the build - > https://issues.apache.org/jira/browse/TEPHRA-288 > > Thanks, > Poorna. > > > On Wed, May 2, 2018 at 1:23 AM, Poorna Chandra <poo...@apache.org> wrote: > > > Hi All, > > > > There are a few more unresolved JIRAs marked for release > 0.14.0-incubating > > [1]. If there are no objections, I'll move them out of release > > 0.14.0-incubating tomorrow. > > > > I'm planning to start a release after that. > > > > Thanks, > > Poorna. > > > > [1] - https://issues.apache.org/jira/browse/TEPHRA-287?jql= > > project%20%3D%20TEPHRA%20AND%20fixVersion%20%3D%200.14.0- > > incubating%20%26%26%20status%20!%3D%20Resolved > > > > > > On Fri, Apr 20, 2018 at 8:44 PM, Poorna Chandra <poo...@apache.org> > wrote: > > > >> Hi James, > >> > >> There are a few bug fixes I want to get in. I'll work on them next week. > >> I'm planning to start the release process after that. > >> > >> Thanks, > >> Poorna. > >> > >> > >> On Thu, Apr 19, 2018 at 9:25 PM, James Taylor <jamestay...@apache.org> > >> wrote: > >> > >>> Would it be possible to do an 0.14.0 release? > >>> > >>> Thanks, > >>> James > >>> > >> > >> > > >
[jira] [Created] (TEPHRA-290) Make logic that determines compatibility module to use more flexible
James Taylor created TEPHRA-290: --- Summary: Make logic that determines compatibility module to use more flexible Key: TEPHRA-290 URL: https://issues.apache.org/jira/browse/TEPHRA-290 Project: Tephra Issue Type: Improvement Reporter: James Taylor Assignee: Poorna Chandra The logic that determines which compatibility module to use is based on an exact string match. A company will often create a "light" fork of an OS project in their own internal repo and have their own versioning scheme to better support emergency bug fixing. To support that better, Tephra should make the logic more flexible that determines the compatibility module. Instead of an exact string match, a check for contains could be used. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (TEPHRA-287) ActionChange.getChangeKey() not implemented correctly
[ https://issues.apache.org/jira/browse/TEPHRA-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved TEPHRA-287. - Resolution: Fixed > ActionChange.getChangeKey() not implemented correctly > - > > Key: TEPHRA-287 > URL: https://issues.apache.org/jira/browse/TEPHRA-287 > Project: Tephra > Issue Type: Bug > Reporter: James Taylor > Assignee: James Taylor >Priority: Major > Fix For: 0.14.0-incubating > > Attachments: TEPHRA-287_v1.patch, TEPHRA-287_v2.patch, > TEPHRA-287_v3.patch > > > The ActionChange.getChangeKey() simply concatenates together the row key, > family, and qualifier which could lead to incorrect conflicting keys. For > example (rowKey='a', family='bc') would conflict with (rowKey='ab', > family='c'). A simple fix would be to prefix each part with the byte length > of each part. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TEPHRA-287) ActionChange.getChangeKey() not implemented correctly
[ https://issues.apache.org/jira/browse/TEPHRA-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16466682#comment-16466682 ] James Taylor commented on TEPHRA-287: - Thanks for the review, [~poornachandra]. I made your recommended changes and merged the change. > ActionChange.getChangeKey() not implemented correctly > - > > Key: TEPHRA-287 > URL: https://issues.apache.org/jira/browse/TEPHRA-287 > Project: Tephra > Issue Type: Bug > Reporter: James Taylor > Assignee: James Taylor >Priority: Major > Fix For: 0.14.0-incubating > > Attachments: TEPHRA-287_v1.patch, TEPHRA-287_v2.patch, > TEPHRA-287_v3.patch > > > The ActionChange.getChangeKey() simply concatenates together the row key, > family, and qualifier which could lead to incorrect conflicting keys. For > example (rowKey='a', family='bc') would conflict with (rowKey='ab', > family='c'). A simple fix would be to prefix each part with the byte length > of each part. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TEPHRA-287) ActionChange.getChangeKey() not implemented correctly
[ https://issues.apache.org/jira/browse/TEPHRA-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16464472#comment-16464472 ] James Taylor commented on TEPHRA-287: - Here you go, [~poornachandra]: https://github.com/apache/incubator-tephra/pull/75 > ActionChange.getChangeKey() not implemented correctly > - > > Key: TEPHRA-287 > URL: https://issues.apache.org/jira/browse/TEPHRA-287 > Project: Tephra > Issue Type: Bug > Reporter: James Taylor > Assignee: James Taylor >Priority: Major > Fix For: 0.14.0-incubating > > Attachments: TEPHRA-287_v1.patch, TEPHRA-287_v2.patch, > TEPHRA-287_v3.patch > > > The ActionChange.getChangeKey() simply concatenates together the row key, > family, and qualifier which could lead to incorrect conflicting keys. For > example (rowKey='a', family='bc') would conflict with (rowKey='ab', > family='c'). A simple fix would be to prefix each part with the byte length > of each part. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEPHRA-287) ActionChange.getChangeKey() not implemented correctly
[ https://issues.apache.org/jira/browse/TEPHRA-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-287: Attachment: TEPHRA-287_v3.patch > ActionChange.getChangeKey() not implemented correctly > - > > Key: TEPHRA-287 > URL: https://issues.apache.org/jira/browse/TEPHRA-287 > Project: Tephra > Issue Type: Bug > Reporter: James Taylor > Assignee: James Taylor >Priority: Major > Fix For: 0.14.0-incubating > > Attachments: TEPHRA-287_v1.patch, TEPHRA-287_v2.patch, > TEPHRA-287_v3.patch > > > The ActionChange.getChangeKey() simply concatenates together the row key, > family, and qualifier which could lead to incorrect conflicting keys. For > example (rowKey='a', family='bc') would conflict with (rowKey='ab', > family='c'). A simple fix would be to prefix each part with the byte length > of each part. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEPHRA-287) ActionChange.getChangeKey() not implemented correctly
[ https://issues.apache.org/jira/browse/TEPHRA-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-287: Attachment: (was: TEPHRA-287_v3.patch) > ActionChange.getChangeKey() not implemented correctly > - > > Key: TEPHRA-287 > URL: https://issues.apache.org/jira/browse/TEPHRA-287 > Project: Tephra > Issue Type: Bug > Reporter: James Taylor > Assignee: James Taylor >Priority: Major > Fix For: 0.14.0-incubating > > Attachments: TEPHRA-287_v1.patch, TEPHRA-287_v2.patch, > TEPHRA-287_v3.patch > > > The ActionChange.getChangeKey() simply concatenates together the row key, > family, and qualifier which could lead to incorrect conflicting keys. For > example (rowKey='a', family='bc') would conflict with (rowKey='ab', > family='c'). A simple fix would be to prefix each part with the byte length > of each part. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEPHRA-287) ActionChange.getChangeKey() not implemented correctly
[ https://issues.apache.org/jira/browse/TEPHRA-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-287: Attachment: TEPHRA-287_v3.patch > ActionChange.getChangeKey() not implemented correctly > - > > Key: TEPHRA-287 > URL: https://issues.apache.org/jira/browse/TEPHRA-287 > Project: Tephra > Issue Type: Bug > Reporter: James Taylor > Assignee: James Taylor >Priority: Major > Fix For: 0.14.0-incubating > > Attachments: TEPHRA-287_v1.patch, TEPHRA-287_v2.patch, > TEPHRA-287_v3.patch > > > The ActionChange.getChangeKey() simply concatenates together the row key, > family, and qualifier which could lead to incorrect conflicting keys. For > example (rowKey='a', family='bc') would conflict with (rowKey='ab', > family='c'). A simple fix would be to prefix each part with the byte length > of each part. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
release for 0.14.0?
Would it be possible to do an 0.14.0 release? Thanks, James
[jira] [Commented] (TEPHRA-287) ActionChange.getChangeKey() not implemented correctly
[ https://issues.apache.org/jira/browse/TEPHRA-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16444824#comment-16444824 ] James Taylor commented on TEPHRA-287: - Ping [~poornachandra]. > ActionChange.getChangeKey() not implemented correctly > - > > Key: TEPHRA-287 > URL: https://issues.apache.org/jira/browse/TEPHRA-287 > Project: Tephra > Issue Type: Bug > Reporter: James Taylor > Assignee: James Taylor >Priority: Major > Fix For: 0.14.0-incubating > > Attachments: TEPHRA-287_v1.patch, TEPHRA-287_v2.patch > > > The ActionChange.getChangeKey() simply concatenates together the row key, > family, and qualifier which could lead to incorrect conflicting keys. For > example (rowKey='a', family='bc') would conflict with (rowKey='ab', > family='c'). A simple fix would be to prefix each part with the byte length > of each part. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (TEPHRA-287) ActionChange.getChangeKey() not implemented correctly
[ https://issues.apache.org/jira/browse/TEPHRA-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427430#comment-16427430 ] James Taylor edited comment on TEPHRA-287 at 4/5/18 6:41 PM: - bq. If all the clients are not upgraded simultaneously then we may miss some conflicts due to the change set encoding change. Any thoughts on how to handle this? Good point. The only thing I can think of would be to have a new config property that enables the new change set encoding. When not set, the old encoding scheme would be used. The config would be enabled only after knowing that all clients have been upgraded. I can implement this if you think it's a reasonable approach. was (Author: jamestaylor): bq. f all the clients are not upgraded simultaneously then we may miss some conflicts due to the change set encoding change. Any thoughts on how to handle this? Good point. The only thing I can think of would be to have a new config property that enables the new change set encoding. When not set, the old encoding scheme would be used. The config would be enabled only after knowing that all clients have been upgraded. I can implement this if you think it's a reasonable approach. > ActionChange.getChangeKey() not implemented correctly > - > > Key: TEPHRA-287 > URL: https://issues.apache.org/jira/browse/TEPHRA-287 > Project: Tephra > Issue Type: Bug > Reporter: James Taylor > Assignee: James Taylor >Priority: Major > Fix For: 0.14.0-incubating > > Attachments: TEPHRA-287_v1.patch, TEPHRA-287_v2.patch > > > The ActionChange.getChangeKey() simply concatenates together the row key, > family, and qualifier which could lead to incorrect conflicting keys. For > example (rowKey='a', family='bc') would conflict with (rowKey='ab', > family='c'). A simple fix would be to prefix each part with the byte length > of each part. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TEPHRA-287) ActionChange.getChangeKey() not implemented correctly
[ https://issues.apache.org/jira/browse/TEPHRA-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427430#comment-16427430 ] James Taylor commented on TEPHRA-287: - bq. f all the clients are not upgraded simultaneously then we may miss some conflicts due to the change set encoding change. Any thoughts on how to handle this? Good point. The only thing I can think of would be to have a new config property that enables the new change set encoding. When not set, the old encoding scheme would be used. The config would be enabled only after knowing that all clients have been upgraded. I can implement this if you think it's a reasonable approach. > ActionChange.getChangeKey() not implemented correctly > - > > Key: TEPHRA-287 > URL: https://issues.apache.org/jira/browse/TEPHRA-287 > Project: Tephra > Issue Type: Bug > Reporter: James Taylor > Assignee: James Taylor >Priority: Major > Fix For: 0.14.0-incubating > > Attachments: TEPHRA-287_v1.patch, TEPHRA-287_v2.patch > > > The ActionChange.getChangeKey() simply concatenates together the row key, > family, and qualifier which could lead to incorrect conflicting keys. For > example (rowKey='a', family='bc') would conflict with (rowKey='ab', > family='c'). A simple fix would be to prefix each part with the byte length > of each part. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEPHRA-287) ActionChange.getChangeKey() not implemented correctly
[ https://issues.apache.org/jira/browse/TEPHRA-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-287: Attachment: TEPHRA-287_v2.patch > ActionChange.getChangeKey() not implemented correctly > - > > Key: TEPHRA-287 > URL: https://issues.apache.org/jira/browse/TEPHRA-287 > Project: Tephra > Issue Type: Bug > Reporter: James Taylor > Assignee: James Taylor >Priority: Major > Fix For: 0.14.0-incubating > > Attachments: TEPHRA-287_v1.patch, TEPHRA-287_v2.patch > > > The ActionChange.getChangeKey() simply concatenates together the row key, > family, and qualifier which could lead to incorrect conflicting keys. For > example (rowKey='a', family='bc') would conflict with (rowKey='ab', > family='c'). A simple fix would be to prefix each part with the byte length > of each part. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEPHRA-286) AbstractTransactionAwareTable.ActionChange equals method always returns false
[ https://issues.apache.org/jira/browse/TEPHRA-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-286: Attachment: TEPHRA-286_v4.patch > AbstractTransactionAwareTable.ActionChange equals method always returns false > - > > Key: TEPHRA-286 > URL: https://issues.apache.org/jira/browse/TEPHRA-286 > Project: Tephra > Issue Type: Bug > Reporter: James Taylor > Assignee: James Taylor >Priority: Major > Fix For: 0.14.0-incubating > > Attachments: TEPHRA-286_v1.patch, TEPHRA-286_v2.patch, > TEPHRA-286_v3.patch, TEPHRA-286_v4.patch > > > The AbstractTransactionAwareTable.ActionChange class uses Objects.equals to > compare byte[] which will always return false (unless the two arrays are ==). > It should be changed to use Bytes.equals instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TEPHRA-287) ActionChange.getChangeKey() not implemented correctly
[ https://issues.apache.org/jira/browse/TEPHRA-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412074#comment-16412074 ] James Taylor commented on TEPHRA-287: - Ping [~poornachandra]. > ActionChange.getChangeKey() not implemented correctly > - > > Key: TEPHRA-287 > URL: https://issues.apache.org/jira/browse/TEPHRA-287 > Project: Tephra > Issue Type: Bug > Reporter: James Taylor > Assignee: James Taylor >Priority: Major > Fix For: 0.14.0-incubating > > Attachments: TEPHRA-287_v1.patch > > > The ActionChange.getChangeKey() simply concatenates together the row key, > family, and qualifier which could lead to incorrect conflicting keys. For > example (rowKey='a', family='bc') would conflict with (rowKey='ab', > family='c'). A simple fix would be to prefix each part with the byte length > of each part. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TEPHRA-286) AbstractTransactionAwareTable.ActionChange equals method always returns false
[ https://issues.apache.org/jira/browse/TEPHRA-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16407270#comment-16407270 ] James Taylor commented on TEPHRA-286: - I’ll update spacing and commit. Thanks for the review. > AbstractTransactionAwareTable.ActionChange equals method always returns false > - > > Key: TEPHRA-286 > URL: https://issues.apache.org/jira/browse/TEPHRA-286 > Project: Tephra > Issue Type: Bug > Reporter: James Taylor > Assignee: James Taylor >Priority: Major > Fix For: 0.14.0-incubating > > Attachments: TEPHRA-286_v1.patch, TEPHRA-286_v2.patch, > TEPHRA-286_v3.patch > > > The AbstractTransactionAwareTable.ActionChange class uses Objects.equals to > compare byte[] which will always return false (unless the two arrays are ==). > It should be changed to use Bytes.equals instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TEPHRA-287) ActionChange.getChangeKey() not implemented correctly
[ https://issues.apache.org/jira/browse/TEPHRA-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405880#comment-16405880 ] James Taylor commented on TEPHRA-287: - Please review, [~chtyim] or [~poornachandra]. > ActionChange.getChangeKey() not implemented correctly > - > > Key: TEPHRA-287 > URL: https://issues.apache.org/jira/browse/TEPHRA-287 > Project: Tephra > Issue Type: Bug > Reporter: James Taylor >Assignee: Poorna Chandra >Priority: Major > Fix For: 0.14.0-incubating > > Attachments: TEPHRA-287_v1.patch > > > The ActionChange.getChangeKey() simply concatenates together the row key, > family, and qualifier which could lead to incorrect conflicting keys. For > example (rowKey='a', family='bc') would conflict with (rowKey='ab', > family='c'). A simple fix would be to prefix each part with the byte length > of each part. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (TEPHRA-287) ActionChange.getChangeKey() not implemented correctly
[ https://issues.apache.org/jira/browse/TEPHRA-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor reassigned TEPHRA-287: --- Assignee: James Taylor (was: Poorna Chandra) > ActionChange.getChangeKey() not implemented correctly > - > > Key: TEPHRA-287 > URL: https://issues.apache.org/jira/browse/TEPHRA-287 > Project: Tephra > Issue Type: Bug > Reporter: James Taylor > Assignee: James Taylor >Priority: Major > Fix For: 0.14.0-incubating > > Attachments: TEPHRA-287_v1.patch > > > The ActionChange.getChangeKey() simply concatenates together the row key, > family, and qualifier which could lead to incorrect conflicting keys. For > example (rowKey='a', family='bc') would conflict with (rowKey='ab', > family='c'). A simple fix would be to prefix each part with the byte length > of each part. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEPHRA-287) ActionChange.getChangeKey() not implemented correctly
[ https://issues.apache.org/jira/browse/TEPHRA-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-287: Fix Version/s: 0.14.0-incubating > ActionChange.getChangeKey() not implemented correctly > - > > Key: TEPHRA-287 > URL: https://issues.apache.org/jira/browse/TEPHRA-287 > Project: Tephra > Issue Type: Bug > Reporter: James Taylor >Assignee: Poorna Chandra >Priority: Major > Fix For: 0.14.0-incubating > > Attachments: TEPHRA-287_v1.patch > > > The ActionChange.getChangeKey() simply concatenates together the row key, > family, and qualifier which could lead to incorrect conflicting keys. For > example (rowKey='a', family='bc') would conflict with (rowKey='ab', > family='c'). A simple fix would be to prefix each part with the byte length > of each part. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TEPHRA-286) AbstractTransactionAwareTable.ActionChange equals method always returns false
[ https://issues.apache.org/jira/browse/TEPHRA-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405878#comment-16405878 ] James Taylor commented on TEPHRA-286: - Third time's the charm - with check style and rat checks passing. > AbstractTransactionAwareTable.ActionChange equals method always returns false > - > > Key: TEPHRA-286 > URL: https://issues.apache.org/jira/browse/TEPHRA-286 > Project: Tephra > Issue Type: Bug > Reporter: James Taylor > Assignee: James Taylor >Priority: Major > Fix For: 0.14.0-incubating > > Attachments: TEPHRA-286_v1.patch, TEPHRA-286_v2.patch, > TEPHRA-286_v3.patch > > > The AbstractTransactionAwareTable.ActionChange class uses Objects.equals to > compare byte[] which will always return false (unless the two arrays are ==). > It should be changed to use Bytes.equals instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEPHRA-287) ActionChange.getChangeKey() not implemented correctly
[ https://issues.apache.org/jira/browse/TEPHRA-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-287: Attachment: TEPHRA-287_v1.patch > ActionChange.getChangeKey() not implemented correctly > - > > Key: TEPHRA-287 > URL: https://issues.apache.org/jira/browse/TEPHRA-287 > Project: Tephra > Issue Type: Bug > Reporter: James Taylor >Assignee: Poorna Chandra >Priority: Major > Attachments: TEPHRA-287_v1.patch > > > The ActionChange.getChangeKey() simply concatenates together the row key, > family, and qualifier which could lead to incorrect conflicting keys. For > example (rowKey='a', family='bc') would conflict with (rowKey='ab', > family='c'). A simple fix would be to prefix each part with the byte length > of each part. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEPHRA-286) AbstractTransactionAwareTable.ActionChange equals method always returns false
[ https://issues.apache.org/jira/browse/TEPHRA-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-286: Attachment: TEPHRA-286_v3.patch > AbstractTransactionAwareTable.ActionChange equals method always returns false > - > > Key: TEPHRA-286 > URL: https://issues.apache.org/jira/browse/TEPHRA-286 > Project: Tephra > Issue Type: Bug > Reporter: James Taylor > Assignee: James Taylor >Priority: Major > Fix For: 0.14.0-incubating > > Attachments: TEPHRA-286_v1.patch, TEPHRA-286_v2.patch, > TEPHRA-286_v3.patch > > > The AbstractTransactionAwareTable.ActionChange class uses Objects.equals to > compare byte[] which will always return false (unless the two arrays are ==). > It should be changed to use Bytes.equals instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TEPHRA-286) AbstractTransactionAwareTable.ActionChange equals method always returns false
[ https://issues.apache.org/jira/browse/TEPHRA-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405838#comment-16405838 ] James Taylor commented on TEPHRA-286: - Attached v2 patch that includes the license header for the new test file. > AbstractTransactionAwareTable.ActionChange equals method always returns false > - > > Key: TEPHRA-286 > URL: https://issues.apache.org/jira/browse/TEPHRA-286 > Project: Tephra > Issue Type: Bug > Reporter: James Taylor > Assignee: James Taylor >Priority: Major > Fix For: 0.14.0-incubating > > Attachments: TEPHRA-286_v1.patch, TEPHRA-286_v2.patch > > > The AbstractTransactionAwareTable.ActionChange class uses Objects.equals to > compare byte[] which will always return false (unless the two arrays are ==). > It should be changed to use Bytes.equals instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEPHRA-286) AbstractTransactionAwareTable.ActionChange equals method always returns false
[ https://issues.apache.org/jira/browse/TEPHRA-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-286: Attachment: TEPHRA-286_v2.patch > AbstractTransactionAwareTable.ActionChange equals method always returns false > - > > Key: TEPHRA-286 > URL: https://issues.apache.org/jira/browse/TEPHRA-286 > Project: Tephra > Issue Type: Bug > Reporter: James Taylor > Assignee: James Taylor >Priority: Major > Fix For: 0.14.0-incubating > > Attachments: TEPHRA-286_v1.patch, TEPHRA-286_v2.patch > > > The AbstractTransactionAwareTable.ActionChange class uses Objects.equals to > compare byte[] which will always return false (unless the two arrays are ==). > It should be changed to use Bytes.equals instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (TEPHRA-287) ActionChange.getChangeKey() not implemented correctly
James Taylor created TEPHRA-287: --- Summary: ActionChange.getChangeKey() not implemented correctly Key: TEPHRA-287 URL: https://issues.apache.org/jira/browse/TEPHRA-287 Project: Tephra Issue Type: Bug Reporter: James Taylor Assignee: Poorna Chandra The ActionChange.getChangeKey() simply concatenates together the row key, family, and qualifier which could lead to incorrect conflicting keys. For example (rowKey='a', family='bc') would conflict with (rowKey='ab', family='c'). A simple fix would be to prefix each part with the byte length of each part. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEPHRA-286) AbstractTransactionAwareTable.ActionChange equals method always returns false
[ https://issues.apache.org/jira/browse/TEPHRA-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-286: Fix Version/s: 0.14.0-incubating > AbstractTransactionAwareTable.ActionChange equals method always returns false > - > > Key: TEPHRA-286 > URL: https://issues.apache.org/jira/browse/TEPHRA-286 > Project: Tephra > Issue Type: Bug > Reporter: James Taylor > Assignee: James Taylor >Priority: Major > Fix For: 0.14.0-incubating > > Attachments: TEPHRA-286_v1.patch > > > The AbstractTransactionAwareTable.ActionChange class uses Objects.equals to > compare byte[] which will always return false (unless the two arrays are ==). > It should be changed to use Bytes.equals instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TEPHRA-286) AbstractTransactionAwareTable.ActionChange equals method always returns false
[ https://issues.apache.org/jira/browse/TEPHRA-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405715#comment-16405715 ] James Taylor commented on TEPHRA-286: - Please review, [~poornachandra]. > AbstractTransactionAwareTable.ActionChange equals method always returns false > - > > Key: TEPHRA-286 > URL: https://issues.apache.org/jira/browse/TEPHRA-286 > Project: Tephra > Issue Type: Bug > Reporter: James Taylor > Assignee: James Taylor >Priority: Major > Attachments: TEPHRA-286_v1.patch > > > The AbstractTransactionAwareTable.ActionChange class uses Objects.equals to > compare byte[] which will always return false (unless the two arrays are ==). > It should be changed to use Bytes.equals instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEPHRA-286) AbstractTransactionAwareTable.ActionChange equals method always returns false
[ https://issues.apache.org/jira/browse/TEPHRA-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated TEPHRA-286: Attachment: TEPHRA-286_v1.patch > AbstractTransactionAwareTable.ActionChange equals method always returns false > - > > Key: TEPHRA-286 > URL: https://issues.apache.org/jira/browse/TEPHRA-286 > Project: Tephra > Issue Type: Bug > Reporter: James Taylor > Assignee: James Taylor >Priority: Major > Attachments: TEPHRA-286_v1.patch > > > The AbstractTransactionAwareTable.ActionChange class uses Objects.equals to > compare byte[] which will always return false (unless the two arrays are ==). > It should be changed to use Bytes.equals instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
