+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
When you set autoCommit to true on a connection a commit is a called after
each statement is executed.
If you want to commit a batch of rows from the client set auto commit to
false and call commit on the connection when you are ready.
On Thu, Jul 6, 2017 at 1:10 PM, Poorna Chandra
+1
Ran Phoenix tests and verified there are no regressions.
Thanks,
Thomas
On Wed, May 24, 2017 at 12:22 PM, Poorna Chandra wrote:
> +1
>
> - Checked build and test
> - Checked signature and checksums
> - Checked LICENSE, NOTICE and DISCLAIMER
> - Checked release tag and
+1 . Ran Phoenix tests and verified that there were no failures.
On Tue, Feb 14, 2017 at 4:54 PM, Alan Gates wrote:
> +1. Checked the signatures, checked the LICENSE, NOTICE, and DISCLAIMER
> files. Checked to be sure there were no binary files. Did a build with a
>
[
https://issues.apache.org/jira/browse/TEPHRA-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas D'Silva updated TEPHRA-208:
--
Attachment: TEPHRA-208.patch
> Compaction removes rows incorrectly for family dele
Thomas D'Silva created TEPHRA-208:
-
Summary: Compaction removes rows incorrectly for family deletes
with column level conflict detection
Key: TEPHRA-208
URL: https://issues.apache.org/jira/browse/TEPHRA-208
this line after setting the tx snapshot dir:
>
> conf.setLong(TxConstants.Manager.CFG_TX_SNAPSHOT_INTERVAL, 2L);
>
> And the test passes now. The coprocessors use the snapshot data to clean up
> data.
>
> Thanks,
> Gokul
>
> On Wed, Jan 4, 2017 at 4:24 PM, Tho
Hi,
I am trying to debug a Phoenix test failure that deletes rows from a
transactional table and then runs major compaction to remove the deleted
rows. The rows are not getting removed after major compaction is run. I
think it might be related to my test setup. I have attached a patch that