[GitHub] incubator-omid pull request #21: [OMID-87] Fix BatchPool initialization

2018-02-01 Thread francisco-perez-sorrosal 
GitHub user francisco-perez-sorrosal opened a pull request:

https://github.com/apache/incubator-omid/pull/21

[OMID-87] Fix BatchPool initialization

Added config.setMaxIdle(poolSize + 1) to the configuration.
Added some tests to prove it works.

Change-Id: Idc32ffa8472e87defdc540abbb901cfba700eb05

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/francisco-perez-sorrosal/incubator-omid 
omid-87

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-omid/pull/21.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #21


commit 7ccd2e0751e9fa8de765feda8a246fb927b5b670
Author: Francisco Perez-Sorrosal 
Date:   2018-02-01T23:19:09Z

[OMID-87] Fix BatchPool initialization

Added config.setMaxIdle(poolSize + 1) to the configuration.
Added some tests to prove it works.

Change-Id: Idc32ffa8472e87defdc540abbb901cfba700eb05




---

[jira] [Updated] (OMID-88) Add 0.9.0.0 and phoenix-integration branches to Travis

2018-02-01 Thread Francisco Perez-Sorrosal (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OMID-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francisco Perez-Sorrosal updated OMID-88:
-
Affects Version/s: (was: 0.9.0.0)

> Add 0.9.0.0 and phoenix-integration branches to Travis
> --
>
> Key: OMID-88
> URL: https://issues.apache.org/jira/browse/OMID-88
> Project: Apache Omid
>  Issue Type: Bug
>Reporter: Francisco Perez-Sorrosal
>Assignee: Francisco Perez-Sorrosal
>Priority: Major
>  Labels: branches, omid, travis
> Fix For: 0.9.0.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (OMID-88) Add 0.9.0.0 and phoenix-integration branches to Travis

2018-02-01 Thread Francisco Perez-Sorrosal (JIRA) 
Francisco Perez-Sorrosal created OMID-88:


 Summary: Add 0.9.0.0 and phoenix-integration branches to Travis
 Key: OMID-88
 URL: https://issues.apache.org/jira/browse/OMID-88
 Project: Apache Omid
  Issue Type: Bug
Affects Versions: 0.9.0.0
Reporter: Francisco Perez-Sorrosal
Assignee: Francisco Perez-Sorrosal
 Fix For: 0.9.0.0






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] incubator-omid pull request #20: [OMID-85] Writing directly to HBase using s...

2018-02-01 Thread ohadshacham 
GitHub user ohadshacham opened a pull request:

https://github.com/apache/incubator-omid/pull/20

[OMID-85] Writing directly to HBase using specific version marks the …

…write as a write that was done by a specific transaction.

However, due to lack of shadow cells, getting the commit timestamp of the 
transaction can be done only by access the commit table.
The motivation of this feature is to add the shadow cells during the write 
and save the commit table access.
This feature is required by Apache Phoenix that during index creation adds 
the data table's entries,
appeared before creation, to the index. In this case, the version and the 
commit timestamp should be the fence id and therefore, a direct write to HBase 
with the addition of shadow cells is required.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ohadshacham/incubator-omid AutoCommit

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-omid/pull/20.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #20


commit 462984833997c6192ae30788f5f7a3d866d41dce
Author: Ohad Shacham 
Date:   2018-02-01T15:13:08Z

[OMID-85] Writing directly to HBase using specific version marks the write 
as a write that was done by a specific transaction.
However, due to lack of shadow cells, getting the commit timestamp of the 
transaction can be done only by access the commit table.
The motivation of this feature is to add the shadow cells during the write 
and save the commit table access.
This feature is required by Apache Phoenix that during index creation adds 
the data table's entries,
appeared before creation, to the index. In this case, the version and the 
commit timestamp should be the fence id and therefore, a direct write to HBase 
with the addition of shadow cells is required.




---

[GitHub] incubator-omid pull request #19: [OMID-84] Today, all the writes done by a t...

2018-02-01 Thread ohadshacham 
GitHub user ohadshacham opened a pull request:

https://github.com/apache/incubator-omid/pull/19

[OMID-84] Today, all the writes done by a transaction are taking part…

… in conflict analysis. The purpose of this feature is to let the user 
decide for each write, whether it should take part in the conflict analysis.

The motivation infers from Apache Phoenix that utilizes this feature when 
writing to the secondary index and also when writing to the data table for 
immutable tables (each key is added once and is not modified).

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ohadshacham/incubator-omid OMID-84-from-master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-omid/pull/19.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #19


commit 8fad7b57e3bb6ce6b69e753252c43c33af5a8eeb
Author: Ohad Shacham 
Date:   2018-01-31T14:52:43Z

[OMID-84] Today, all the writes done by a transaction are taking part in 
conflict analysis. The purpose of this feature is to let the user decide for 
each write, whether it should take part in the conflict analysis.
The motivation infers from Apache Phoenix that utilizes this feature when 
writing to the secondary index and also when writing to the data table for 
immutable tables (each key is added once and is not modified).




---

[jira] [Commented] (OMID-85) Autocommit

2018-02-01 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/OMID-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16348717#comment-16348717
 ] 

ASF GitHub Bot commented on OMID-85:


GitHub user ohadshacham opened a pull request:

https://github.com/apache/incubator-omid/pull/20

[OMID-85] Writing directly to HBase using specific version marks the …

…write as a write that was done by a specific transaction.

However, due to lack of shadow cells, getting the commit timestamp of the 
transaction can be done only by access the commit table.
The motivation of this feature is to add the shadow cells during the write 
and save the commit table access.
This feature is required by Apache Phoenix that during index creation adds 
the data table's entries,
appeared before creation, to the index. In this case, the version and the 
commit timestamp should be the fence id and therefore, a direct write to HBase 
with the addition of shadow cells is required.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ohadshacham/incubator-omid AutoCommit

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-omid/pull/20.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #20


commit 462984833997c6192ae30788f5f7a3d866d41dce
Author: Ohad Shacham 
Date:   2018-02-01T15:13:08Z

[OMID-85] Writing directly to HBase using specific version marks the write 
as a write that was done by a specific transaction.
However, due to lack of shadow cells, getting the commit timestamp of the 
transaction can be done only by access the commit table.
The motivation of this feature is to add the shadow cells during the write 
and save the commit table access.
This feature is required by Apache Phoenix that during index creation adds 
the data table's entries,
appeared before creation, to the index. In this case, the version and the 
commit timestamp should be the fence id and therefore, a direct write to HBase 
with the addition of shadow cells is required.




> Autocommit
> --
>
> Key: OMID-85
> URL: https://issues.apache.org/jira/browse/OMID-85
> Project: Apache Omid
>  Issue Type: Sub-task
>Reporter: Ohad Shacham
>Assignee: Ohad Shacham
>Priority: Major
>
> Writing directly to HBase using specific version marks the write as a write 
> that was done by a specific transaction. However, due to lack of shadow 
> cells, getting the commit timestamp of the transaction can be done only by 
> access the commit table. The motivation of this feature is to add the shadow 
> cells during the write and save the commit table access.
> This feature is required by Apache Phoenix that during index creation adds 
> the data table's entries, appeared before creation, to the index. In this 
> case, the version and the commit timestamp should be the fence id and 
> therefore, a direct write to HBase with the addition of shadow cells is 
> required.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OMID-85) Autocommit

2018-02-01 Thread Ohad Shacham (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OMID-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ohad Shacham updated OMID-85:
-
Summary: Autocommit  (was: Direct HBase write with shadow cells)

> Autocommit
> --
>
> Key: OMID-85
> URL: https://issues.apache.org/jira/browse/OMID-85
> Project: Apache Omid
>  Issue Type: Sub-task
>Reporter: Ohad Shacham
>Assignee: Ohad Shacham
>Priority: Major
>
> Writing directly to HBase using specific version marks the write as a write 
> that was done by a specific transaction. However, due to lack of shadow 
> cells, getting the commit timestamp of the transaction can be done only by 
> access the commit table. The motivation of this feature is to add the shadow 
> cells during the write and save the commit table access.
> This feature is required by Apache Phoenix that during index creation adds 
> the data table's entries, appeared before creation, to the index. In this 
> case, the version and the commit timestamp should be the fence id and 
> therefore, a direct write to HBase with the addition of shadow cells is 
> required.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OMID-84) Conflict free writes

2018-02-01 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/OMID-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16348171#comment-16348171
 ] 

ASF GitHub Bot commented on OMID-84:


GitHub user ohadshacham opened a pull request:

https://github.com/apache/incubator-omid/pull/19

[OMID-84] Today, all the writes done by a transaction are taking part…

… in conflict analysis. The purpose of this feature is to let the user 
decide for each write, whether it should take part in the conflict analysis.

The motivation infers from Apache Phoenix that utilizes this feature when 
writing to the secondary index and also when writing to the data table for 
immutable tables (each key is added once and is not modified).

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ohadshacham/incubator-omid OMID-84-from-master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-omid/pull/19.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #19


commit 8fad7b57e3bb6ce6b69e753252c43c33af5a8eeb
Author: Ohad Shacham 
Date:   2018-01-31T14:52:43Z

[OMID-84] Today, all the writes done by a transaction are taking part in 
conflict analysis. The purpose of this feature is to let the user decide for 
each write, whether it should take part in the conflict analysis.
The motivation infers from Apache Phoenix that utilizes this feature when 
writing to the secondary index and also when writing to the data table for 
immutable tables (each key is added once and is not modified).




> Conflict free writes
> 
>
> Key: OMID-84
> URL: https://issues.apache.org/jira/browse/OMID-84
> Project: Apache Omid
>  Issue Type: Sub-task
>Reporter: Ohad Shacham
>Assignee: Ohad Shacham
>Priority: Major
>
> Today, all the writes done by a transaction are taking part in conflict 
> analysis. The purpose of this feature is to let the user decide for each 
> write, whether it should take part in the conflict analysis. 
> The motivation infers from Apache Phoenix that utilizes this feature when 
> writing to the secondary index and also when writing to the data table for 
> immutable tables (each key is added once and is not modified).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)