[GitHub] incubator-omid pull request #25: [OMID-93] mark mutation as committed

[ohadshacham]

Github user ohadshacham closed the pull request at:

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


---

[GitHub] incubator-omid pull request #26: A bug fix in [OMID-74].

[ohadshacham]

Github user ohadshacham closed the pull request at:

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


---

[jira] [Resolved] (OMID-94) Tune Omid for Phoenix testing environment

[Ohad Shacham (JIRA)]

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

Ohad Shacham resolved OMID-94.
--
Resolution: Fixed

> Tune Omid for Phoenix testing environment
> -
>
> Key: OMID-94
> URL: https://issues.apache.org/jira/browse/OMID-94
> Project: Apache Omid
>  Issue Type: Sub-task
>Reporter: Ohad Shacham
>Assignee: Ohad Shacham
>Priority: Major
> Attachments: OMID-94.v0.patch
>
>
> Changing accessibility levels and other small modifications are needed for 
> running Phoenix testing environment with Omid as its transaction processor.



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

[jira] [Commented] (OMID-94) Tune Omid for Phoenix testing environment

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OMID-94:


Github user ohadshacham closed the pull request at:

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


> Tune Omid for Phoenix testing environment
> -
>
> Key: OMID-94
> URL: https://issues.apache.org/jira/browse/OMID-94
> Project: Apache Omid
>  Issue Type: Sub-task
>Reporter: Ohad Shacham
>Assignee: Ohad Shacham
>Priority: Major
> Attachments: OMID-94.v0.patch
>
>
> Changing accessibility levels and other small modifications are needed for 
> running Phoenix testing environment with Omid as its transaction processor.



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

[jira] [Updated] (OMID-94) Tune Omid for Phoenix testing environment

[Ohad Shacham (JIRA)]

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

Ohad Shacham updated OMID-94:
-
Attachment: OMID-94.v0.patch

> Tune Omid for Phoenix testing environment
> -
>
> Key: OMID-94
> URL: https://issues.apache.org/jira/browse/OMID-94
> Project: Apache Omid
>  Issue Type: Sub-task
>Reporter: Ohad Shacham
>Assignee: Ohad Shacham
>Priority: Major
> Attachments: OMID-94.v0.patch
>
>
> Changing accessibility levels and other small modifications are needed for 
> running Phoenix testing environment with Omid as its transaction processor.



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

[jira] [Commented] (OMID-93) Mark mutation as committed

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OMID-93:


Github user ohadshacham closed the pull request at:

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


> Mark mutation as committed
> --
>
> Key: OMID-93
> URL: https://issues.apache.org/jira/browse/OMID-93
> Project: Apache Omid
>  Issue Type: Sub-task
>Reporter: Ohad Shacham
>Assignee: Ohad Shacham
>Priority: Major
> Attachments: OMID-93.v1.patch
>
>
> This task requires the addition of commit metadata (shadow cells) to an 
> existing mutation. This feature is required by Apache Phoenix both for local 
> index population and update. 



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

[jira] [Closed] (OMID-93) Mark mutation as committed

[Ohad Shacham (JIRA)]

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

Ohad Shacham closed OMID-93.


> Mark mutation as committed
> --
>
> Key: OMID-93
> URL: https://issues.apache.org/jira/browse/OMID-93
> Project: Apache Omid
>  Issue Type: Sub-task
>Reporter: Ohad Shacham
>Assignee: Ohad Shacham
>Priority: Major
> Attachments: OMID-93.v1.patch
>
>
> This task requires the addition of commit metadata (shadow cells) to an 
> existing mutation. This feature is required by Apache Phoenix both for local 
> index population and update. 



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

[jira] [Updated] (OMID-93) Mark mutation as committed

[Ohad Shacham (JIRA)]

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

Ohad Shacham updated OMID-93:
-
Attachment: OMID-93.v1.patch

> Mark mutation as committed
> --
>
> Key: OMID-93
> URL: https://issues.apache.org/jira/browse/OMID-93
> Project: Apache Omid
>  Issue Type: Sub-task
>Reporter: Ohad Shacham
>Assignee: Ohad Shacham
>Priority: Major
> Attachments: OMID-93.v1.patch
>
>
> This task requires the addition of commit metadata (shadow cells) to an 
> existing mutation. This feature is required by Apache Phoenix both for local 
> index population and update. 



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

[jira] [Commented] (OMID-74) Efficient column family deletion in Row level conflict analysis

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OMID-74:


Github user ohadshacham closed the pull request at:

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


> Efficient column family deletion in Row level conflict analysis
> ---
>
> Key: OMID-74
> URL: https://issues.apache.org/jira/browse/OMID-74
> Project: Apache Omid
>  Issue Type: Sub-task
>Reporter: Ohad Shacham
>Assignee: Ohad Shacham
>Priority: Major
> Attachments: OMID-74.v2.patch
>
>
> The idea is to use a qualifier to denote that all the columns of a specific 
> family were deleted. 
> Current implementation reads from HBase the entire family and then writes a 
> tombstone to each one of its cells. The new implementation does not need to 
> perform the read and only writes the qualifier to denote that the family was 
> deleted. This is true only for Row level conflict detection since in Cell 
> level we need to read the cells and add these to the write set.



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

[jira] [Commented] (OMID-70) World time based timestamp generator

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OMID-70:


Github user ohadshacham closed the pull request at:

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


> World time based timestamp generator
> 
>
> Key: OMID-70
> URL: https://issues.apache.org/jira/browse/OMID-70
> Project: Apache Omid
>  Issue Type: Sub-task
>Reporter: Ohad Shacham
>Assignee: Ohad Shacham
>Priority: Major
> Attachments: OMID-70.v2.patch
>
>
> Adding world time base timestamp generator. The generator should maintain 
> monotonicity and persists the maximal timestamp in each interval (for high 
> availability).
> 
> The motivation for this feature is the integration with Apache Phoenix.
> Phoenix's customers requires mapping from timestamp to world time in order to 
> debug their logs.



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

[jira] [Resolved] (OMID-74) Efficient column family deletion in Row level conflict analysis

[Ohad Shacham (JIRA)]

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

Ohad Shacham resolved OMID-74.
--
Resolution: Fixed

> Efficient column family deletion in Row level conflict analysis
> ---
>
> Key: OMID-74
> URL: https://issues.apache.org/jira/browse/OMID-74
> Project: Apache Omid
>  Issue Type: Sub-task
>Reporter: Ohad Shacham
>Assignee: Ohad Shacham
>Priority: Major
> Attachments: OMID-74.v2.patch
>
>
> The idea is to use a qualifier to denote that all the columns of a specific 
> family were deleted. 
> Current implementation reads from HBase the entire family and then writes a 
> tombstone to each one of its cells. The new implementation does not need to 
> perform the read and only writes the qualifier to denote that the family was 
> deleted. This is true only for Row level conflict detection since in Cell 
> level we need to read the cells and add these to the write set.



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

[jira] [Closed] (OMID-74) Efficient column family deletion in Row level conflict analysis

[Ohad Shacham (JIRA)]

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

Ohad Shacham closed OMID-74.


> Efficient column family deletion in Row level conflict analysis
> ---
>
> Key: OMID-74
> URL: https://issues.apache.org/jira/browse/OMID-74
> Project: Apache Omid
>  Issue Type: Sub-task
>Reporter: Ohad Shacham
>Assignee: Ohad Shacham
>Priority: Major
> Attachments: OMID-74.v2.patch
>
>
> The idea is to use a qualifier to denote that all the columns of a specific 
> family were deleted. 
> Current implementation reads from HBase the entire family and then writes a 
> tombstone to each one of its cells. The new implementation does not need to 
> perform the read and only writes the qualifier to denote that the family was 
> deleted. This is true only for Row level conflict detection since in Cell 
> level we need to read the cells and add these to the write set.



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

[jira] [Updated] (OMID-74) Efficient column family deletion in Row level conflict analysis

[Ohad Shacham (JIRA)]

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

Ohad Shacham updated OMID-74:
-
Attachment: OMID-74.v2.patch

> Efficient column family deletion in Row level conflict analysis
> ---
>
> Key: OMID-74
> URL: https://issues.apache.org/jira/browse/OMID-74
> Project: Apache Omid
>  Issue Type: Sub-task
>Reporter: Ohad Shacham
>Assignee: Ohad Shacham
>Priority: Major
> Attachments: OMID-74.v2.patch
>
>
> The idea is to use a qualifier to denote that all the columns of a specific 
> family were deleted. 
> Current implementation reads from HBase the entire family and then writes a 
> tombstone to each one of its cells. The new implementation does not need to 
> perform the read and only writes the qualifier to denote that the family was 
> deleted. This is true only for Row level conflict detection since in Cell 
> level we need to read the cells and add these to the write set.



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

[jira] [Resolved] (OMID-70) World time based timestamp generator

[Ohad Shacham (JIRA)]

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

Ohad Shacham resolved OMID-70.
--
Resolution: Fixed

> World time based timestamp generator
> 
>
> Key: OMID-70
> URL: https://issues.apache.org/jira/browse/OMID-70
> Project: Apache Omid
>  Issue Type: Sub-task
>Reporter: Ohad Shacham
>Assignee: Ohad Shacham
>Priority: Major
> Attachments: OMID-70.v2.patch
>
>
> Adding world time base timestamp generator. The generator should maintain 
> monotonicity and persists the maximal timestamp in each interval (for high 
> availability).
> 
> The motivation for this feature is the integration with Apache Phoenix.
> Phoenix's customers requires mapping from timestamp to world time in order to 
> debug their logs.



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

[jira] [Closed] (OMID-70) World time based timestamp generator

[Ohad Shacham (JIRA)]

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

Ohad Shacham closed OMID-70.


> World time based timestamp generator
> 
>
> Key: OMID-70
> URL: https://issues.apache.org/jira/browse/OMID-70
> Project: Apache Omid
>  Issue Type: Sub-task
>Reporter: Ohad Shacham
>Assignee: Ohad Shacham
>Priority: Major
> Attachments: OMID-70.v2.patch
>
>
> Adding world time base timestamp generator. The generator should maintain 
> monotonicity and persists the maximal timestamp in each interval (for high 
> availability).
> 
> The motivation for this feature is the integration with Apache Phoenix.
> Phoenix's customers requires mapping from timestamp to world time in order to 
> debug their logs.



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

Re: [VOTE] Omid release branch 0.9.0.0 - Release candidate 1

[Ohad Shacham]

Thanks Alan. I'll start a vote in incubator.

On Wed, Mar 21, 2018 at 9:46 PM, Alan Gates  wrote:

> +1.  Checked DISCLAIMER, LICENSE, and NOTICE files, did a rat build,
> checked that there weren't any binaries in the release.
>
> One note for future releases, Apache has now changed its guidelines on
> hashes for the releases.  It now recommends against md5 and requires SHA
> (256 or greater I think).  I don't think you need to reroll this release,
> but it should be changed in the next release.
>
> Alan.
>
> On Sun, Mar 18, 2018 at 1:03 AM, Ohad Shacham 
> wrote:
>
> >  Thanks James and Flavio. I will take your comments into account.
> > According to https://www.apache.org/foundation/voting.htmlwe need at
> > least three PMC members to vote and currently only two did.
> > Could another PMC member please check the release and vote?
> > Thanks,Ohad
> >
> > On Friday, March 16, 2018, 2:09:53 PM GMT+2, Flavio Junqueira <
> > f...@apache.org> wrote:
> >
> >  +1, I built from sources and built fine for me. I checked LICENSE and
> > NOTICE, and ran the rat tool.
> >
> > One point that I'm wondering about is whether there has been an
> > investigation of the dependencies with respect to licenses. It called my
> > attention that both LICENSE and NOTICE files are pretty bare-bones. If
> you
> > haven't, it is worth going through this exercise and checking this page:
> >
> > http://www.apache.org/dev/licensing-howto.html <
> http://www.apache.org/dev/
> > licensing-howto.html>
> >
> > -Flavio
> >
> > > On 14 Mar 2018, at 18:35, James Taylor  wrote:
> > >
> > > +1 to the release. All unit tests pass with both "mvn package
> -Dhbase-1"
> > > and "mvn package -Dhbase-0"
> > >
> > > Some minor nits to consider for next time:
> > > - have a default profile so that mvn package works out of the box
> > > - separate integration tests (that require spinning up a mini cluster)
> > from
> > > other faster running tests. Run the faster unit tests during mvn
> package
> > > and run integration tests during mvn verify.
> > > -  put newlines in your email so that the URLs can be clicked on.
> > Instead,
> > > the URLs are running together with the next line.
> > >
> > > Thanks,
> > > James
> > >
> > > On Tue, Mar 13, 2018 at 12:46 PM, Ohad Shacham  >
> > > wrote:
> > >
> > >> Add  -Phbase-1 to your maven command. It should solve the error.
> > >>
> > >>
> > >> Sent from Yahoo Mail for iPhone
> > >>
> > >>
> > >> On Tuesday, March 13, 2018, 21:43, James Taylor <
> jamestay...@apache.org
> > >
> > >> wrote:
> > >>
> > >> Rat check passes when I run "mvn -Prelease_profile -Phbase-1 install"
> > which
> > >> is good.
> > >>
> > >> However, "mvn clean install" fails (on my Mac) with the following
> error:
> > >>
> > >> [INFO]
> > >> 
> > 
> > >> [INFO] Building HBase tools 0.9.0.0
> > >> [INFO]
> > >> 
> > 
> > >> [INFO]
> > >> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @
> > omid-hbase-tools
> > >> ---
> > >> [INFO] Deleting
> > >> /Users/jtaylor/dev/apache/apache-omid-incubating-0.9.0.
> > >> 0-src/hbase-tools/target
> > >> [INFO]
> > >> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @
> > >> omid-hbase-tools ---
> > >> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> > >> [INFO] skip non existing resourceDirectory
> > >> /Users/jtaylor/dev/apache/apache-omid-incubating-0.9.0.
> > >> 0-src/hbase-tools/src/main/resources
> > >> [INFO]
> > >> [INFO] --- maven-compiler-plugin:3.5:compile (default-compile) @
> > >> omid-hbase-tools ---
> > >> [INFO] Changes detected - recompiling the module!
> > >> [INFO] Compiling 1 source file to
> > >> /Users/jtaylor/dev/apache/apache-omid-incubating-0.9.0.
> > >> 0-src/hbase-tools/target/classes
> > >> [INFO] -
> > >> [ERROR] COMPILATION ERROR :
> > >> [INFO] -
> > >> [ERROR]
> > >> /Users/jtaylor/dev/apache/apache-omid-incubating-0.9.0.
> > >> 0-src/hbase-tools/src/main/java/org/apache/omid/tools/
> > >> hbase/OmidTableManager.java:[33,23]
> > >> cannot find symbol
> > >>  symbol:  class HBaseShims
> > >>  location: package org.apache.omid
> > >> [ERROR]
> > >> /Users/jtaylor/dev/apache/apache-omid-incubating-0.9.0.
> > >> 0-src/hbase-tools/src/main/java/org/apache/omid/tools/
> > >> hbase/OmidTableManager.java:[153,13]
> > >> cannot find symbol
> > >>  symbol:  variable HBaseShims
> > >>  location: class org.apache.omid.tools.hbase.OmidTableManager
> > >> [INFO] 2 errors
> > >>
> > >>
> > >> On Tue, Mar 13, 2018 at 2:17 AM, Ohad Shacham  >
> > >> wrote:
> > >>
> > >>> Hi All,
> > >>>
> > >>> I would like to call a vote to release Apache Omid (Incubator)
> 0.9.0.0,
> > >>>