Re: [ACTION REQUIRED] Omid & Tephra Migration to Phoenix LDAP

I think there are various options here: 1) Leave as is, with separate release cycles etc. 2) Migrate into Phoenix code base, release together with phoenix, but as separate, independent artifacts 3) Tightly integrate into Phoenix, essentially removing support for using them independently I

Re: [ACTION REQUIRED] Omid & Tephra Migration to Phoenix LDAP

Hi, my ID is anew and I intend to continue contributing to Tephra. -Andreas On Wed, Nov 27, 2019 at 1:39 PM Gokul Gunasekaran wrote: > Hi, > > I intend to continue working on Tephra. My id is gokul. > > Gokul > > On Tue, Nov 26, 2019 at 10:25 AM Josh Elser wrote: > > > Hi, > > > > As a part of

Re: [VOTE] Graduate into the Phoenix project

+1 On Wed, Oct 30, 2019 at 12:28 PM James Taylor wrote: > +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

[jira] [Commented] (TEPHRA-303) HBase 1.1 tests don't compile

[ https://issues.apache.org/jira/browse/TEPHRA-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16961493#comment-16961493 ] Andreas Neumann commented on TEPHRA-303: It's been a while, I agree a release would be good

[jira] [Updated] (TEPHRA-302) Add tests and examples for HBase 1.5.x

[ https://issues.apache.org/jira/browse/TEPHRA-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Neumann updated TEPHRA-302: --- Summary: Add tests and examples for HBase 1.5.x (was: Add tests for HBase 1.5.x) >

[jira] [Resolved] (TEPHRA-303) HBase 1.1 tests don't compile

[ https://issues.apache.org/jira/browse/TEPHRA-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Neumann resolved TEPHRA-303. Resolution: Fixed > HBase 1.1 tests don't comp

[jira] [Assigned] (TEPHRA-302) Add tests for HBase 1.5.x

[ https://issues.apache.org/jira/browse/TEPHRA-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Neumann reassigned TEPHRA-302: -- Assignee: Andreas Neumann (was: Poorna Chandra) > Add tests for HBase 1.

[jira] [Commented] (TEPHRA-303) HBase 1.1 tests don't compile

[ https://issues.apache.org/jira/browse/TEPHRA-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16903170#comment-16903170 ] Andreas Neumann commented on TEPHRA-303: Since there don't seem to be any objections, I

[jira] [Commented] (TEPHRA-303) HBase 1.1 tests don't compile

[ https://issues.apache.org/jira/browse/TEPHRA-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16891468#comment-16891468 ] Andreas Neumann commented on TEPHRA-303: [~lhofhansl] do you think this is good to merge

[jira] [Commented] (TEPHRA-303) HBase 1.1 tests don't compile

[ https://issues.apache.org/jira/browse/TEPHRA-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890317#comment-16890317 ] Andreas Neumann commented on TEPHRA-303: I also restructures the build so that it pass in Travis

[jira] [Resolved] (TEPHRA-304) Remove Support for Java 7

[ https://issues.apache.org/jira/browse/TEPHRA-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Neumann resolved TEPHRA-304. Resolution: Fixed Fix Version/s: 0.16.0-incubating > Remove Support for Jav

Re: [DISCUSS] Remove support for Java 7

Looks like there are no objections. I have created https://issues.apache.org/jira/browse/TEPHRA-304 and will send a PR soon. -Andreas On Wed, Jul 10, 2019 at 2:02 PM Terence Yim wrote: > +1 from me for removing Java 7 support. > > Terence > > On Wed, Jul 10, 2019 at 10:22 AM

[jira] [Created] (TEPHRA-304) Remove Support for Java 7

Andreas Neumann created TEPHRA-304: -- Summary: Remove Support for Java 7 Key: TEPHRA-304 URL: https://issues.apache.org/jira/browse/TEPHRA-304 Project: Tephra Issue Type: Improvement

[DISCUSS] Remove support for Java 7

All, Java 7 has long reached the end of its life support, yet Tephra still supports and tests with Java 7. After the recent change to use HTTPS, Java 7 causes repeated test failures, caused by its lack of support for TLS 1.2 (

[jira] [Commented] (TEPHRA-303) HBase 1.1 tests don't compile

[ https://issues.apache.org/jira/browse/TEPHRA-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16882281#comment-16882281 ] Andreas Neumann commented on TEPHRA-303: Java 7 build fail due to this:  [https

[jira] [Commented] (TEPHRA-303) HBase 1.1 tests don't compile

[ https://issues.apache.org/jira/browse/TEPHRA-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16882277#comment-16882277 ] Andreas Neumann commented on TEPHRA-303: Then, is the above good to merge? I will start

[jira] [Commented] (TEPHRA-303) HBase 1.1 tests don't compile

[ https://issues.apache.org/jira/browse/TEPHRA-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16878152#comment-16878152 ] Andreas Neumann commented on TEPHRA-303: This PR seems to fix it It is a bit of a restructuring

[jira] [Commented] (TEPHRA-303) HBase 1.1 tests don't compile

[ https://issues.apache.org/jira/browse/TEPHRA-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16875244#comment-16875244 ] Andreas Neumann commented on TEPHRA-303: Running mvn --debug, I see that it uses: {code:java

[jira] [Commented] (TEPHRA-303) HBase 1.1 tests don't compile

[ https://issues.apache.org/jira/browse/TEPHRA-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16875239#comment-16875239 ] Andreas Neumann commented on TEPHRA-303: It failed for me on Linux, where I have maven 3.6.1

[jira] [Commented] (TEPHRA-303) HBase 1.1 tests don't compile

[ https://issues.apache.org/jira/browse/TEPHRA-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16875223#comment-16875223 ] Andreas Neumann commented on TEPHRA-303: Looks like my versions I slightly different.  {code:java

Re: [DISCUSS] Status of this project

ional tables, there’s a lot about that > > which makes sense. > > > > > > > On Jun 21, 2019, at 3:36 PM, Andreas Neumann wrote: > > > > > > Hello everybody, > > > > > > Observing that this project is not making much progress towards

[jira] [Commented] (TEPHRA-303) HBase 1.1 tests don't compile

[ https://issues.apache.org/jira/browse/TEPHRA-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16874537#comment-16874537 ] Andreas Neumann commented on TEPHRA-303: It succeeds for me. When I run the same command

[jira] [Commented] (TEPHRA-303) HBase 1.1 tests don't compile

[ https://issues.apache.org/jira/browse/TEPHRA-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16874250#comment-16874250 ] Andreas Neumann commented on TEPHRA-303: Interesting, how did this pass the travis build

[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=16873698#comment-16873698 ] Andreas Neumann commented on TEPHRA-301: I think it's ok to commit this. Can you open a Jira

[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=16873686#comment-16873686 ] Andreas Neumann commented on TEPHRA-301: I think you should still add tests for Hbase-1.5

[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=16873623#comment-16873623 ] Andreas Neumann commented on TEPHRA-301: +1 to James' comment. We can just use the 1.4 module

[DISCUSS] Status of this project

Hello everybody, Observing that this project is not making much progress towards graduation, the community has not grown much over the last year, and not many new features have been added, activity overall is pretty low and the project seems a bit stagnating. I am wondering whether we should

Re: Proposed Jun19 incubator report for Tephra

Thanks for the quick responses. Submitting it to wiki now. -Andreas On Tue, Jun 4, 2019 at 4:44 PM James Taylor wrote: > +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 wr

Proposed Jun19 incubator report for Tephra

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

[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=16846268#comment-16846268 ] Andreas Neumann commented on TEPHRA-300: I think it would be at least required in 2.0? > Tep

[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=16846259#comment-16846259 ] Andreas Neumann commented on TEPHRA-300: The change LGTM.  Since this applies to older HBase

[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=16842802#comment-16842802 ] Andreas Neumann commented on TEPHRA-299: Please go ahead. Looks like [~poornachandra] already

Re: Reading tephra snapshots

Hi Varun, for debugging purposes, you should only need to read the last snapshot and the transaction log that follows it. Older snapshots should not be needed. Tephra does not have a CLI tool to do that yet, CDAP (which uses Tephra) has a similar tool, however a little more complex because it

Re: SELECT after INSERT shows missing data

1) our transactions are in-fact using Tephra snapshot isolation > 2) any lower level Tephra transaction details which may help us > troubleshoot this issue, if and when it occurs again? > > Thanks very much > > On Tue, Dec 11, 2018 at 12:05 PM Andreas Neumann wrote: > &g

Re: SELECT after INSERT shows missing data

Hey Varun, I think the issue is that your code starts the second transaction before the first one has committed (inside the outer @Transactional). Because of snapshot isolation, the second transaction cannot see the writes from the first one. I see tw ways to make it work: 1. Remove the

Re: Proposed Tehpra incubator report for Dec 2018

LGTM. Thanks for putting it together, Poorna. On Wed, Dec 5, 2018 at 2:46 PM Poorna Chandra wrote: > Hi All, > > Please review the proposed incubator report for Tephra. I'm add it to the > incubator wiki later this afternoon. > > Thanks, > Poorna > > > > Tephra

Re: Tephra + Phoenix - configuration for high availability

Hi Curtis, All changes to the transaction state, including in-process transactions, are captured in the transaction log. When a failover occurs, the new transaction manager recreates the entire transaction state by replaying the log from the last snapshot. In-flight transactions should still be

Re: HBase 2.0 support?

Hey, I think it is already supported - it was added in 0.14. See https://issues.apache.org/jira/browse/TEPHRA-272 Do you see any issues using it with HBase 2.0? Cheers -Andreas On Thu, Aug 30, 2018 at 10:17 AM Jean-Marc Spaggiari < jean-m...@spaggiari.org> wrote: > Hi, > > I'm wondering if

[jira] [Created] (TEPHRA-293) Transaction Log is logging too verbosely

Andreas Neumann created TEPHRA-293: -- Summary: Transaction Log is logging too verbosely Key: TEPHRA-293 URL: https://issues.apache.org/jira/browse/TEPHRA-293 Project: Tephra Issue Type

Re: Question from a mentor after reviewing the latest report

being a > subproject. > > Andreas, do you agree that Tephra is ready to start thinking about > graduation? > > Alan. > > On Thu, Jun 14, 2018 at 8:48 AM Andreas Neumann wrote: > > > My 2 cents: > > > > I think in its current scope, Tephra is quite mature and comple

Re: Question from a mentor after reviewing the latest report

My 2 cents: I think in its current scope, Tephra is quite mature and complete. The next big step would be to implement a fully distributed transaction manager, with replication and consensus protocol to ensure consistency. That would be a major undertaking and I am not sure that it would be

Re: Proposed incubator podling report for June 2018

done. Thanks for your input. On Wed, Jun 6, 2018 at 1:48 PM, Poorna Chandra wrote: > +1, thanks Andreas! > > Poorna. > > On Wed, Jun 6, 2018, 9:38 AM Andreas Neumann wrote: > > > Good point, I will add that. > > > > On Tue, Jun 5, 2018 at 6:13 PM, James Ta

Re: Proposed incubator podling report for June 2018

Good point, I will add that. On Tue, Jun 5, 2018 at 6:13 PM, James Taylor wrote: > 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: > > > H

Proposed incubator podling report for June 2018

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

[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=16488485#comment-16488485 ] Andreas Neumann commented on TEPHRA-291: HBase, for example, has  [https://git-wip-us.apache.org

[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=16483282#comment-16483282 ] Andreas Neumann commented on TEPHRA-291: Thanks for the patch, [~jamestaylor]. I am wondering

[jira] [Created] (TEPHRA-291) Notice file is outdated

Andreas Neumann created TEPHRA-291: -- Summary: Notice file is outdated Key: TEPHRA-291 URL: https://issues.apache.org/jira/browse/TEPHRA-291 Project: Tephra Issue Type: Bug Affects

Re: [VOTE] Release of Apache Tephra-0.14.0-incubating [rc1]

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 th

Re: [VOTE] Release of Apache Tephra-0.14.0-incubating [rc1]

t; > 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

[jira] [Commented] (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:comment-tabpanel=16423226#comment-16423226 ] Andreas Neumann commented on TEPHRA-269: Nice design! A couple of comments: * would it make sense

[jira] [Commented] (TEPHRA-285) Fix TransactionProcessorTest in tephra-hbase-compat-1.4

[ https://issues.apache.org/jira/browse/TEPHRA-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412073#comment-16412073 ] Andreas Neumann commented on TEPHRA-285: Until this is fixed in HBase, we should exclude

[jira] [Resolved] (TEPHRA-279) If getTransactionAwareName() throws an exception, abort() does not happen

[ https://issues.apache.org/jira/browse/TEPHRA-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Neumann resolved TEPHRA-279. Resolution: Fixed > If getTransactionAwareName() throws an exception, abort() d

Re: Proposed Tephra incubator report for Mar 2018

+1 On Tue, Mar 6, 2018 at 12:31 PM, Gokul Gunasekaran wrote: > +1 > > On Tue, Mar 6, 2018 at 11:41 AM, James Taylor > wrote: > > > +1 > > > > On Tue, Mar 6, 2018 at 11:41 AM, Poorna Chandra > wrote: > > > > > Hi All, > > > > > >

[jira] [Resolved] (TEPHRA-282) Travis builds fail due to timeout

[ https://issues.apache.org/jira/browse/TEPHRA-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Neumann resolved TEPHRA-282. Resolution: Fixed > Travis builds fail due to time

[jira] [Created] (TEPHRA-282) Travis builds fail due to timeout

Andreas Neumann created TEPHRA-282: -- Summary: Travis builds fail due to timeout Key: TEPHRA-282 URL: https://issues.apache.org/jira/browse/TEPHRA-282 Project: Tephra Issue Type: Bug

[jira] [Updated] (TEPHRA-278) Support HBase 1.4

[ https://issues.apache.org/jira/browse/TEPHRA-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Neumann updated TEPHRA-278: --- Fix Version/s: 0.14.0-incubating > Support HBase

[jira] [Resolved] (TEPHRA-278) Support HBase 1.4

[ https://issues.apache.org/jira/browse/TEPHRA-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Neumann resolved TEPHRA-278. Resolution: Fixed > Support HBase 1.4 > - > >

[jira] [Commented] (TEPHRA-278) Support HBase 1.4

[ https://issues.apache.org/jira/browse/TEPHRA-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327459#comment-16327459 ] Andreas Neumann commented on TEPHRA-278: OK, I will create a Jira for the build timeout

[jira] [Commented] (TEPHRA-247) Avoid encoding the transaction multiple times

[ https://issues.apache.org/jira/browse/TEPHRA-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327452#comment-16327452 ] Andreas Neumann commented on TEPHRA-247: Yes, the in-progress list can grow large. A would think

[jira] [Commented] (TEPHRA-278) Support HBase 1.4

[ https://issues.apache.org/jira/browse/TEPHRA-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16326505#comment-16326505 ] Andreas Neumann commented on TEPHRA-278: Hmmm. According to this: [https://docs.travis-ci.com

[jira] [Commented] (TEPHRA-247) Avoid encoding the transaction multiple times

[ https://issues.apache.org/jira/browse/TEPHRA-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16326493#comment-16326493 ] Andreas Neumann commented on TEPHRA-247: I do see that it could be possible to work around

[jira] [Assigned] (TEPHRA-279) If getTransactionAwareName() throws an exception, abort() does not happen

[ https://issues.apache.org/jira/browse/TEPHRA-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Neumann reassigned TEPHRA-279: -- Assignee: Andreas Neumann (was: Poorna Chandra) > If getTransactionAwareName() thr

[jira] [Created] (TEPHRA-281) TransactionContext should allow sub-classes to manage the tx-awares

Andreas Neumann created TEPHRA-281: -- Summary: TransactionContext should allow sub-classes to manage the tx-awares Key: TEPHRA-281 URL: https://issues.apache.org/jira/browse/TEPHRA-281 Project

[jira] [Created] (TEPHRA-280) TransactionContext is too chatty

Andreas Neumann created TEPHRA-280: -- Summary: TransactionContext is too chatty Key: TEPHRA-280 URL: https://issues.apache.org/jira/browse/TEPHRA-280 Project: Tephra Issue Type: Improvement

[jira] [Created] (TEPHRA-279) If getTransactionAwareName() throws an exception, abort() does not happen

Andreas Neumann created TEPHRA-279: -- Summary: If getTransactionAwareName() throws an exception, abort() does not happen Key: TEPHRA-279 URL: https://issues.apache.org/jira/browse/TEPHRA-279 Project

[jira] [Comment Edited] (TEPHRA-247) Avoid encoding the transaction multiple times

[ https://issues.apache.org/jira/browse/TEPHRA-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16323117#comment-16323117 ] Andreas Neumann edited comment on TEPHRA-247 at 1/11/18 10:42 PM: -- Hi

[jira] [Commented] (TEPHRA-247) Avoid encoding the transaction multiple times

[ https://issues.apache.org/jira/browse/TEPHRA-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16323117#comment-16323117 ] Andreas Neumann commented on TEPHRA-247: Hi Patr > Avoid encoding the transaction multiple ti

Re: Proposed Tephra incubator report for December 2017

+1 looks good On Tue, Dec 5, 2017 at 1:25 PM, Poorna Chandra wrote: > Hi All, > > Please review the draft incubator report for Tephra. Let me know if any > changes are required. The report is due tomorrow. I'm planning to add it to > the wiki tomorrow. > > Thanks, > Poorna. >

Re: Delete markers are returned from a regular Get/Scan

do you think? On Tue, Nov 14, 2017 at 2:26 PM, Andreas Neumann <a...@apache.org> wrote: > Hi Micael, > > mixing transactional and non-transactional writes in the same table is > risky, and you spotted one of the issues with that. Tephra inserts a > "family delete marker&q

Re: java.lang.RuntimeException: org.apache.thrift.TException: Unable to discover transaction service.

n Wed, Oct 18, 2017 at 1:39 PM, Andreas Neumann <a...@apache.org> wrote: > > > Hi James, > > > > do you have logs from that test run? There can be different reasons: > > - the test started before Tephra was initialized, in that case maybe wait > > until it

[jira] [Commented] (TEPHRA-257) If start() encounters an RPC timeout, an invalid transaction is left behind

[ https://issues.apache.org/jira/browse/TEPHRA-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16202550#comment-16202550 ] Andreas Neumann commented on TEPHRA-257: It turns out that this cannot be fixed as long as Tephra

[jira] [Resolved] (TEPHRA-257) If start() encounters an RPC timeout, an invalid transaction is left behind

[ https://issues.apache.org/jira/browse/TEPHRA-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Neumann resolved TEPHRA-257. Resolution: Won't Fix > If start() encounters an RPC timeout, an invalid transact

[ANNOUNCE] Apache Tephra-0.13.0-incubating released

Hi All, The Apache Tephra team is excited to announce the latest release of Apache Tephra-0.13.0-incubating. This is the sixth 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

[jira] [Created] (TEPHRA-264) When transaction size limits are exceeded, the error message should indicate what configuration to change in order to increase the limit

Andreas Neumann created TEPHRA-264: -- Summary: 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

[jira] [Commented] (TEPHRA-99) Make "long running" transactions usable with TransactionContext

[ https://issues.apache.org/jira/browse/TEPHRA-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16170385#comment-16170385 ] Andreas Neumann commented on TEPHRA-99: --- Unfortunately, there is no easy way for a client to find out

[jira] [Commented] (TEPHRA-99) Make "long running" transactions usable with TransactionContext

[ https://issues.apache.org/jira/browse/TEPHRA-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16168069#comment-16168069 ] Andreas Neumann commented on TEPHRA-99: --- Conceptually that can work. There are only two caveats

[VOTE] Release of Apache Tephra-0.13.0-incubating [rc2]

Hi all, This is a call for a vote on releasing Apache Tephra 0.13.0-incubating, release candidate 2. This is the sixth release of Tephra. The source tarball, including signatures, digests, etc. can be found at: https://dist.apache.org/repos/dist/dev/incubator/tephra/0. 13.0-incubating-rc2/src

[jira] [Commented] (TEPHRA-99) Make "long running" transactions usable with TransactionContext

[ https://issues.apache.org/jira/browse/TEPHRA-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16167194#comment-16167194 ] Andreas Neumann commented on TEPHRA-99: --- You only need to worry about updateTx() if you use

Re: [VOTE] Release of Apache Tephra-0.13.0-incubating [rc1]

es Taylor <jamestay...@apache.org> > wrote: > > > +1. Verified that all Phoenix unit tests pass with the RC. > > > > On Wed, Sep 13, 2017 at 8:31 PM Andreas Neumann <a...@apache.org> wrote: > > > > > Hi all, > > > > > > This is a cal

[jira] [Commented] (TEPHRA-99) Make "long running" transactions usable with TransactionContext

[ https://issues.apache.org/jira/browse/TEPHRA-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16166619#comment-16166619 ] Andreas Neumann commented on TEPHRA-99: --- It seems what you really need is a read-only transaction

Re: release for 0.13?

Hi James, excellent timing! We were just looking at remaining issues and moved them out to 0.14, none of them were critical or show-stoppers, and should not hold back a release that supports Hbase 1.3. We are planning to prepare the release and send out the vote tonight. If you want to help, we'd

[jira] [Updated] (TEPHRA-245) Improve the prune debug tool

[ https://issues.apache.org/jira/browse/TEPHRA-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Neumann updated TEPHRA-245: --- Fix Version/s: (was: 0.13.0-incubating) 0.14.0-incubating > Impr

[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 ] Andreas Neumann updated TEPHRA-204: --- Fix Version/s: (was: 0.13.0-incubating) 0.14.0-incubating > Docum

[jira] [Resolved] (TEPHRA-219) Setup proper security context in co-processor for compaction and flushes

[ https://issues.apache.org/jira/browse/TEPHRA-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Neumann resolved TEPHRA-219. Resolution: Fixed Remaining refactoring work will be done in TEPHRA-262 > Setup pro

[jira] [Created] (TEPHRA-262) Refactoring to remove Security dependencies from the Pruning classes

Andreas Neumann created TEPHRA-262: -- Summary: Refactoring to remove Security dependencies from the Pruning classes Key: TEPHRA-262 URL: https://issues.apache.org/jira/browse/TEPHRA-262 Project

[jira] [Updated] (TEPHRA-243) Fix concurrency issues in Transaction log writer; also improve the logging

[ https://issues.apache.org/jira/browse/TEPHRA-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Neumann updated TEPHRA-243: --- Summary: Fix concurrency issues in Transaction log writer; also improve the logging

[jira] [Resolved] (TEPHRA-243) Fix concurrency issues in Transaction log writer; also improve the logging

[ https://issues.apache.org/jira/browse/TEPHRA-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Neumann resolved TEPHRA-243. Resolution: Fixed > Fix concurrency issues in Transaction log writer; also impr

[jira] [Resolved] (TEPHRA-261) Make TransactionSystemTest.getCommonConfiguration() protected

[ https://issues.apache.org/jira/browse/TEPHRA-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Neumann resolved TEPHRA-261. Resolution: Fixed > Make TransactionSystemTest.getCommonConfiguration() protec

[jira] [Created] (TEPHRA-261) Make TransactionSystemTest.getCommonConfiguration() protected

Andreas Neumann created TEPHRA-261: -- Summary: Make TransactionSystemTest.getCommonConfiguration() protected Key: TEPHRA-261 URL: https://issues.apache.org/jira/browse/TEPHRA-261 Project: Tephra

[jira] [Resolved] (TEPHRA-258) Improve log message for Thrift client connection

[ https://issues.apache.org/jira/browse/TEPHRA-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Neumann resolved TEPHRA-258. Resolution: Fixed > Improve log message for Thrift client connect

[jira] [Created] (TEPHRA-259) Exception handlers should only log an exception if they don't rethrow it

Andreas Neumann created TEPHRA-259: -- Summary: Exception handlers should only log an exception if they don't rethrow it Key: TEPHRA-259 URL: https://issues.apache.org/jira/browse/TEPHRA-259 Project

[jira] [Commented] (TEPHRA-258) Improve log message for Thrift client connection

[ https://issues.apache.org/jira/browse/TEPHRA-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16162310#comment-16162310 ] Andreas Neumann commented on TEPHRA-258: Also, the AbstractClientProvider has very verbose logging

[jira] [Created] (TEPHRA-258) Improve log message for Thrift client connection

Andreas Neumann created TEPHRA-258: -- Summary: Improve log message for Thrift client connection Key: TEPHRA-258 URL: https://issues.apache.org/jira/browse/TEPHRA-258 Project: Tephra Issue

[jira] [Created] (TEPHRA-256) Transaction Log Synchronization is overly complex and too restrictive

Andreas Neumann created TEPHRA-256: -- Summary: Transaction Log Synchronization is overly complex and too restrictive Key: TEPHRA-256 URL: https://issues.apache.org/jira/browse/TEPHRA-256 Project

[jira] [Created] (TEPHRA-255) PruneUpperBoundWriterSupplierTest is flaky

Andreas Neumann created TEPHRA-255: -- Summary: PruneUpperBoundWriterSupplierTest is flaky Key: TEPHRA-255 URL: https://issues.apache.org/jira/browse/TEPHRA-255 Project: Tephra Issue Type

[jira] [Resolved] (TEPHRA-253) TransactionProcessorTest is sometimes flaky

[ https://issues.apache.org/jira/browse/TEPHRA-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Neumann resolved TEPHRA-253. Resolution: Fixed > TransactionProcessorTest is sometimes fl

[jira] [Commented] (TEPHRA-253) TransactionProcessorTest is sometimes flaky

[ https://issues.apache.org/jira/browse/TEPHRA-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16160097#comment-16160097 ] Andreas Neumann commented on TEPHRA-253: Fix is to wait with the flush until the transaction state

[jira] [Updated] (TEPHRA-253) TransactionProcessorTest is sometimes flaky

[ https://issues.apache.org/jira/browse/TEPHRA-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Neumann updated TEPHRA-253: --- Fix Version/s: 0.13.0-incubating > TransactionProcessorTest is sometimes fl

[jira] [Commented] (TEPHRA-253) TransactionProcessorTest is sometimes flaky

[ https://issues.apache.org/jira/browse/TEPHRA-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16160061#comment-16160061 ] Andreas Neumann commented on TEPHRA-253: Suspicion confirmed. After changing travis to dump

[jira] [Assigned] (TEPHRA-253) TransactionProcessorTest is sometimes flaky

[ https://issues.apache.org/jira/browse/TEPHRA-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Neumann reassigned TEPHRA-253: -- Assignee: Andreas Neumann (was: Poorna Chandra) > TransactionProcessorT

  1   2   >