Re: [VOTE] Graduate into the Phoenix project
+1 On Wed, Oct 30, 2019 at 12:35 PM James Taylor wrote: > +1 > > On Wed, Oct 30, 2019 at 12:15 PM Alan Gates wrote: > > > I propose that the Omid 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 > > Omid repo. Any Omid 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] (OMID-121) Apache Incubator report - December 2018
[ https://issues.apache.org/jira/browse/OMID-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16707670#comment-16707670 ] Francisco Perez-Sorrosal commented on OMID-121: --- Just as a reminder for future reports, Thejas Nair manifested in September 15th that he would like to resign as mentor of Omid as the project had already enough mentors. > Apache Incubator report - December 2018 > --- > > Key: OMID-121 > URL: https://issues.apache.org/jira/browse/OMID-121 > Project: Apache Omid > Issue Type: Task >Reporter: Ohad Shacham >Assignee: Ohad Shacham >Priority: Major > > Provide a report for September 1, 2018 - November 31, 2018 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: [VOTE] Omid release branch 1.0.0 - Release candidate 0
+1 On Thursday, November 15, 2018, 12:32:40 AM PST, Ohad Shacham wrote: Hi All, We would like to call a vote to release Apache Omid (Incubator) 1.0.0, release candidate #0. Links to various release artifacts are given below. Please review and vote. The vote will be open for at least 72 hours and until necessary number of votes are reached. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here is my +1 Release notes for the 1.0.0 release:https://dist.apache.org/repos/dist/dev/incubator/omid/1.0.0-rc0/RELEASE_NOTES.html Git tag for the release: https://git-wip-us.apache.org/repos/asf/incubator-omid.git/?p=incubator-omid.git;a=tag;h=14d5cb2d899ef381be40edc6d95aede50bb396ea Sources for the release: https://dist.apache.org/repos/dist/dev/incubator/omid/1.0.0-rc0/apache-omid-incubating-1.0.0-src.tar.gz Source release verification: PGP Signature: https://dist.apache.org/repos/dist/dev/incubator/omid/1.0.0-rc0/apache-omid-incubating-1.0.0-src.tar.gz.asc SHA512 Hash: https://dist.apache.org/repos/dist/dev/incubator/omid/1.0.0-rc0/apache-omid-incubating-1.0.0-src.tar.gz.sha512 Keys to verify the signature of the release artifact are available at: https://dist.apache.org/repos/dist/dev/incubator/omid/1.0.0-rc0/KEYS Thanks, Yoni and Ohad
Re: Webpage git
Hi Ohad, Maven is a project management tool that follows the premise of "convention over configuration" in contrast to "configuration over convention" (e.g. gradle). This means basically that there's a predefined project lifecycle that the project stakeholders must adhere to (See https://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html) This lifecycle includes the well-known stages/maven-targets of clean, compile, build, package, etc... In Maven, as part of the stages of the project lifecycle, there's one related to the project documentation/website generation. This is related to the Maven target/plugin "site" that I mentioned in the previous email. The documentation for that, is the official in Maven, so that's why I pointed out to that documentation in the previous email. This is the explicit link for the "site" target of Maven in the official Maven documentation: https://maven.apache.org/guides/mini/guide-site.html As I said, the project documentation of the Omid website is in under "doc/site" folder of the project and it follows the description in the official Maven documentation (There's no specific config that was used for that.) There, you can found the site.xml file (site descriptor) that describes the website structure at a general level, and the "markdown" folder which includes the different pages I created with the documentation for Omid (Those pages should have been also updated when you do a release if there were changes) I chose Markdown files to document the project because they are standard and can be re-used with different documentation engines if you don't like the standard one provided by Maven. Regarding the distributionManagement XML tag hurting the deployment to Nexus, I didn't found any problems last time. The distributionManagement XML tag is part of the Maven site as you can see in the Maven documentation.Having said that, if you prefer to generate the website with a different tool than the standard, feel free to use it. As I said the main documentation is in Markdown files and those are processed by almost all doc engines out there. You can ask the Phoenix guys for the tool that they are using for generating the website. Note: I'm sending this to the Omid dev group as someone can find it interesting. Thanks, Francisco P.S. I've collected some commands from my history that I was using at that time just FYI. They are pretty standard as you can see: 1303 mvn site:stage -Ddependency.locations.enabled=false 1432 mvn clean site:site -Ddependency.locations.enabled=false 2952 mvn clean site:site2953 mvn site:deploy On Thursday, July 12, 2018, 2:08:00 AM PDT, Ohad Shacham wrote: Hi Francisco, Thanks! Any idea how this thing works? :) Is there any documentation? I found info about wagon, however, I am not sure how the new webpage can be synthesis and upload. I also cloned the site git repo and it seems that the version there is older than the one on the webpage. BTW, putting this info under the distributionManagement hurts the option to deploy the release to Nexus. Thx, Ohad On Wed, Jul 11, 2018 at 9:31 PM, Francisco Perez-Sorrosal wrote: Hi Ohad, Sorry, I didn't see the message and Kostas just told me. All the information related to the website distribution (including the repository) is in the pom.xml file (see the distribution management section). It's released through Maven (see the site and wagon plugins doc) https://github.com/ apache/incubator-omid/blob/ master/pom.xml All the documentation of the website is in under doc/site folder of the project. Thanks, FranciscoOn Sunday, July 8, 2018, 2:15:07 AM PDT, Ohad Shacham wrote: Hey Francisco, Do you have it? I want to update the webpage. Thx,Ohad On Fri, Jun 22, 2018 at 9:04 PM, Ohad Shacham wrote: Man Could you please send me the repository for the website? I would like to change the version to 0.9.0.0. ThxOhad Sent from Yahoo Mail for iPhone
[jira] [Commented] (OMID-101) Provide Apache Incubator Report June 2018
[ https://issues.apache.org/jira/browse/OMID-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16506616#comment-16506616 ] Francisco Perez-Sorrosal commented on OMID-101: --- Report updated with James' comments in https://wiki.apache.org/incubator/June2018 > Provide Apache Incubator Report June 2018 > - > > Key: OMID-101 > URL: https://issues.apache.org/jira/browse/OMID-101 > Project: Apache Omid > Issue Type: Task > Reporter: Francisco Perez-Sorrosal > Assignee: Francisco Perez-Sorrosal >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OMID-101) Provide Apache Incubator Report June 2018
[ https://issues.apache.org/jira/browse/OMID-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16506438#comment-16506438 ] Francisco Perez-Sorrosal commented on OMID-101: --- Added draft report to: https://wiki.apache.org/incubator/June2018 Please feel free to add/change info on the draft > Provide Apache Incubator Report June 2018 > - > > Key: OMID-101 > URL: https://issues.apache.org/jira/browse/OMID-101 > Project: Apache Omid > Issue Type: Task > Reporter: Francisco Perez-Sorrosal > Assignee: Francisco Perez-Sorrosal >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OMID-101) Provide Apache Incubator Report June 2018
[ https://issues.apache.org/jira/browse/OMID-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16506436#comment-16506436 ] Francisco Perez-Sorrosal commented on OMID-101: --- Draft: - Omid Omid is a flexible, reliable, high performant and scalable ACID transactional framework that allows client applications to execute transactions on top of MVCC key/value-based NoSQL datastores (currently Apache HBase) providing Snapshot Isolation guarantees on the accessed data. Omid has been incubating since 2016-03-28. Three most important issues to address in the move towards graduation: 1. Boost project dissemination in the Apache community. 2. Collaborate/integrate Omid with other Apache projects. 3. Get positive feedback from other projects currently in Apache. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? N/A How has the community developed since the last report? Continue integration with Apache Phoenix. Pinterest exploring to use Omid in production. How has the project developed since the last report? Preparing 0.9.0 version. Solved issues related to legal stuff. Quarter Stats (from: 2017-03-01 to: 2018-05-31): +-+ | Metric | counts | +-+ | # of msgs in dev list | 192 | | Active Contributors (incl mentors)| 8 | | Jira New Issues | 10 | | Resolved Issues | 10 | | Pull Requests merged | 12 | | Pull Requests proposed | 14 | +-+ 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: 2016-06-24 When were the last committers or PPMC members elected? Signed-off-by: [ ](omid) Alan Gates Comments: [ ](omid) Lars Hofhansl Comments: [ ](omid) Flavio P. Junqueira Comments: [ ](omid) Thejas Nair Comments: [ ](omid) James Taylor Comments: > Provide Apache Incubator Report June 2018 > - > > Key: OMID-101 > URL: https://issues.apache.org/jira/browse/OMID-101 > Project: Apache Omid > Issue Type: Task > Reporter: Francisco Perez-Sorrosal > Assignee: Francisco Perez-Sorrosal >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OMID-91) Provide Apache Incubator Report March 2018
[ https://issues.apache.org/jira/browse/OMID-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Perez-Sorrosal closed OMID-91. Resolution: Done Done here: https://wiki.apache.org/incubator/March2018 > Provide Apache Incubator Report March 2018 > -- > > Key: OMID-91 > URL: https://issues.apache.org/jira/browse/OMID-91 > Project: Apache Omid > Issue Type: Task > Reporter: Francisco Perez-Sorrosal > Assignee: Francisco Perez-Sorrosal >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: [VOTE] Omid release branch 0.9.0.0 - Release candidate 3
+1 Francisco On Wednesday, May 16, 2018, 5:12:18 PM PDT, Alan Gates wrote: +1 Built with a clean repo, ran the tests, ran RAT. Checked the NOTICE, LICENSE, and DISCLAIMER files. Alan. On Tue, May 15, 2018 at 12:36 PM, James Taylor wrote: > +1. Downloaded source and confirmed that all unit tests pass. > > On Sun, May 13, 2018 at 5:32 AM, Ohad Shacham > wrote: > > > Hi All, > > > > > > I would like to call a vote to release Apache Omid (Incubator) > > 0.9.0.0, release candidate #3. > > > > > > Links to various release artifacts are given below. Please review and > vote. > > > > The vote will be open for at least 72 hours and until necessary number of > > votes are reached. > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove (and reason why) > > > > Here is my +1 > > > > Release notes for the 0.9.0.0 > > release:https://dist.apache.org/repos/dist/dev/incubator/ > > omid/0.9.0.0-rc3/RELEASE_NOTES.html > > > > Git tag for the release: > > > > https://git-wip-us.apache.org/repos/asf/incubator-omid.git/? > > p=incubator-omid.git;a=tag;h=229831bc377e47431cc7cbc211803069158b5711 > > > > > > Sources for the release: > > > > https://dist.apache.org/repos/dist/dev/incubator/omid/0.9.0. > > 0-rc3/apache-omid-incubating-0.9.0.0-src.tar.gz > > Source release verification: PGP Signature: > > https://dist.apache.org/repos/dist/dev/incubator/omid/0.9.0. > > 0-rc3/apache-omid-incubating-0.9.0.0-src.tar.gz.asc > > SHA512 Hash: > > https://dist.apache.org/repos/dist/dev/incubator/omid/0.9.0. > > 0-rc3/apache-omid-incubating-0.9.0.0-src.tar.gz.sha512 > > Keys to verify the signature of the release artifact are available at: > > https://dist.apache.org/repos/dist/dev/incubator/omid/0.9.0.0-rc3/KEYS > > > > > > Thanks, > > Ohad > > >
[jira] [Created] (OMID-101) Provide Apache Incubator Report June 2018
Francisco Perez-Sorrosal created OMID-101: - Summary: Provide Apache Incubator Report June 2018 Key: OMID-101 URL: https://issues.apache.org/jira/browse/OMID-101 Project: Apache Omid Issue Type: Task Reporter: Francisco Perez-Sorrosal Assignee: Francisco Perez-Sorrosal -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: [VOTE] Omid release branch 0.9.0.0 - Release candidate 2
Sorry, I missed that. I thought my vote didn't count. +1 On Thursday, April 19, 2018, 2:29:05 PM PDT, James Taylor wrote: Hi Francisco,Thanks for taking a look. I don't see an actual vote, though? I'm assuming you're +1. If so, would you mind responding back on list with your vote?Thanks,James On Wed, Apr 11, 2018 at 11:25 AM, Francisco Pérez-Sorrosal wrote: Hi all, I've cloned and tested the 0.9.0.0-rc2 tag in a new local repo with both hbase-1 profile (now default) and hbase-0: - Tests and rat pass with no problems, and binary/src packages are created in both profiles - Checked that LICENSE.txt, DISCLAIMER and NOTICE are included in the src package - The contents of the binary packages seem to be OK. - TSO-server running OK with default config On Wed, Apr 11, 2018 at 8:48 AM Alan Gates wrote: > You don't have to have all the incubator PMC votes before going to the > general list, just 3 +1s from the PPMC. Technically we already have that > (since I assume you are +1), but it would be good to see feedback from > other non-mentor PPMC members. > > Alan. > > On Wed, Apr 11, 2018 at 2:00 AM, Ohad Shacham > wrote: > > > Thanks Alan! > > We need one more PMC in order to start a vote at the general list. Can > > anyone please check and vote? > > > > Thx, > > Ohad > > > > > > On Mon, Apr 9, 2018 at 10:19 PM, Alan Gates > wrote: > > > > > +1. Ran a build in a fresh repo, as well as RAT. Checked no binary > > files > > > included. Reviewed DISCLAIMER, LICENSE, and NOTICE files. > > > > > > Alan. > > > > > > On Tue, Apr 3, 2018 at 2:51 AM, Ohad Shacham > > > wrote: > > > > > > > Hi All, > > > > > > > > > > > > I would like to call a vote to release Apache Omid (Incubator) > > > > 0.9.0.0, release candidate #2. > > > > > > > > > > > > Links to various release artifacts are given below. Please review and > > > vote. > > > > > > > > The vote will be open for at least 72 hours and until necessary > number > > of > > > > votes are reached. > > > > [ ] +1 approve > > > > [ ] +0 no opinion > > > > [ ] -1 disapprove (and reason why) > > > > > > > > Here is my +1 > > > > > > > > Release notes for the 0.9.0.0 > > > > release:https://dist.apache. org/repos/dist/dev/incubator/ > > > > omid/0.9.0.0-rc2/RELEASE_ NOTES.html > > > > > > > > Git tag for the release: > > > > > > > > https://git-wip-us.apache.org/ repos/asf/incubator-omid.git/? > > > > p=incubator-omid.git;a=tag;h= 264a30e825bd0a75c435888d3cc12a 35b19b4405 > > > > > > > > > > > > Sources for the release: > > > > > > > > https://dist.apache.org/repos/ dist/dev/incubator/omid/0.9.0. > > > > 0-rc2/apache-omid-incubating- 0.9.0.0-src.tar.gz > > > > Source release verification: PGP Signature: > > > > https://dist.apache.org/repos/ dist/dev/incubator/omid/0.9.0. > > > > 0-rc2/apache-omid-incubating- 0.9.0.0-src.tar.gz.asc > > > > SHA512 Hash: > > > > https://dist.apache.org/repos/ dist/dev/incubator/omid/0.9.0. > > > > 0-rc2/apache-omid-incubating- 0.9.0.0-src.tar.gz.sha512 > > > > Keys to verify the signature of the release artifact are available > at: > > > > > https://dist.apache.org/repos/ dist/dev/incubator/omid/0.9.0. 0-rc2/KEYS > > > > > > > > > > > > Thanks, > > > > Ohad > > > > > > > > > >
[jira] [Commented] (OMID-91) Provide Apache Incubator Report March 2018
[ https://issues.apache.org/jira/browse/OMID-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391650#comment-16391650 ] Francisco Perez-Sorrosal commented on OMID-91: -- Report added to Apache Wiki here: https://wiki.apache.org/incubator/March2018 > Provide Apache Incubator Report March 2018 > -- > > Key: OMID-91 > URL: https://issues.apache.org/jira/browse/OMID-91 > Project: Apache Omid > Issue Type: Task > Reporter: Francisco Perez-Sorrosal > Assignee: Francisco Perez-Sorrosal >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OMID-91) Provide Apache Incubator Report March 2018
[ https://issues.apache.org/jira/browse/OMID-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391644#comment-16391644 ] Francisco Perez-Sorrosal commented on OMID-91: -- Draft: - Omid Omid is a flexible, reliable, high performant and scalable ACID transactional framework that allows client applications to execute transactions on top of MVCC key/value-based NoSQL datastores (currently Apache HBase) providing Snapshot Isolation guarantees on the accessed data. Omid has been incubating since 2016-03-28. Three most important issues to address in the move towards graduation: 1. Boost project dissemination in the Apache community. 2. Collaborate/integrate Omid with other Apache projects. 3. Get positive feedback from other projects currently in Apache. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? N/A How has the community developed since the last report? Apache Phoenix How has the project developed since the last report? HBase 0.x version being tested in prod environment at Yahoo. Preparing 0.9.0 version. Quarter Stats (from: 2017-12-01 to: 2018-02-28): +-+ | Metric | counts | +-+ | # of msgs in dev list | 108 | | Active Contributors (incl mentors)| 8 | | Jira New Issues | 2 | | Resolved Issues | 8 | | Pull Requests merged | 9 | | Pull Requests proposed | 3 | +-+ 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: 2016-06-24 When were the last committers or PPMC members elected? Signed-off-by: [ ](omid) Alan Gates Comments: [ ](omid) Lars Hofhansl Comments: [ ](omid) Flavio P. Junqueira Comments: [ ](omid) Thejas Nair Comments: [ ](omid) James Taylor Comments: > Provide Apache Incubator Report March 2018 > -- > > Key: OMID-91 > URL: https://issues.apache.org/jira/browse/OMID-91 > Project: Apache Omid > Issue Type: Task > Reporter: Francisco Perez-Sorrosal > Assignee: Francisco Perez-Sorrosal >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OMID-81) Provide Apache Incubator Report December 2017
[ https://issues.apache.org/jira/browse/OMID-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Perez-Sorrosal closed OMID-81. Resolution: Done > Provide Apache Incubator Report December 2017 > - > > Key: OMID-81 > URL: https://issues.apache.org/jira/browse/OMID-81 > Project: Apache Omid > Issue Type: Bug > Reporter: Francisco Perez-Sorrosal > Assignee: Francisco Perez-Sorrosal >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OMID-91) Provide Apache Incubator Report March 2018
Francisco Perez-Sorrosal created OMID-91: Summary: Provide Apache Incubator Report March 2018 Key: OMID-91 URL: https://issues.apache.org/jira/browse/OMID-91 Project: Apache Omid Issue Type: Task Reporter: Francisco Perez-Sorrosal Assignee: Francisco Perez-Sorrosal -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OMID-63) Do not expose HBaseTransactionClient interface in HBaseTransactionManager
[ https://issues.apache.org/jira/browse/OMID-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Perez-Sorrosal updated OMID-63: - Fix Version/s: (was: 0.9.0.0) > Do not expose HBaseTransactionClient interface in HBaseTransactionManager > - > > Key: OMID-63 > URL: https://issues.apache.org/jira/browse/OMID-63 > Project: Apache Omid > Issue Type: Bug > Reporter: Francisco Perez-Sorrosal > Assignee: Francisco Perez-Sorrosal >Priority: Major > > We should not expose that interface to clients -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (OMID-88) Add 0.9.0.0 and phoenix-integration branches to Travis
[ https://issues.apache.org/jira/browse/OMID-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16364545#comment-16364545 ] Francisco Perez-Sorrosal edited comment on OMID-88 at 2/14/18 6:21 PM: --- This fix should be added to the phoenix-integration branch in order to validate pull requests through Travis. was (Author: fperezsorrosal): This fix should be added to the phoenix-integration branch in order to validate pull request through Travis. > 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: all > 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] [Commented] (OMID-88) Add 0.9.0.0 and phoenix-integration branches to Travis
[ https://issues.apache.org/jira/browse/OMID-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16364545#comment-16364545 ] Francisco Perez-Sorrosal commented on OMID-88: -- This fix should be added to the phoenix-integration branch in order to validate pull request through Travis. > 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: all > 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] [Resolved] (OMID-88) Add 0.9.0.0 and phoenix-integration branches to Travis
[ https://issues.apache.org/jira/browse/OMID-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Perez-Sorrosal resolved OMID-88. -- Resolution: Fixed Done here in master branch: [https://github.com/apache/incubator-omid/commit/d7bbcb9954d5b4624d382e17496b61bbfbc4dbdd] Also in 0.9.0.0 branch: https://github.com/apache/incubator-omid/commit/fa7e2bccb7f13c3e3b0a515bbb87c876a21928e0 > 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: all > 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)
[GitHub] incubator-omid pull request #23: [OMID-89] Fix metrics in Persistence proces...
GitHub user francisco-perez-sorrosal opened a pull request: https://github.com/apache/incubator-omid/pull/23 [OMID-89] Fix metrics in Persistence processor handlers Change-Id: Ieb6cdf5d47cb113ea6cc8e9799bfbdef20b66565 You can merge this pull request into a Git repository by running: $ git pull https://github.com/francisco-perez-sorrosal/incubator-omid omid-89 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-omid/pull/23.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 #23 commit 7a25b91b4401704d9a7b6cdf38c6dc7cd196b4e7 Author: Francisco Perez-Sorrosal Date: 2018-02-02T23:09:02Z [OMID-89] Fix metrics in Persistence processsor handlers Change-Id: Ieb6cdf5d47cb113ea6cc8e9799bfbdef20b66565 ---
[jira] [Created] (OMID-89) Fix metrics in PersistenceProcesssorHandlers
Francisco Perez-Sorrosal created OMID-89: Summary: Fix metrics in PersistenceProcesssorHandlers Key: OMID-89 URL: https://issues.apache.org/jira/browse/OMID-89 Project: Apache Omid Issue Type: Bug Affects Versions: 0.8.2.0 Reporter: Francisco Perez-Sorrosal Assignee: Francisco Perez-Sorrosal Fix For: 0.9.0.0 Currently all the processor handlers report to the same metrics output. Separate the metrics of each handler to let each of them report individually through a handler identifier. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] incubator-omid pull request #22: [OMID-88] Add 0.9.0.0 and phoenix-integrati...
GitHub user francisco-perez-sorrosal opened a pull request: https://github.com/apache/incubator-omid/pull/22 [OMID-88] Add 0.9.0.0 and phoenix-integration branches to Travis Change-Id: Ib3308cfdb20ee84b3a71da8ec976873ff279d54f You can merge this pull request into a Git repository by running: $ git pull https://github.com/francisco-perez-sorrosal/incubator-omid omid-88 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-omid/pull/22.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 #22 commit d7bbcb9954d5b4624d382e17496b61bbfbc4dbdd Author: Francisco Perez-Sorrosal Date: 2018-02-01T23:55:25Z [OMID-88] Add 0.9.0.0 and phoenix-integration branches to Travis Change-Id: Ib3308cfdb20ee84b3a71da8ec976873ff279d54f ---
[GitHub] incubator-omid pull request #21: [OMID-87] Fix BatchPool initialization
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
[ 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: all > 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: all > 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] [Updated] (OMID-88) Add 0.9.0.0 and phoenix-integration branches to Travis
[ 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
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)
[jira] [Created] (OMID-87) Fix BatchPool initialization
Francisco Perez-Sorrosal created OMID-87: Summary: Fix BatchPool initialization Key: OMID-87 URL: https://issues.apache.org/jira/browse/OMID-87 Project: Apache Omid Issue Type: Bug Affects Versions: 0.8.2.0 Reporter: Francisco Perez-Sorrosal Assignee: Francisco Perez-Sorrosal Fix For: 0.9.0.0 When initializing the ObjectPool for Batch java objects in BatchPoolModule.java, an Apache's GenericObjectPool is used. The pool configuration lacks the call to config.setMaxIdle(int), which provokes that when the Batch objects are returned to the ObjectPool during the pre-creation phase, those above the default max idle number of objects in the pool (which is 8 according to the [Apache documentation|https://commons.apache.org/proper/commons-pool/api-1.6/org/apache/commons/pool/impl/GenericObjectPool.html]) are destroyed. If at some point the TSO needs to access those Batch objects between 8 and the number specified in the Omid configuration (numConcurrentCTWriters), they will be created on the fly, which it was we want to avoid when pre-creating the ObjectPool during the TSO initialization. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] incubator-omid pull request #18: [OMID-86] Add Tx info in RollbackException
GitHub user francisco-perez-sorrosal opened a pull request: https://github.com/apache/incubator-omid/pull/18 [OMID-86] Add Tx info in RollbackException Add missing transaction information in all RollbackException in AbstractTransactionManager Change-Id: Ic6279a22f087861f6fa75953a76984932ecd9a90 You can merge this pull request into a Git repository by running: $ git pull https://github.com/francisco-perez-sorrosal/incubator-omid omid-86 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-omid/pull/18.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 #18 commit de7479355bef19dd6d0348b377e4cde51d691828 Author: Francisco Perez-Sorrosal Date: 2018-01-31T01:14:54Z [OMID-86] Add Tx info in RollbackException Add missing transaction information in all RollbackException in AbstractTransactionManager Change-Id: Ic6279a22f087861f6fa75953a76984932ecd9a90 ---
[jira] [Updated] (OMID-86) Add Tx info in RollbackException
[ https://issues.apache.org/jira/browse/OMID-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Perez-Sorrosal updated OMID-86: - Description: Add missing transaction information in all RollbackException in AbstractTransactionManager. Required for debugging purposes. was:Add missing transaction information in all RollbackException in AbstractTransactionManager > Add Tx info in RollbackException > > > Key: OMID-86 > URL: https://issues.apache.org/jira/browse/OMID-86 > Project: Apache Omid > Issue Type: Improvement >Affects Versions: 0.8.2.0 > Reporter: Francisco Perez-Sorrosal > Assignee: Francisco Perez-Sorrosal >Priority: Trivial > Fix For: 0.9.0.0 > > > Add missing transaction information in all RollbackException in > AbstractTransactionManager. > Required for debugging purposes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OMID-86) Add Tx info in RollbackException
Francisco Perez-Sorrosal created OMID-86: Summary: Add Tx info in RollbackException Key: OMID-86 URL: https://issues.apache.org/jira/browse/OMID-86 Project: Apache Omid Issue Type: Improvement Affects Versions: 0.8.2.0 Reporter: Francisco Perez-Sorrosal Assignee: Francisco Perez-Sorrosal Fix For: 0.9.0.0 Add missing transaction information in all RollbackException in AbstractTransactionManager -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OMID-79) Revert commits for Phoenix integration from master branch
[ https://issues.apache.org/jira/browse/OMID-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Perez-Sorrosal closed OMID-79. Resolution: Fixed Done in [this commit|https://github.com/apache/incubator-omid/commit/31dd269dc88f9617ac37e8dfb5fd867db389ba7c] > Revert commits for Phoenix integration from master branch > - > > Key: OMID-79 > URL: https://issues.apache.org/jira/browse/OMID-79 > Project: Apache Omid > Issue Type: Task > Reporter: Francisco Perez-Sorrosal > Assignee: Francisco Perez-Sorrosal >Priority: Major > > Some commits for Phoenix integration were added to the master branch and > should be reverted: > [https://github.com/apache/incubator-omid/commit/0005b3603571b28e01e5fbd8943e23efc5ead781] > > [https://github.com/apache/incubator-omid/commit/60c9e714fd862f17407202565ac1eb7011910e1e] > > [https://github.com/apache/incubator-omid/commit/0cae2ff18f507f640edbe484e24000630856d3f0] > > [https://github.com/apache/incubator-omid/commit/1f83aeda963472c861b4b622c08b3c8c725fbd16] > > [https://github.com/apache/incubator-omid/commit/4c8d7821fbbad943f46f3dfc0ac51b0ea908f90f] > [https://github.com/apache/incubator-omid/commit/fab2cfebbd9f4c3d95a1d02a428c90c1dc649db5] > > The commits related to the Phoenix integration should be in a different > branch, e.g. phoenix-integration -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OMID-80) Create a branch for Phoenix integration
[ https://issues.apache.org/jira/browse/OMID-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Perez-Sorrosal closed OMID-80. Resolution: Fixed > Create a branch for Phoenix integration > --- > > Key: OMID-80 > URL: https://issues.apache.org/jira/browse/OMID-80 > Project: Apache Omid > Issue Type: Task > Reporter: Francisco Perez-Sorrosal >Assignee: Ohad Shacham >Priority: Major > > The commits related to the Phoenix integration should be in a different > branch, e.g. phoenix-integration. > Please, create a new branch with the commits described below and continue > working there. > The following commits were added to the master branch and will be reverted in > the master branch through OMID-79: > https://github.com/apache/incubator-omid/commit/0005b3603571b28e01e5fbd8943e23efc5ead781 > https://github.com/apache/incubator-omid/commit/60c9e714fd862f17407202565ac1eb7011910e1e > https://github.com/apache/incubator-omid/commit/0cae2ff18f507f640edbe484e24000630856d3f0 > https://github.com/apache/incubator-omid/commit/1f83aeda963472c861b4b622c08b3c8c725fbd16 > https://github.com/apache/incubator-omid/commit/4c8d7821fbbad943f46f3dfc0ac51b0ea908f90f > https://github.com/apache/incubator-omid/commit/fab2cfebbd9f4c3d95a1d02a428c90c1dc649db5 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OMID-80) Create a branch for Phoenix integration
[ https://issues.apache.org/jira/browse/OMID-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16346022#comment-16346022 ] Francisco Perez-Sorrosal commented on OMID-80: -- Renamed branch for Phoenix integration form PhoenixCompatibility to phoenix-integration as per was stated in the description of this issue. Please use non-capitalized names and dashes for branches/tags from now on. See it here: [https://github.com/apache/incubator-omid/tree/phoenix-integration] and here: [https://git-wip-us.apache.org/repos/asf?p=incubator-omid.git] > Create a branch for Phoenix integration > --- > > Key: OMID-80 > URL: https://issues.apache.org/jira/browse/OMID-80 > Project: Apache Omid > Issue Type: Task > Reporter: Francisco Perez-Sorrosal >Assignee: Ohad Shacham >Priority: Major > > The commits related to the Phoenix integration should be in a different > branch, e.g. phoenix-integration. > Please, create a new branch with the commits described below and continue > working there. > The following commits were added to the master branch and will be reverted in > the master branch through OMID-79: > https://github.com/apache/incubator-omid/commit/0005b3603571b28e01e5fbd8943e23efc5ead781 > https://github.com/apache/incubator-omid/commit/60c9e714fd862f17407202565ac1eb7011910e1e > https://github.com/apache/incubator-omid/commit/0cae2ff18f507f640edbe484e24000630856d3f0 > https://github.com/apache/incubator-omid/commit/1f83aeda963472c861b4b622c08b3c8c725fbd16 > https://github.com/apache/incubator-omid/commit/4c8d7821fbbad943f46f3dfc0ac51b0ea908f90f > https://github.com/apache/incubator-omid/commit/fab2cfebbd9f4c3d95a1d02a428c90c1dc649db5 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OMID-79) Revert commits for Phoenix integration from master branch
[ https://issues.apache.org/jira/browse/OMID-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Perez-Sorrosal updated OMID-79: - Description: Some commits for Phoenix integration were added to the master branch and should be reverted: [https://github.com/apache/incubator-omid/commit/0005b3603571b28e01e5fbd8943e23efc5ead781] [https://github.com/apache/incubator-omid/commit/60c9e714fd862f17407202565ac1eb7011910e1e] [https://github.com/apache/incubator-omid/commit/0cae2ff18f507f640edbe484e24000630856d3f0] [https://github.com/apache/incubator-omid/commit/1f83aeda963472c861b4b622c08b3c8c725fbd16] [https://github.com/apache/incubator-omid/commit/4c8d7821fbbad943f46f3dfc0ac51b0ea908f90f] [https://github.com/apache/incubator-omid/commit/fab2cfebbd9f4c3d95a1d02a428c90c1dc649db5] The commits related to the Phoenix integration should be in a different branch, e.g. phoenix-integration was: Some commits for Phoenix integration were added to the master branch and should be reverted: https://github.com/apache/incubator-omid/commit/0005b3603571b28e01e5fbd8943e23efc5ead781 https://github.com/apache/incubator-omid/commit/60c9e714fd862f17407202565ac1eb7011910e1e https://github.com/apache/incubator-omid/commit/0cae2ff18f507f640edbe484e24000630856d3f0 https://github.com/apache/incubator-omid/commit/1f83aeda963472c861b4b622c08b3c8c725fbd16 https://github.com/apache/incubator-omid/commit/4c8d7821fbbad943f46f3dfc0ac51b0ea908f90f The commits related to the Phoenix integration should be in a different branch, e.g. phoenix-integration > Revert commits for Phoenix integration from master branch > - > > Key: OMID-79 > URL: https://issues.apache.org/jira/browse/OMID-79 > Project: Apache Omid > Issue Type: Task > Reporter: Francisco Perez-Sorrosal > Assignee: Francisco Perez-Sorrosal >Priority: Major > > Some commits for Phoenix integration were added to the master branch and > should be reverted: > [https://github.com/apache/incubator-omid/commit/0005b3603571b28e01e5fbd8943e23efc5ead781] > > [https://github.com/apache/incubator-omid/commit/60c9e714fd862f17407202565ac1eb7011910e1e] > > [https://github.com/apache/incubator-omid/commit/0cae2ff18f507f640edbe484e24000630856d3f0] > > [https://github.com/apache/incubator-omid/commit/1f83aeda963472c861b4b622c08b3c8c725fbd16] > > [https://github.com/apache/incubator-omid/commit/4c8d7821fbbad943f46f3dfc0ac51b0ea908f90f] > [https://github.com/apache/incubator-omid/commit/fab2cfebbd9f4c3d95a1d02a428c90c1dc649db5] > > The commits related to the Phoenix integration should be in a different > branch, e.g. phoenix-integration -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OMID-81) Provide Apache Incubator Report December 2017
[ https://issues.apache.org/jira/browse/OMID-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16279004#comment-16279004 ] Francisco Perez-Sorrosal commented on OMID-81: -- Report added to Apache Wiki here: https://wiki.apache.org/incubator/December2017 > Provide Apache Incubator Report December 2017 > - > > Key: OMID-81 > URL: https://issues.apache.org/jira/browse/OMID-81 > Project: Apache Omid > Issue Type: Bug > Reporter: Francisco Perez-Sorrosal > Assignee: Francisco Perez-Sorrosal > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OMID-81) Provide Apache Incubator Report December 2017
[ https://issues.apache.org/jira/browse/OMID-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16278995#comment-16278995 ] Francisco Perez-Sorrosal commented on OMID-81: -- See draft below: - Omid Omid is a flexible, reliable, high performant and scalable ACID transactional framework that allows client applications to execute transactions on top of MVCC key/value-based NoSQL datastores (currently Apache HBase) providing Snapshot Isolation guarantees on the accessed data. Omid has been incubating since 2016-03-28. Three most important issues to address in the move towards graduation: 1. Boost project dissemination in the Apache community. 2. Collaborate/integrate Omid with other Apache projects. 3. Get positive feedback from other projects currently in Apache. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? N/A How has the community developed since the last report? Continue integration with Apache Phoenix How has the project developed since the last report? Critical fixes on security and HBase 0.x & 1.x integration. HBase 0.x version being tested in prod environment at Yahoo. Started testing HBase version 1.x in local environments. Quarter Stats (from: 2017-09-01 to: 2017-11-30): +-+ | Metric | counts | +-+ | # of msgs in dev list | 53| | Active Contributors (incl mentors)|8| | Jira New Issues |5| | Resolved Issues |1| | Pull Requests merged |1| | Pull Requests proposed|2| +-+ 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: 2016-06-24 When were the last committers or PPMC members elected? Signed-off-by: [ ](omid) Alan Gates Comments: [ ](omid) Lars Hofhansl Comments: [ ](omid) Flavio P. Junqueira Comments: [ ](omid) Thejas Nair Comments: [ ](omid) James Taylor Comments: > Provide Apache Incubator Report December 2017 > - > > Key: OMID-81 > URL: https://issues.apache.org/jira/browse/OMID-81 > Project: Apache Omid > Issue Type: Bug > Reporter: Francisco Perez-Sorrosal > Assignee: Francisco Perez-Sorrosal > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OMID-75) Provide Apache Incubator Report September 2017
[ https://issues.apache.org/jira/browse/OMID-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Perez-Sorrosal closed OMID-75. Resolution: Fixed See final report here: https://wiki.apache.org/incubator/September2017 > Provide Apache Incubator Report September 2017 > -- > > Key: OMID-75 > URL: https://issues.apache.org/jira/browse/OMID-75 > Project: Apache Omid > Issue Type: Task > Reporter: Francisco Perez-Sorrosal > Assignee: Francisco Perez-Sorrosal > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OMID-81) Provide Apache Incubator Report December 2017
Francisco Perez-Sorrosal created OMID-81: Summary: Provide Apache Incubator Report December 2017 Key: OMID-81 URL: https://issues.apache.org/jira/browse/OMID-81 Project: Apache Omid Issue Type: Bug Reporter: Francisco Perez-Sorrosal Assignee: Francisco Perez-Sorrosal -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OMID-80) Create a branch for Phoenix integration
[ https://issues.apache.org/jira/browse/OMID-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Perez-Sorrosal updated OMID-80: - Description: The commits related to the Phoenix integration should be in a different branch, e.g. phoenix-integration. Please, create a new branch with the commits described below and continue working there. The following commits were added to the master branch and will be reverted in the master branch through OMID-79: https://github.com/apache/incubator-omid/commit/0005b3603571b28e01e5fbd8943e23efc5ead781 https://github.com/apache/incubator-omid/commit/60c9e714fd862f17407202565ac1eb7011910e1e https://github.com/apache/incubator-omid/commit/0cae2ff18f507f640edbe484e24000630856d3f0 https://github.com/apache/incubator-omid/commit/1f83aeda963472c861b4b622c08b3c8c725fbd16 https://github.com/apache/incubator-omid/commit/4c8d7821fbbad943f46f3dfc0ac51b0ea908f90f https://github.com/apache/incubator-omid/commit/fab2cfebbd9f4c3d95a1d02a428c90c1dc649db5 was: The commits related to the Phoenix integration should be in a different branch, e.g. phoenix-integration. Please, create a new branch with the commits described below and continue working there. The following commits were added to the master branch and will be reverted in the master branch through OMID-79: https://github.com/apache/incubator-omid/commit/0005b3603571b28e01e5fbd8943e23efc5ead781 https://github.com/apache/incubator-omid/commit/60c9e714fd862f17407202565ac1eb7011910e1e https://github.com/apache/incubator-omid/commit/0cae2ff18f507f640edbe484e24000630856d3f0 https://github.com/apache/incubator-omid/commit/1f83aeda963472c861b4b622c08b3c8c725fbd16 https://github.com/apache/incubator-omid/commit/4c8d7821fbbad943f46f3dfc0ac51b0ea908f90f > Create a branch for Phoenix integration > --- > > Key: OMID-80 > URL: https://issues.apache.org/jira/browse/OMID-80 > Project: Apache Omid > Issue Type: Task > Reporter: Francisco Perez-Sorrosal >Assignee: Ohad Shacham > > The commits related to the Phoenix integration should be in a different > branch, e.g. phoenix-integration. > Please, create a new branch with the commits described below and continue > working there. > The following commits were added to the master branch and will be reverted in > the master branch through OMID-79: > https://github.com/apache/incubator-omid/commit/0005b3603571b28e01e5fbd8943e23efc5ead781 > https://github.com/apache/incubator-omid/commit/60c9e714fd862f17407202565ac1eb7011910e1e > https://github.com/apache/incubator-omid/commit/0cae2ff18f507f640edbe484e24000630856d3f0 > https://github.com/apache/incubator-omid/commit/1f83aeda963472c861b4b622c08b3c8c725fbd16 > https://github.com/apache/incubator-omid/commit/4c8d7821fbbad943f46f3dfc0ac51b0ea908f90f > https://github.com/apache/incubator-omid/commit/fab2cfebbd9f4c3d95a1d02a428c90c1dc649db5 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OMID-80) Create a branch for Phoenix integration
[ https://issues.apache.org/jira/browse/OMID-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16278967#comment-16278967 ] Francisco Perez-Sorrosal commented on OMID-80: -- I've just seen another commit in the master branch: https://github.com/apache/incubator-omid/commit/fab2cfebbd9f4c3d95a1d02a428c90c1dc649db5 Would you please create a separate branch to include the commits for the Phoenix integration instead of doing it on the master branch as is described above? There are some critical commits related to security and other stuff in the current release branch (0.9.0.0) that should be added to the master branch before integrating Phoenix. Thanks! > Create a branch for Phoenix integration > --- > > Key: OMID-80 > URL: https://issues.apache.org/jira/browse/OMID-80 > Project: Apache Omid > Issue Type: Task > Reporter: Francisco Perez-Sorrosal >Assignee: Ohad Shacham > > The commits related to the Phoenix integration should be in a different > branch, e.g. phoenix-integration. > Please, create a new branch with the commits described below and continue > working there. > The following commits were added to the master branch and will be reverted in > the master branch through OMID-79: > https://github.com/apache/incubator-omid/commit/0005b3603571b28e01e5fbd8943e23efc5ead781 > https://github.com/apache/incubator-omid/commit/60c9e714fd862f17407202565ac1eb7011910e1e > https://github.com/apache/incubator-omid/commit/0cae2ff18f507f640edbe484e24000630856d3f0 > https://github.com/apache/incubator-omid/commit/1f83aeda963472c861b4b622c08b3c8c725fbd16 > https://github.com/apache/incubator-omid/commit/4c8d7821fbbad943f46f3dfc0ac51b0ea908f90f -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OMID-80) Create a branch for Phoenix integration
[ https://issues.apache.org/jira/browse/OMID-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Perez-Sorrosal updated OMID-80: - Description: The commits related to the Phoenix integration should be in a different branch, e.g. phoenix-integration. Please, create a new branch with the commits described below and continue working there. The following commits were added to the master branch and will be reverted in the master branch through OMID-79: https://github.com/apache/incubator-omid/commit/0005b3603571b28e01e5fbd8943e23efc5ead781 https://github.com/apache/incubator-omid/commit/60c9e714fd862f17407202565ac1eb7011910e1e https://github.com/apache/incubator-omid/commit/0cae2ff18f507f640edbe484e24000630856d3f0 https://github.com/apache/incubator-omid/commit/1f83aeda963472c861b4b622c08b3c8c725fbd16 https://github.com/apache/incubator-omid/commit/4c8d7821fbbad943f46f3dfc0ac51b0ea908f90f was: The commits related to the Phoenix integration should be in a different branch, e.g. phoenix-integration. The following commits were added to the master branch and should be reverted in #OMID-79: https://github.com/apache/incubator-omid/commit/0005b3603571b28e01e5fbd8943e23efc5ead781 https://github.com/apache/incubator-omid/commit/60c9e714fd862f17407202565ac1eb7011910e1e https://github.com/apache/incubator-omid/commit/0cae2ff18f507f640edbe484e24000630856d3f0 https://github.com/apache/incubator-omid/commit/1f83aeda963472c861b4b622c08b3c8c725fbd16 https://github.com/apache/incubator-omid/commit/4c8d7821fbbad943f46f3dfc0ac51b0ea908f90f > Create a branch for Phoenix integration > --- > > Key: OMID-80 > URL: https://issues.apache.org/jira/browse/OMID-80 > Project: Apache Omid > Issue Type: Task > Reporter: Francisco Perez-Sorrosal >Assignee: Ohad Shacham > > The commits related to the Phoenix integration should be in a different > branch, e.g. phoenix-integration. > Please, create a new branch with the commits described below and continue > working there. > The following commits were added to the master branch and will be reverted in > the master branch through OMID-79: > https://github.com/apache/incubator-omid/commit/0005b3603571b28e01e5fbd8943e23efc5ead781 > https://github.com/apache/incubator-omid/commit/60c9e714fd862f17407202565ac1eb7011910e1e > https://github.com/apache/incubator-omid/commit/0cae2ff18f507f640edbe484e24000630856d3f0 > https://github.com/apache/incubator-omid/commit/1f83aeda963472c861b4b622c08b3c8c725fbd16 > https://github.com/apache/incubator-omid/commit/4c8d7821fbbad943f46f3dfc0ac51b0ea908f90f -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OMID-80) Create a branch for Phoenix integration
[ https://issues.apache.org/jira/browse/OMID-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Perez-Sorrosal reassigned OMID-80: Assignee: Ohad Shacham (was: Francisco Perez-Sorrosal) > Create a branch for Phoenix integration > --- > > Key: OMID-80 > URL: https://issues.apache.org/jira/browse/OMID-80 > Project: Apache Omid > Issue Type: Task > Reporter: Francisco Perez-Sorrosal >Assignee: Ohad Shacham > > The commits related to the Phoenix integration should be in a different > branch, e.g. phoenix-integration. > The following commits were added to the master branch and should be reverted > in #OMID-79: > https://github.com/apache/incubator-omid/commit/0005b3603571b28e01e5fbd8943e23efc5ead781 > https://github.com/apache/incubator-omid/commit/60c9e714fd862f17407202565ac1eb7011910e1e > https://github.com/apache/incubator-omid/commit/0cae2ff18f507f640edbe484e24000630856d3f0 > https://github.com/apache/incubator-omid/commit/1f83aeda963472c861b4b622c08b3c8c725fbd16 > https://github.com/apache/incubator-omid/commit/4c8d7821fbbad943f46f3dfc0ac51b0ea908f90f -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OMID-80) Create a branch for Phoenix integration
[ https://issues.apache.org/jira/browse/OMID-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Perez-Sorrosal updated OMID-80: - Priority: Major (was: Blocker) > Create a branch for Phoenix integration > --- > > Key: OMID-80 > URL: https://issues.apache.org/jira/browse/OMID-80 > Project: Apache Omid > Issue Type: Task > Reporter: Francisco Perez-Sorrosal > Assignee: Francisco Perez-Sorrosal > > The commits related to the Phoenix integration should be in a different > branch, e.g. phoenix-integration. > The following commits were added to the master branch and should be reverted > in #OMID-79: > https://github.com/apache/incubator-omid/commit/0005b3603571b28e01e5fbd8943e23efc5ead781 > https://github.com/apache/incubator-omid/commit/60c9e714fd862f17407202565ac1eb7011910e1e > https://github.com/apache/incubator-omid/commit/0cae2ff18f507f640edbe484e24000630856d3f0 > https://github.com/apache/incubator-omid/commit/1f83aeda963472c861b4b622c08b3c8c725fbd16 > https://github.com/apache/incubator-omid/commit/4c8d7821fbbad943f46f3dfc0ac51b0ea908f90f -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OMID-80) Create a branch for Phoenix integration
[ https://issues.apache.org/jira/browse/OMID-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Perez-Sorrosal updated OMID-80: - Description: The commits related to the Phoenix integration should be in a different branch, e.g. phoenix-integration. The following commits were added to the master branch and should be reverted in #OMID-79: https://github.com/apache/incubator-omid/commit/0005b3603571b28e01e5fbd8943e23efc5ead781 https://github.com/apache/incubator-omid/commit/60c9e714fd862f17407202565ac1eb7011910e1e https://github.com/apache/incubator-omid/commit/0cae2ff18f507f640edbe484e24000630856d3f0 https://github.com/apache/incubator-omid/commit/1f83aeda963472c861b4b622c08b3c8c725fbd16 https://github.com/apache/incubator-omid/commit/4c8d7821fbbad943f46f3dfc0ac51b0ea908f90f > Create a branch for Phoenix integration > --- > > Key: OMID-80 > URL: https://issues.apache.org/jira/browse/OMID-80 > Project: Apache Omid > Issue Type: Task > Reporter: Francisco Perez-Sorrosal > Assignee: Francisco Perez-Sorrosal >Priority: Blocker > > The commits related to the Phoenix integration should be in a different > branch, e.g. phoenix-integration. > The following commits were added to the master branch and should be reverted > in #OMID-79: > https://github.com/apache/incubator-omid/commit/0005b3603571b28e01e5fbd8943e23efc5ead781 > https://github.com/apache/incubator-omid/commit/60c9e714fd862f17407202565ac1eb7011910e1e > https://github.com/apache/incubator-omid/commit/0cae2ff18f507f640edbe484e24000630856d3f0 > https://github.com/apache/incubator-omid/commit/1f83aeda963472c861b4b622c08b3c8c725fbd16 > https://github.com/apache/incubator-omid/commit/4c8d7821fbbad943f46f3dfc0ac51b0ea908f90f -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OMID-80) Create a branch for Phoenix integration
Francisco Perez-Sorrosal created OMID-80: Summary: Create a branch for Phoenix integration Key: OMID-80 URL: https://issues.apache.org/jira/browse/OMID-80 Project: Apache Omid Issue Type: Task Reporter: Francisco Perez-Sorrosal Assignee: Francisco Perez-Sorrosal Priority: Blocker -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OMID-79) Revert commits for Phoenix integration from master branch
Francisco Perez-Sorrosal created OMID-79: Summary: Revert commits for Phoenix integration from master branch Key: OMID-79 URL: https://issues.apache.org/jira/browse/OMID-79 Project: Apache Omid Issue Type: Task Reporter: Francisco Perez-Sorrosal Assignee: Francisco Perez-Sorrosal Some commits for Phoenix integration were added to the master branch and should be reverted: https://github.com/apache/incubator-omid/commit/0005b3603571b28e01e5fbd8943e23efc5ead781 https://github.com/apache/incubator-omid/commit/60c9e714fd862f17407202565ac1eb7011910e1e https://github.com/apache/incubator-omid/commit/0cae2ff18f507f640edbe484e24000630856d3f0 https://github.com/apache/incubator-omid/commit/1f83aeda963472c861b4b622c08b3c8c725fbd16 https://github.com/apache/incubator-omid/commit/4c8d7821fbbad943f46f3dfc0ac51b0ea908f90f The commits related to the Phoenix integration should be in a different branch, e.g. phoenix-integration -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OMID-77) Omid Coprocessor is not working in HBase version 0.98 after adding the shims
[ https://issues.apache.org/jira/browse/OMID-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16204257#comment-16204257 ] Francisco Perez-Sorrosal commented on OMID-77: -- Logs: 2017-10-12 09:57:55,103 FATAL regionserver.HRegionServer [regionserver50511-smallCompactions-1507798675910] : ABORTING region server gsbl887n36.blue.ygrid.yahoo.com,50511,1507798657685: The coprocessor org.apache.omid.transaction.OmidCompactor threw java.lang.NoClassDefFoundError: org/apache/hadoop/hbase/regionserver/CompactorScanner java.lang.NoClassDefFoundError: org/apache/hadoop/hbase/regionserver/CompactorScanner at org.apache.omid.transaction.OmidCompactor.preCompact(OmidCompactor.java:123) at org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost$9.call(RegionCoprocessorHost.java:471) at org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost$RegionOperation.call(RegionCoprocessorHost.java:1523) at org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.execOperation(RegionCoprocessorHost.java:1598) at org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.execOperationWithResult(RegionCoprocessorHost.java:1572) at org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.preCompact(RegionCoprocessorHost.java:466) at org.apache.hadoop.hbase.regionserver.compactions.Compactor.postCreateCoprocScanner(Compactor.java:198) at org.apache.hadoop.hbase.regionserver.compactions.DefaultCompactor.compact(DefaultCompactor.java:71) at org.apache.hadoop.hbase.regionserver.DefaultStoreEngine$DefaultCompactionContext.compact(DefaultStoreEngine.java:110) at org.apache.hadoop.hbase.regionserver.HStore.compact(HStore.java:1107) at org.apache.hadoop.hbase.regionserver.HRegion.compact(HRegion.java:1552) at org.apache.hadoop.hbase.regionserver.CompactSplitThread$CompactionRunner.run(CompactSplitThread.java:478) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.hbase.regionserver.CompactorScanner at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at org.apache.hadoop.hbase.util.CoprocessorClassLoader.loadClass(CoprocessorClassLoader.java:275) ... 15 more 2017-10-12 09:57:55,104 FATAL regionserver.HRegionServer [regionserver50511-smallCompactions-1507798675910] : RegionServer abort: loaded coprocessors are: [org.apache.hadoop.hbase.security.access.AccessController, org.apache.hadoop.hbase.replication.regionserver.ReplicationHLogEndpoint, org.apache.hadoop.hbase.security.token.TokenProvider, org.apache.omid.transaction.OmidCompactor, com.yahoo.omid.transaction.OmidCompactor] > Omid Coprocessor is not working in HBase version 0.98 after adding the shims > > > Key: OMID-77 > URL: https://issues.apache.org/jira/browse/OMID-77 > Project: Apache Omid > Issue Type: Bug > Reporter: Francisco Perez-Sorrosal > Labels: 0.9x, coprocessor, hbase, shims > > When introducing the shims in this PR > https://github.com/yahoo/omid/pull/37/commits it wasn't taken into account > that HBase filters classes in org.apache.hadoop.hbase. See: > https://github.com/apache/hbase/blob/0.98/hbase-common/src/main/java/org/apache/hadoop/hbase/util/CoprocessorClassLoader.java#L101 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OMID-77) Omid Coprocessor is not working in HBase version 0.98 after adding the shims
Francisco Perez-Sorrosal created OMID-77: Summary: Omid Coprocessor is not working in HBase version 0.98 after adding the shims Key: OMID-77 URL: https://issues.apache.org/jira/browse/OMID-77 Project: Apache Omid Issue Type: Bug Reporter: Francisco Perez-Sorrosal When introducing the shims in this PR https://github.com/yahoo/omid/pull/37/commits it wasn't taken into account that HBase filters classes in org.apache.hadoop.hbase. See: https://github.com/apache/hbase/blob/0.98/hbase-common/src/main/java/org/apache/hadoop/hbase/util/CoprocessorClassLoader.java#L101 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OMID-75) Provide Apache Incubator Report September 2017
[ https://issues.apache.org/jira/browse/OMID-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155779#comment-16155779 ] Francisco Perez-Sorrosal commented on OMID-75: -- Draft published here: https://wiki.apache.org/incubator/September2017 > Provide Apache Incubator Report September 2017 > -- > > Key: OMID-75 > URL: https://issues.apache.org/jira/browse/OMID-75 > Project: Apache Omid > Issue Type: Task > Reporter: Francisco Perez-Sorrosal > Assignee: Francisco Perez-Sorrosal > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OMID-75) Provide Apache Incubator Report September 2017
[ https://issues.apache.org/jira/browse/OMID-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155763#comment-16155763 ] Francisco Perez-Sorrosal commented on OMID-75: -- See Draft below: Omid Omid is a flexible, reliable, high performant and scalable ACID transactional framework that allows client applications to execute transactions on top of MVCC key/value-based NoSQL datastores (currently Apache HBase) providing Snapshot Isolation guarantees on the accessed data. Omid has been incubating since 2016-03-28. Three most important issues to address in the move towards graduation: 1. Boost project dissemination in the Apache community. 2. Collaborate/integrate Omid with other Apache projects. 3. Get positive feedback from other projects currently Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? N/A How has the community developed since the last report? Started integration with Apache Phoenix How has the project developed since the last report? Several bugs discovered and fixed. Continue testing prod environment at Yahoo. Branch 0.9.0.0 started for next release Quarter Stats (from: 2017-03-01 to: 2017-05-31): +-+ | Metric | counts | +-+ | # of msgs in dev list | 108| | Active Contributors (incl mentors)|8| | Jira New Issues |6| | Resolved Issues |6| | Pull Requests merged |3| | Pull Requests proposed|3| +-+ 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: 2016-06-24 When were the last committers or PPMC members elected? Signed-off-by: [ ](omid) Alan Gates Comments: [ ](omid) Lars Hofhansl Comments: [ ](omid) Flavio P. Junqueira Comments: [ ](omid) Thejas Nair Comments: [ ](omid) James Taylor Comments: IPMC/Shepherd notes: > Provide Apache Incubator Report September 2017 > -- > > Key: OMID-75 > URL: https://issues.apache.org/jira/browse/OMID-75 > Project: Apache Omid > Issue Type: Task > Reporter: Francisco Perez-Sorrosal > Assignee: Francisco Perez-Sorrosal > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OMID-75) Provide Apache Incubator Report September 2017
Francisco Perez-Sorrosal created OMID-75: Summary: Provide Apache Incubator Report September 2017 Key: OMID-75 URL: https://issues.apache.org/jira/browse/OMID-75 Project: Apache Omid Issue Type: Task Reporter: Francisco Perez-Sorrosal Assignee: Francisco Perez-Sorrosal -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (OMID-69) Provide Apache Incubator Report June 2017
[ https://issues.apache.org/jira/browse/OMID-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Perez-Sorrosal closed OMID-69. Resolution: Done See final report in here: https://wiki.apache.org/incubator/June2017 > Provide Apache Incubator Report June 2017 > - > > Key: OMID-69 > URL: https://issues.apache.org/jira/browse/OMID-69 > Project: Apache Omid > Issue Type: Task > Reporter: Francisco Perez-Sorrosal > Assignee: Francisco Perez-Sorrosal > > See Draft below: > Omid > Omid is a flexible, reliable, high performant and scalable ACID transactional > framework that allows client applications to execute transactions on top of > MVCC key/value-based NoSQL datastores (currently Apache HBase) providing > Snapshot Isolation guarantees on the accessed data. > Omid has been incubating since 2016-03-28. > Three most important issues to address in the move towards graduation: > 1. Boost project dissemination in the Apache community. > 2. Collaborate/integrate Omid with other Apache projects. > 3. Get positive feedback from other projects currently > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be > aware of? > N/A > How has the community developed since the last report? > 2 new contributors > Omid presented in the Apache Conf US in comparison to other Apache TMs for > HBase. It will be presented also in HBase conf in mid June. > Meeting with Apache Tephra contributors > How has the project developed since the last report? > Several bugs discovered and working on fixes. > Continue working on next release. Testing in prod env. > Quarter Stats (from: 2017-03-01 to: 2017-05-31): > +-+ > | Metric | counts | > +-+ > | # of msgs in dev list | 60| > | Active Contributors (incl mentors)|8| > | Jira New Issues |8| > | Resolved Issues |2| > | Pull Requests merged |1| > | Pull Requests proposed|3| > +-+ > 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: > 2016-06-24 > When were the last committers or PPMC members elected? > Signed-off-by: > [ ](omid) Alan Gates > Comments: > [ ](omid) Lars Hofhansl > Comments: > [ ](omid) Flavio P. Junqueira > Comments: > [ ](omid) Thejas Nair > Comments: > [ ](omid) James Taylor > Comments: > IPMC/Shepherd notes: -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] incubator-omid pull request #14: [OMID-67] Avoid Kerberos logging multiple t...
GitHub user francisco-perez-sorrosal opened a pull request: https://github.com/apache/incubator-omid/pull/14 [OMID-67] Avoid Kerberos logging multiple times It may cause race conditions when done multiple times from the same JVM. The Kerberos ticket is not properly renewed when this happens. Change-Id: I07599f54bc9bead90a87d30a2f6b033de64b6470 You can merge this pull request into a Git repository by running: $ git pull https://github.com/francisco-perez-sorrosal/incubator-omid fix-kerberos Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-omid/pull/14.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 #14 commit 7c22891b6b4e4805e12dcd13baeee57c24ac9da1 Author: Francisco Perez-Sorrosal Date: 2017-05-11T19:00:21Z [OMID-67] Avoid Kerberos logging multiple times It may cause race conditions when done multiple times from the same JVM. The Kerberos ticket is not properly renewed when this happens. Change-Id: I07599f54bc9bead90a87d30a2f6b033de64b6470 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: Committing to Omid
Dear Edward, I don't have any idea why you guys can't commit to the repo (you and Jonathan are supposed to be committers too.) If you are trying to commit directly to the github apache repo, that's not supported by the Apache infrastructure AFAIK. The configuration I have for doing commits into the Omid incubator repo is: $ git remote show apache * remote apache Fetch URL: https://git-wip-us.apache.org/repos/asf/incubator-omid.git Push URL: https://git-wip-us.apache.org/repos/asf/incubator-omid.git HEAD branch: master Remote branches: 0.8.2.0 tracked master tracked Local branches configured for 'git pull': 0.8.2.0 merges with remote 0.8.2.0 apache-master merges with remote master Local refs configured for 'git push': 0.8.2.0 pushes to 0.8.2.0 (up to date) master pushes to master (local out of date) If you are going to commit code related to the Phoenix integration, I strongly suggest that you create a branch for it (e.g. phoenix-integration,) in order to avoid doing it in the master branch for now, especially if the new code introduces incompatible or major changes to the current codebase. We're working to make a release (there are some reviews tagged as 0.9.0.0 that should go to the master branch) that includes HA and some some fixes related to security issues (kerberos) and bugs and has to be tested in production through the Sieve project, which it is taking some time. As is mentioned in the Omid Incubator Status page (http://incubator.apache.org/projects/omid.html), the project champion is Daniel Dai from Hortonworks. I'm forwarding this to dev@omid.incubator.apache.org and Daniel to see if someone can help with your commit problem. Thanks and best regards, Francisco On Sunday, July 9, 2017, 6:23:08 AM PDT, Edward Bortnikov wrote: Hi, Francisco, Hope all is well. As you know, Ohad is working with the Salesforce folks to make Omid a backend TP technology for Phoenix. We've made considerable progress with this goal, including commits to the Phoenix code. It's time to start committing our changes to Omid now (you have probably seen all the new jira's - very welcome to review). However, Ohad has had hard time committing the code, although he's supposed to be committer. Could you explain us how to fix that? Ask whom to fix that? Thanks,Eddie
[jira] [Commented] (OMID-66) Clean commit table entries lower than the LWM
[ https://issues.apache.org/jira/browse/OMID-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16039475#comment-16039475 ] Francisco Perez-Sorrosal commented on OMID-66: -- [~ruchirc] 1. Regarding the frequency of cleaning: We can define a configuration option for the coprocessor with the corresponding key, similar to the one used in the current coprocessor for getting the commit table name: https://github.com/apache/incubator-omid/blob/master/hbase-coprocessor/src/main/java/org/apache/omid/transaction/OmidCompactor.java#L82 e.g. private static final String HBASE_CT_CLEANER_FREQUENCY_IN_MINUTES_KEY = "omid.hbase.commitTableCleaner.cleaningFrequencyInMinutes"; 2. Regarding the utilization of the timestamp as identifier of the commit table entries older than the low watermark: In this code https://git.corp.yahoo.com/fperez/omid/blob/master/hbase-commit-table/src/main/java/org/apache/omid/committable/hbase/HBaseCommitTable.java#L101 you can see that we use the start timestamp as HBase timestamp, so yes, the entries in the commit table contain the same info as in the row key and it can be used as identifier 3. Regarding the statistics: I'm not sure what is the best method to report statistics in HBase coprocessors. Long time ago I submitted this PR (https://github.com/apache/incubator-omid/pull/7) for adding statistics to the current compactor coprocessor but nobody has reviewed yet. Do you know the approach used in the PR is standard in the HBase community? If yes, we can follow the same approach as in the PR I submitted. Otherwise, for now you can add just a log line informing about the number of entries scanned vs removed in each coprocessor execution. > Clean commit table entries lower than the LWM > - > > Key: OMID-66 > URL: https://issues.apache.org/jira/browse/OMID-66 > Project: Apache Omid > Issue Type: Improvement > Reporter: Francisco Perez-Sorrosal >Assignee: ruchir choudhry >Priority: Minor > > The entries of the committed transactions in the commit table that clients > were not able remove (e.g. because they failed) stay there as trash. There > should be a mechanism (e.g. in form of a coprocessor) to remove those entries. > The cleaning mechanism should run periodically, reading the current low > watermark and removing the commit table entries older than the read low > watermark. Statistics such as the number of cleaned entries would be nice to > have. > Up to now we haven't seen a degraded performance in production systems > because of this fact, but it could be a potential problem at some point in > the future. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OMID-69) Provide Apache Incubator Report June 2017
[ https://issues.apache.org/jira/browse/OMID-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16039280#comment-16039280 ] Francisco Perez-Sorrosal commented on OMID-69: -- Report added to Apache wiki: https://wiki.apache.org/incubator/June2017 > Provide Apache Incubator Report June 2017 > - > > Key: OMID-69 > URL: https://issues.apache.org/jira/browse/OMID-69 > Project: Apache Omid > Issue Type: Task > Reporter: Francisco Perez-Sorrosal > Assignee: Francisco Perez-Sorrosal > > See Draft below: > Omid > Omid is a flexible, reliable, high performant and scalable ACID transactional > framework that allows client applications to execute transactions on top of > MVCC key/value-based NoSQL datastores (currently Apache HBase) providing > Snapshot Isolation guarantees on the accessed data. > Omid has been incubating since 2016-03-28. > Three most important issues to address in the move towards graduation: > 1. Boost project dissemination in the Apache community. > 2. Collaborate/integrate Omid with other Apache projects. > 3. Get positive feedback from other projects currently > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be > aware of? > N/A > How has the community developed since the last report? > 2 new contributors > Omid presented in the Apache Conf US in comparison to other Apache TMs for > HBase. It will be presented also in HBase conf in mid June. > Meeting with Apache Tephra contributors > How has the project developed since the last report? > Several bugs discovered and working on fixes. > Continue working on next release. Testing in prod env. > Quarter Stats (from: 2017-03-01 to: 2017-05-31): > +-+ > | Metric | counts | > +-+ > | # of msgs in dev list | 60| > | Active Contributors (incl mentors)|8| > | Jira New Issues |8| > | Resolved Issues |2| > | Pull Requests merged |1| > | Pull Requests proposed|3| > +-+ > 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: > 2016-06-24 > When were the last committers or PPMC members elected? > Signed-off-by: > [ ](omid) Alan Gates > Comments: > [ ](omid) Lars Hofhansl > Comments: > [ ](omid) Flavio P. Junqueira > Comments: > [ ](omid) Thejas Nair > Comments: > [ ](omid) James Taylor > Comments: > IPMC/Shepherd notes: -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OMID-69) Provide Apache Incubator Report June 2017
Francisco Perez-Sorrosal created OMID-69: Summary: Provide Apache Incubator Report June 2017 Key: OMID-69 URL: https://issues.apache.org/jira/browse/OMID-69 Project: Apache Omid Issue Type: Task Reporter: Francisco Perez-Sorrosal Assignee: Francisco Perez-Sorrosal See Draft below: Omid Omid is a flexible, reliable, high performant and scalable ACID transactional framework that allows client applications to execute transactions on top of MVCC key/value-based NoSQL datastores (currently Apache HBase) providing Snapshot Isolation guarantees on the accessed data. Omid has been incubating since 2016-03-28. Three most important issues to address in the move towards graduation: 1. Boost project dissemination in the Apache community. 2. Collaborate/integrate Omid with other Apache projects. 3. Get positive feedback from other projects currently Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? N/A How has the community developed since the last report? 2 new contributors Omid presented in the Apache Conf US in comparison to other Apache TMs for HBase. It will be presented also in HBase conf in mid June. Meeting with Apache Tephra contributors How has the project developed since the last report? Several bugs discovered and working on fixes. Continue working on next release. Testing in prod env. Quarter Stats (from: 2017-03-01 to: 2017-05-31): +-+ | Metric | counts | +-+ | # of msgs in dev list | 60| | Active Contributors (incl mentors)|8| | Jira New Issues |8| | Resolved Issues |2| | Pull Requests merged |1| | Pull Requests proposed|3| +-+ 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: 2016-06-24 When were the last committers or PPMC members elected? Signed-off-by: [ ](omid) Alan Gates Comments: [ ](omid) Lars Hofhansl Comments: [ ](omid) Flavio P. Junqueira Comments: [ ](omid) Thejas Nair Comments: [ ](omid) James Taylor Comments: IPMC/Shepherd notes: -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (OMID-60) Provide Apache Incubator Report March 2017
[ https://issues.apache.org/jira/browse/OMID-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Perez-Sorrosal closed OMID-60. Resolution: Done See it here: https://wiki.apache.org/incubator/March2017 > Provide Apache Incubator Report March 2017 > -- > > Key: OMID-60 > URL: https://issues.apache.org/jira/browse/OMID-60 > Project: Apache Omid > Issue Type: Task > Reporter: Francisco Perez-Sorrosal > Assignee: Francisco Perez-Sorrosal > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OMID-65) Extend HBaseOmidClientConfiguration creation methods
[ https://issues.apache.org/jira/browse/OMID-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Perez-Sorrosal updated OMID-65: - Fix Version/s: 0.9.0.0 > Extend HBaseOmidClientConfiguration creation methods > > > Key: OMID-65 > URL: https://issues.apache.org/jira/browse/OMID-65 > Project: Apache Omid > Issue Type: New Feature > Reporter: Francisco Perez-Sorrosal >Assignee: Sheridan Rawlins >Priority: Minor > Fix For: 0.9.0.0 > > > Add a constructor that takes a Properties (via its parent-interface of Map ?>) for properties to be used. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OMID-65) Extend HBaseOmidClientConfiguration creation methods
[ https://issues.apache.org/jira/browse/OMID-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16034204#comment-16034204 ] Francisco Perez-Sorrosal commented on OMID-65: -- +1 > Extend HBaseOmidClientConfiguration creation methods > > > Key: OMID-65 > URL: https://issues.apache.org/jira/browse/OMID-65 > Project: Apache Omid > Issue Type: New Feature > Reporter: Francisco Perez-Sorrosal >Assignee: Sheridan Rawlins >Priority: Minor > > Add a constructor that takes a Properties (via its parent-interface of Map ?>) for properties to be used. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OMID-65) Extend HBaseOmidClientConfiguration creation methods
[ https://issues.apache.org/jira/browse/OMID-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Perez-Sorrosal reassigned OMID-65: Assignee: Sheridan Rawlins > Extend HBaseOmidClientConfiguration creation methods > > > Key: OMID-65 > URL: https://issues.apache.org/jira/browse/OMID-65 > Project: Apache Omid > Issue Type: New Feature > Reporter: Francisco Perez-Sorrosal >Assignee: Sheridan Rawlins >Priority: Minor > > Add a constructor that takes a Properties (via its parent-interface of Map ?>) for properties to be used. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (OMID-66) Clean commit table entries lower than the LWM
[ https://issues.apache.org/jira/browse/OMID-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Perez-Sorrosal reassigned OMID-66: Assignee: ruchir choudhry > Clean commit table entries lower than the LWM > - > > Key: OMID-66 > URL: https://issues.apache.org/jira/browse/OMID-66 > Project: Apache Omid > Issue Type: Improvement > Reporter: Francisco Perez-Sorrosal >Assignee: ruchir choudhry >Priority: Minor > > The entries of the committed transactions in the commit table that clients > were not able remove (e.g. because they failed) stay there as trash. There > should be a mechanism (e.g. in form of a coprocessor) to remove those entries. > The cleaning mechanism should run periodically, reading the current low > watermark and removing the commit table entries older than the read low > watermark. Statistics such as the number of cleaned entries would be nice to > have. > Up to now we haven't seen a degraded performance in production systems > because of this fact, but it could be a potential problem at some point in > the future. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Re: Hello Omid dev team
> [INFO] >> > [INFO] --- maven-assembly-plugin:2.4:single (make-assembly) @ >> > omid-benchmarks --- >> > [INFO] Reading assembly descriptor: maven/assembly/bin.xml >> > [WARNING] NOTE: Currently, inclusion of module dependencies may produce >> > unpredictable results if a version conflict occurs. >> > [INFO] Building tar: >> > /Users/r0choud/incubator-omid/benchmarks/target/omid- >> > benchmarks-0.8.2.11-SNAPSHOT-bin.tar.gz >> > [INFO] >> > [INFO] --- license-maven-plugin:2.11:check (check-license) @ >> > omid-benchmarks --- >> > [INFO] Checking licenses... >> > [INFO] >> > [INFO] --- maven-install-plugin:2.4:install (default-install) @ >> > omid-benchmarks --- >> > [INFO] Installing >> > /Users/r0choud/incubator-omid/benchmarks/target/omid- >> > benchmarks-0.8.2.11-SNAPSHOT.jar >> > to >> > /Users/r0choud/.m2/repository/org/apache/omid/omid- >> > benchmarks/0.8.2.11-SNAPSHOT/omid-benchmarks-0.8.2.11-SNAPSHOT.jar >> > [INFO] Installing /Users/r0choud/incubator-omid/benchmarks/pom.xml to >> > /Users/r0choud/.m2/repository/org/apache/omid/omid- >> > benchmarks/0.8.2.11-SNAPSHOT/omid-benchmarks-0.8.2.11-SNAPSHOT.pom >> > [INFO] Installing >> > /Users/r0choud/incubator-omid/benchmarks/target/omid- >> > benchmarks-0.8.2.11-SNAPSHOT-bin.tar.gz >> > to >> > /Users/r0choud/.m2/repository/org/apache/omid/omid- >> > benchmarks/0.8.2.11-SNAPSHOT/omid-benchmarks-0.8.2.11-SNAPSH >> OT-bin.tar.gz >> > [INFO] >> > [INFO] >> > >> >> > [INFO] Building Timestamp Storage 0.8.2.11-SNAPSHOT >> > [INFO] >> > >> >> > [INFO] >> > [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ >> > omid-timestamp-storage --- >> > [INFO] Deleting /Users/r0choud/incubator-omid/timestamp-storage/target >> > [INFO] >> > [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ >> > omid-timestamp-storage --- >> > [INFO] Using 'UTF-8' encoding to copy filtered resources. >> > [INFO] skip non existing resourceDirectory >> > /Users/r0choud/incubator-omid/timestamp-storage/src/main/resources >> > [INFO] >> > [INFO] --- maven-compiler-plugin:3.5:compile (default-compile) @ >> > omid-timestamp-storage --- >> > [INFO] Changes detected - recompiling the module! >> > [INFO] Compiling 10 source files to >> > /Users/r0choud/incubator-omid/timestamp-storage/target/classes >> > [INFO] >> > [INFO] --- maven-resources-plugin:2.6:testResources >> > (default-testResources) >> > @ omid-timestamp-storage --- >> > [INFO] Using 'UTF-8' encoding to copy filtered resources. >> > [INFO] Copying 1 resource >> > [INFO] >> > [INFO] --- maven-compiler-plugin:3.5:testCompile (default-testCompile) >> @ >> > omid-timestamp-storage --- >> > [INFO] Changes detected - recompiling the module! >> > [INFO] Compiling 2 source files to >> > /Users/r0choud/incubator-omid/timestamp-storage/target/test-classes >> > [INFO] >> > [INFO] --- maven-surefire-plugin:2.19:test (default-test) @ >> > omid-timestamp-storage --- >> > [INFO] Tests are skipped. >> > [INFO] >> > [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ >> omid-timestamp-storage >> > --- >> > [INFO] Building jar: >> > /Users/r0choud/incubator-omid/timestamp-storage/target/omid- >> > timestamp-storage-0.8.2.11-SNAPSHOT.jar >> > [INFO] >> > [INFO] --- license-maven-plugin:2.11:check (check-license) @ >> > omid-timestamp-storage --- >> > [INFO] Checking licenses... >> > [INFO] >> > [INFO] --- maven-install-plugin:2.4:install (default-install) @ >> > omid-timestamp-storage --- >> > [INFO] Installing >> > /Users/r0choud/incubator-omid/timestamp-storage/target/omid- >> > timestamp-storage-0.8.2.11-SNAPSHOT.jar >> > to >> > /Users/r0choud/.m2/repository/org/apache/omid/omid- >> > timestamp-storage/0.8.2.11-SNAPSHOT/omid-timestamp- >> > storage-0.8.2.11-SNAPSHOT.jar >> > [INFO] Installing /Users/r0choud/incubator-omid/ >> timestamp-storage/pom.xml >> > to >> > /Users/r0choud/.m2/repository/org/apache/omid/omid- >> > timestamp-storage/0.8.2.11-SNAPSHOT/omid-timestamp- >> > storage-0.8.2.11-SNAPSHOT.pom >> > [INFO] >> > [INFO] >> > >> >> > [INFO] Building HBase tools 0.8.2.11-SNAPSHOT >> > [INFO] >> > >> >> > [INFO] >> > [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ >> omid-hbase-tools >> > --- >> > [INFO] Deleting /Users/r0choud/incubator-omid/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/r0choud/incubator-omid/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/r0choud/incubator-omid/hbase-tools/target/classes >> > [INFO] - >> > [ERROR] COMPILATION ERROR : >> > [INFO] - >> > [ERROR] >> > /Users/r0choud/incubator-omid/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/r0choud/incubator-omid/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 >> > [INFO] - >> > [INFO] >> > >> >> > [INFO] Reactor Summary: >> > [INFO] >> > [INFO] Omid ... SUCCESS [ >> > 0.743 s] >> > [INFO] Common . SUCCESS [ >> > 3.392 s] >> > [INFO] State Machine .. SUCCESS [ >> > 0.198 s] >> > [INFO] Commit Table ... SUCCESS [ >> > 0.343 s] >> > [INFO] Metrics SUCCESS [ >> > 0.207 s] >> > [INFO] Transaction Client . SUCCESS [ >> > 0.471 s] >> > [INFO] HBase Common ... SUCCESS [ >> > 0.761 s] >> > [INFO] HBase Commit Table . SUCCESS [ >> > 0.492 s] >> > [INFO] Codahale Metrics ... SUCCESS [ >> > 0.119 s] >> > [INFO] Benchmarks . SUCCESS [ >> > 6.314 s] >> > [INFO] Timestamp Storage .. SUCCESS [ >> > 0.412 s] >> > [INFO] HBase tools FAILURE [ >> > 0.134 s] >> > [INFO] TSO and TO Servers . SKIPPED >> > [INFO] Shims Aggregator for HBase . SKIPPED >> > [INFO] Shims layer for HBase 0.x .. SKIPPED >> > [INFO] Shims layer for HBase 1.x .. SKIPPED >> > [INFO] HBase Client ... SKIPPED >> > [INFO] HBase Coprocessors . SKIPPED >> > [INFO] Omid Client Examples ... SKIPPED >> > [INFO] Omid Packaging . SKIPPED >> > [INFO] >> > >> >> > [INFO] BUILD FAILURE >> > [INFO] >> > >> >> > [INFO] Total time: 13.945 s >> > [INFO] Finished at: 2017-05-15T16:40:59-07:00 >> > [INFO] Final Memory: 52M/508M >> > [INFO] >> > >> >> > [ERROR] Failed to execute goal >> > org.apache.maven.plugins:maven-compiler-plugin:3.5:compile >> > (default-compile) on project omid-hbase-tools: Compilation failure: >> > Compilation failure: >> > [ERROR] >> > /Users/r0choud/incubator-omid/hbase-tools/src/main/java/org/ >> > apache/omid/tools/hbase/OmidTableManager.java:[33,23] >> > cannot find symbol >> > [ERROR] symbol: class HBaseShims >> > [ERROR] location: package org.apache.omid >> > [ERROR] >> > /Users/r0choud/incubator-omid/hbase-tools/src/main/java/org/ >> > apache/omid/tools/hbase/OmidTableManager.java:[153,13] >> > cannot find symbol >> > [ERROR] symbol: variable HBaseShims >> > [ERROR] location: class org.apache.omid.tools.hbase.OmidTableManager >> > [ERROR] -> [Help 1] >> > [ERROR] >> > [ERROR] To see the full stack trace of the errors, re-run Maven with >> the -e >> > switch. >> > [ERROR] Re-run Maven using the -X switch to enable full debug logging. >> > [ERROR] >> > [ERROR] For more information about the errors and possible solutions, >> > please read the following articles: >> > [ERROR] [Help 1] >> > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException >> > [ERROR] >> > [ERROR] After correcting the problems, you can resume the build with the >> > command >> > [ERROR] mvn -rf :omid-hbase-tools >> > >> > On Wed, Apr 12, 2017 at 10:25 PM, Francisco Perez-Sorrosal < >> > fpe...@yahoo-inc.com.invalid> wrote: >> > >> > > Hi Ruchir, >> > > First, of all welcome! >> > > You can download the release from here: >> https://dist.apache.org/repos/ >> > > dist/release/incubator/omid/omid-incubating-0.8.2.0/Then you can >> follow >> > > the instructions in: https://omid.incubator.apache. >> > > org/quickstart.htmlGeneral info about the Omid components is in here: >> > > https://omid.incubator.apache.org/omid-components.htmlThe default >> > > configuration of the TSO contains examples on how to tune it to your >> > > environment: https://github.com/apache/incubator-omid/blob/master/ >> > > tso-server/src/main/resources/default-omid-server- >> > configuration.ymlFinally, >> > > there´s a module with examples that also show how to configure the >> > clients: >> > > https://github.com/apache/incubator-omid/tree/master/examples >> > > Hope this helps as starting point. >> > > Thanks and best regards, >> > > Francisco >> > > On Wednesday, April 12, 2017, 9:56:59 PM PDT, Ruchir Choudhry < >> > > ruchirchoudhr...@gmail.com> wrote:Do we have a setup doc for Omid, I >> > want >> > > to contribute to this project. >> > > >> > > Regards, >> > > Ruchir >> > > >> > >> >> >> >> -- >> Francisco Pérez-Sorrosal >> > >
[jira] [Updated] (OMID-66) Clean commit table entries lower than the LWM
[ https://issues.apache.org/jira/browse/OMID-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Perez-Sorrosal updated OMID-66: - Description: The entries of the committed transactions in the commit table that clients were not able remove (e.g. because they failed) stay there as trash. There should be a mechanism (e.g. in form of a coprocessor) to remove those entries. The cleaning mechanism should run periodically, reading the current low watermark and removing the commit table entries older than the read low watermark. Statistics such as the number of cleaned entries would be nice to have. Up to now we haven't seen a degraded performance in production systems because of this fact, but it could be a potential problem at some point in the future. was: The entries of the committed transactions in the commit table that clients were not able remove (e.g. because they failed) stay there as trash. There should be a mechanism (e.g. in form of a coprocessor) to remove those entries. Up to now we haven't seen a degraded performance in production systems because of this fact, but it could be a potential problem at some point in the future. > Clean commit table entries lower than the LWM > - > > Key: OMID-66 > URL: https://issues.apache.org/jira/browse/OMID-66 > Project: Apache Omid > Issue Type: Improvement > Reporter: Francisco Perez-Sorrosal >Priority: Minor > > The entries of the committed transactions in the commit table that clients > were not able remove (e.g. because they failed) stay there as trash. There > should be a mechanism (e.g. in form of a coprocessor) to remove those entries. > The cleaning mechanism should run periodically, reading the current low > watermark and removing the commit table entries older than the read low > watermark. Statistics such as the number of cleaned entries would be nice to > have. > Up to now we haven't seen a degraded performance in production systems > because of this fact, but it could be a potential problem at some point in > the future. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OMID-68) Improve documentation to mention HBase profiles when compiling
[ https://issues.apache.org/jira/browse/OMID-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Perez-Sorrosal updated OMID-68: - Description: Mention the profiles to use at least in here http://omid.incubator.apache.org/quickstart.html: -Phbase-0 or -Phbase-1 was: Mention the profiles to use: -Phbase-0 or -Phbase-1 > Improve documentation to mention HBase profiles when compiling > -- > > Key: OMID-68 > URL: https://issues.apache.org/jira/browse/OMID-68 > Project: Apache Omid > Issue Type: Improvement > Reporter: Francisco Perez-Sorrosal > > Mention the profiles to use at least in here > http://omid.incubator.apache.org/quickstart.html: > -Phbase-0 > or > -Phbase-1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OMID-68) Improve documentation to mention HBase profiles when compiling
[ https://issues.apache.org/jira/browse/OMID-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16011552#comment-16011552 ] Francisco Perez-Sorrosal commented on OMID-68: -- Users may have problems with this fact if not documented: https://lists.apache.org/thread.html/7ae9e81906ad8f919acee32d530157b865a72f5d2977c359366bfc09@%3Cdev.omid.apache.org%3E > Improve documentation to mention HBase profiles when compiling > -- > > Key: OMID-68 > URL: https://issues.apache.org/jira/browse/OMID-68 > Project: Apache Omid > Issue Type: Improvement > Reporter: Francisco Perez-Sorrosal > > Mention the profiles to use: > -Phbase-0 > or > -Phbase-1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OMID-68) Improve documentation to mention HBase profiles when compiling
Francisco Perez-Sorrosal created OMID-68: Summary: Improve documentation to mention HBase profiles when compiling Key: OMID-68 URL: https://issues.apache.org/jira/browse/OMID-68 Project: Apache Omid Issue Type: Improvement Reporter: Francisco Perez-Sorrosal Mention the profiles to use: -Phbase-0 or -Phbase-1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OMID-67) Avoid Kerberos logging multiple times as it may cause race condition problems
Francisco Perez-Sorrosal created OMID-67: Summary: Avoid Kerberos logging multiple times as it may cause race condition problems Key: OMID-67 URL: https://issues.apache.org/jira/browse/OMID-67 Project: Apache Omid Issue Type: Bug Affects Versions: 0.8.2.0 Reporter: Francisco Perez-Sorrosal Assignee: Francisco Perez-Sorrosal Weird behaviour has been detected after the ticket expired when multiple logins to kerberos are triggered from different HBase modules in the TSO. The result is that the Kerberos ticket is not renewed and it causing this exception to be thrown: 2017-05-09 23:11:28,234 [tso-state-initializer] INFO TSOStateManagerImpl TSO Server state LWM 178000/Epoch 178000 2017-05-09 23:11:28,247 [tso-state-initializer] INFO LeaseManager TSO instance 10.215.69.146:54758 (Epoch 178000) advertised through ZK 2017-05-10 23:14:23,582 [htable-pool6-t269] WARN RpcClient Exception encountered while connecting to the server : javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt)] 2017-05-10 23:14:23,583 [htable-pool6-t269] FATAL RpcClient SASL authentication failed. The most likely cause is missing or invalid credentials. Consider 'kinit'. javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt)] at com.sun.security.sasl.gsskerb.GssKrb5Client.evaluateChallenge(GssKrb5Client.java:211) at org.apache.hadoop.hbase.security.HBaseSaslRpcClient.saslConnect(HBaseSaslRpcClient.java:197) at org.apache.hadoop.hbase.ipc.RpcClient$Connection.setupSaslConnection(RpcClient.java:770) at org.apache.hadoop.hbase.ipc.RpcClient$Connection.access$600(RpcClient.java:357) at org.apache.hadoop.hbase.ipc.RpcClient$Connection$2.run(RpcClient.java:891) at org.apache.hadoop.hbase.ipc.RpcClient$Connection$2.run(RpcClient.java:888) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Subject.java:422) at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1637) at org.apache.hadoop.hbase.ipc.RpcClient$Connection.setupIOstreams(RpcClient.java:888) at org.apache.hadoop.hbase.ipc.RpcClient.getConnection(RpcClient.java:1543) at org.apache.hadoop.hbase.ipc.RpcClient.call(RpcClient.java:1442) at org.apache.hadoop.hbase.ipc.RpcClient.callBlockingMethod(RpcClient.java:1661) at org.apache.hadoop.hbase.ipc.RpcClient$BlockingRpcChannelImplementation.callBlockingMethod(RpcClient.java:1719) at org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$BlockingStub.multi(ClientProtos.java:30085) at org.apache.hadoop.hbase.client.MultiServerCallable.call(MultiServerCallable.java:113) at org.apache.hadoop.hbase.client.MultiServerCallable.call(MultiServerCallable.java:51) at org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithoutRetries(RpcRetryingCaller.java:180) at org.apache.hadoop.hbase.client.AsyncProcess$1.run(AsyncProcess.java:543) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: GSSException: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt) at sun.security.jgss.krb5.Krb5InitCredential.getInstance(Krb5InitCredential.java:147) at sun.security.jgss.krb5.Krb5MechFactory.getCredentialElement(Krb5MechFactory.java:122) at sun.security.jgss.krb5.Krb5MechFactory.getMechanismContext(Krb5MechFactory.java:187) at sun.security.jgss.GSSManagerImpl.getMechanismContext(GSSManagerImpl.java:224) at sun.security.jgss.GSSContextImpl.initSecContext(GSSContextImpl.java:212) at sun.security.jgss.GSSContextImpl.initSecContext(GSSContextImpl.java:179) at com.sun.security.sasl.gsskerb.GssKrb5Client.evaluateChallenge(GssKrb5Client.java:192) ... 23 more 2017-05-10 23:14:24,608 [htable-pool6-t269] WARN RpcClient Exception encountered while connecting to the server : javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt)] 2017-05-10 23:14:24,608 [htable-pool6-t269] FATAL RpcClient SASL authentication failed. The most likely cause is missing or invalid credentials. Consi
Re: Hello Omid dev team
Hi Ruchir, First, of all welcome! You can download the release from here: https://dist.apache.org/repos/dist/release/incubator/omid/omid-incubating-0.8.2.0/Then you can follow the instructions in: https://omid.incubator.apache.org/quickstart.htmlGeneral info about the Omid components is in here: https://omid.incubator.apache.org/omid-components.htmlThe default configuration of the TSO contains examples on how to tune it to your environment: https://github.com/apache/incubator-omid/blob/master/tso-server/src/main/resources/default-omid-server-configuration.ymlFinally, there´s a module with examples that also show how to configure the clients: https://github.com/apache/incubator-omid/tree/master/examples Hope this helps as starting point. Thanks and best regards, Francisco On Wednesday, April 12, 2017, 9:56:59 PM PDT, Ruchir Choudhry wrote:Do we have a setup doc for Omid, I want to contribute to this project. Regards, Ruchir
[jira] [Created] (OMID-66) Clean commit table entries lower than the LWM
Francisco Perez-Sorrosal created OMID-66: Summary: Clean commit table entries lower than the LWM Key: OMID-66 URL: https://issues.apache.org/jira/browse/OMID-66 Project: Apache Omid Issue Type: Improvement Reporter: Francisco Perez-Sorrosal Priority: Minor The entries of the committed transactions in the commit table that clients were not able remove (e.g. because they failed) stay there as trash. There should be a mechanism (e.g. in form of a coprocessor) to remove those entries. Up to now we haven't seen a degraded performance in production systems because of this fact, but it could be a potential problem at some point in the future. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Re: Omid PR
Missed the PR link: https://github.com/apache/incubator-omid/pull/9/commits/7991f76eb5b2e4e31bbbd7ccf6599d8f5d730dc6 On Thursday, March 30, 2017, 8:08:53 AM PDT, Francisco Perez-Sorrosal wrote:Hi Daniel & Ohad, I'm integrating the current Omid into Sieve and I need someone to go over this PR, could you please take a look at it? Thanks, Francisco
Omid PR
Hi Daniel & Ohad, I'm integrating the current Omid into Sieve and I need someone to go over this PR, could you please take a look at it? Thanks, Francisco
[jira] [Commented] (OMID-65) Extend HBaseOmidClientConfiguration creation methods
[ https://issues.apache.org/jira/browse/OMID-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15946329#comment-15946329 ] Francisco Perez-Sorrosal commented on OMID-65: -- PR contributed by [~sheridanrawlins] here: https://github.com/apache/incubator-omid/pull/11 > Extend HBaseOmidClientConfiguration creation methods > > > Key: OMID-65 > URL: https://issues.apache.org/jira/browse/OMID-65 > Project: Apache Omid > Issue Type: New Feature > Reporter: Francisco Perez-Sorrosal >Priority: Minor > > Add a constructor that takes a Properties (via its parent-interface of Map ?>) for properties to be used. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OMID-65) Extend HBaseOmidClientConfiguration creation methods
Francisco Perez-Sorrosal created OMID-65: Summary: Extend HBaseOmidClientConfiguration creation methods Key: OMID-65 URL: https://issues.apache.org/jira/browse/OMID-65 Project: Apache Omid Issue Type: New Feature Reporter: Francisco Perez-Sorrosal Priority: Minor Add a constructor that takes a Properties (via its parent-interface of Map) for properties to be used. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Re: Add a new community members for Omid
Thanks for this clarification Flavio. Thanks, Francisco On Sunday, March 19, 2017, 7:48:16 AM PDT, Flavio Junqueira wrote:I'm sorry about the delay in responding, I've been unavailable for a few days. We should always target offering committership to community members that have been contributing consistently to the community. There is no single way to determine when someone is ready and ach community needs to decide where to set the bar for committership, which can even fluctuate over time. The one point I want to stress here is that it is not necessary to be a committer to contribute. Anyone can propose changes and patches. Contributing prior to having committer status is typically the case in Apache projects. Thanks, -Flavio > On 07 Mar 2017, at 19:49, Francisco Perez-Sorrosal > wrote: > > Dear all, > Is it possible to add Kostas (cc'ed) as a committer to the Omid project? Also > Ohad commented me last week that there's also another person in Haifa working > in Omid (Yonatan Gottesman, also CC'ed), so if he is interested in being a > committer maybe he can follow the process too (I'm also adding another person > in our team at Yahoo -Ganesan Sriram- just in case he's interested too.) What > steps do they need to follow to be onboard? > Ohad commented me last week that he's not receiving the notifications in the > dev list where the new JIRA's requests arrive. They appear in the dev list as > far I can see here > (http://mail-archives.apache.org/mod_mbox/incubator-omid-dev/201703.mbox/browser)Are > your receiving notifications, or is there any problem with the list (or it's > just a config issue)? He seems to be receiving the Phoenix notifications but > not the Omid ones. > Also the CI process is broken due to a change in the protobuf location, what > prevents other PR to be validated. Last week I put the fix in here but > someone should review it and approve it > (https://github.com/apache/incubator-omid/pull/10) > Thanks in advance, > Francisco
[jira] [Closed] (OMID-64) Fix location of protobuf tgz in travis config
[ https://issues.apache.org/jira/browse/OMID-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Perez-Sorrosal closed OMID-64. Resolution: Fixed > Fix location of protobuf tgz in travis config > - > > Key: OMID-64 > URL: https://issues.apache.org/jira/browse/OMID-64 > Project: Apache Omid > Issue Type: Bug > Reporter: Francisco Perez-Sorrosal > Assignee: Francisco Perez-Sorrosal > > Apparently the location has changed in the repo maintained by google to > https://github.com/google/protobuf/releases/download/v2.5.0/protobuf-2.5.0.tar.gz -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Add a new community members for Omid
Dear all, Is it possible to add Kostas (cc'ed) as a committer to the Omid project? Also Ohad commented me last week that there's also another person in Haifa working in Omid (Yonatan Gottesman, also CC'ed), so if he is interested in being a committer maybe he can follow the process too (I'm also adding another person in our team at Yahoo -Ganesan Sriram- just in case he's interested too.) What steps do they need to follow to be onboard? Ohad commented me last week that he's not receiving the notifications in the dev list where the new JIRA's requests arrive. They appear in the dev list as far I can see here (http://mail-archives.apache.org/mod_mbox/incubator-omid-dev/201703.mbox/browser)Are your receiving notifications, or is there any problem with the list (or it's just a config issue)? He seems to be receiving the Phoenix notifications but not the Omid ones. Also the CI process is broken due to a change in the protobuf location, what prevents other PR to be validated. Last week I put the fix in here but someone should review it and approve it (https://github.com/apache/incubator-omid/pull/10) Thanks in advance, Francisco
[jira] [Commented] (OMID-58) Snapshot isolation violation in read only transactions
[ https://issues.apache.org/jira/browse/OMID-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15895316#comment-15895316 ] Francisco Perez-Sorrosal commented on OMID-58: -- Hey [~ohads]. There's no need to go to the TSO as we can do it from the Client side. I started working on a fix for this in the past but I stopped cause I realized that it would be better do first some refactoring to improve how we manage the pre/post hooks for the AbstractTM and remove the TransactionException from the interface exposed to the users. Anyways, I've put in here the draft of what I did: https://github.com/francisco-perez-sorrosal/incubator-omid/commit/2990ea706735a2b7f980c96cd266b174c5ab3133 The round-trip to the database could be avoided if we store the LWM in ZK and we put a watcher in the client, but this could potentially create more problems. > Snapshot isolation violation in read only transactions > -- > > Key: OMID-58 > URL: https://issues.apache.org/jira/browse/OMID-58 > Project: Apache Omid > Issue Type: Bug >Reporter: Ohad Shacham > > Read only transactions in snapshot isolation cannot conflict with any other > transaction. Therefore, the commit process does not contact the TSO and mark > the transaction as committed. > This can cause to snapshot isolation violation in cases where the coprocessor > deletes information from HBase that changes the snapshot of an inflight read > only transaction t. t in this case will be marked as committed, even thought > it did not read a consistent snapshot. > t would be aborted if the commit process would contact the tso because its > read timestamp is smaller than the low water mark. > A solution for this would be to contact the TSO, check the low water mark, > identify in the requestProcessor that the transaction is read only, and > immediately return a result using the reply processor. This will reduce the > latency (v.s. the regular flow) of read only transactions, while maintaining > snapshot isolation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] incubator-omid pull request #10: [OMID-64] Fix location of protobuf tgz in t...
GitHub user francisco-perez-sorrosal opened a pull request: https://github.com/apache/incubator-omid/pull/10 [OMID-64] Fix location of protobuf tgz in travis config Location has changed to https://github.com/google/protobuf/releases/download/v2.5.0/protobuf-2.5.0.tar.gz Change-Id: Icd7740ff23bf17142fb47bdc530178b0292b3a05 You can merge this pull request into a Git repository by running: $ git pull https://github.com/francisco-perez-sorrosal/incubator-omid fix-protobuf-location Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-omid/pull/10.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 #10 commit 0c371361781957c96b20295290a167f7be3b33e2 Author: Francisco Perez-Sorrosal Date: 2017-03-03T18:35:48Z [OMID-64] Fix location of protobuf tgz in travis config Location has changed to https://github.com/google/protobuf/releases/download/v2.5.0/protobuf-2.5.0.tar.gz Change-Id: Icd7740ff23bf17142fb47bdc530178b0292b3a05 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Created] (OMID-64) Fix location of protobuf tgz in travis config
Francisco Perez-Sorrosal created OMID-64: Summary: Fix location of protobuf tgz in travis config Key: OMID-64 URL: https://issues.apache.org/jira/browse/OMID-64 Project: Apache Omid Issue Type: Bug Reporter: Francisco Perez-Sorrosal Assignee: Francisco Perez-Sorrosal Apparently the location has changed in the repo maintained by google to https://github.com/google/protobuf/releases/download/v2.5.0/protobuf-2.5.0.tar.gz -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] incubator-omid pull request #9: [OMID-62] Use interface instead of TSOClient...
GitHub user francisco-perez-sorrosal reopened a pull request: https://github.com/apache/incubator-omid/pull/9 [OMID-62] Use interface instead of TSOClient in AbstractTransactionMa⦠â¦nager This will make it easy to mock AbstractTransactionManager dependencies Change-Id: Ia3c0d59261d2c8abba4509ff7d97ada93e69c758 You can merge this pull request into a Git repository by running: $ git pull https://github.com/francisco-perez-sorrosal/incubator-omid improve-tsoclient-dependency Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-omid/pull/9.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 #9 commit c82e0b3694c07bde03c8473717f77dd4f3ad1ea0 Author: Francisco Perez-Sorrosal Date: 2017-03-03T01:26:02Z [OMID-62] Use interface instead of TSOClient in AbstractTransactionManager This will make it easy to mock AbstractTransactionManager dependencies Change-Id: Ia3c0d59261d2c8abba4509ff7d97ada93e69c758 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] incubator-omid pull request #9: [OMID-62] Use interface instead of TSOClient...
Github user francisco-perez-sorrosal closed the pull request at: https://github.com/apache/incubator-omid/pull/9 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Updated] (OMID-63) Do not expose HBaseTransactionClient interface in HBaseTransactionManager
[ https://issues.apache.org/jira/browse/OMID-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Perez-Sorrosal updated OMID-63: - Fix Version/s: 0.9.0.0 > Do not expose HBaseTransactionClient interface in HBaseTransactionManager > - > > Key: OMID-63 > URL: https://issues.apache.org/jira/browse/OMID-63 > Project: Apache Omid > Issue Type: Bug > Reporter: Francisco Perez-Sorrosal > Assignee: Francisco Perez-Sorrosal > Fix For: 0.9.0.0 > > > We should not expose that interface to clients -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OMID-63) Do not expose HBaseTransactionClient interface in HBaseTransactionManager
Francisco Perez-Sorrosal created OMID-63: Summary: Do not expose HBaseTransactionClient interface in HBaseTransactionManager Key: OMID-63 URL: https://issues.apache.org/jira/browse/OMID-63 Project: Apache Omid Issue Type: Bug Reporter: Francisco Perez-Sorrosal Assignee: Francisco Perez-Sorrosal We should not expose that interface to clients -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OMID-44) Add reference to Yahoo code in NOTICE file
[ https://issues.apache.org/jira/browse/OMID-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Perez-Sorrosal updated OMID-44: - Fix Version/s: 0.9.0.0 > Add reference to Yahoo code in NOTICE file > -- > > Key: OMID-44 > URL: https://issues.apache.org/jira/browse/OMID-44 > Project: Apache Omid > Issue Type: Task >Affects Versions: 0.8.2.0 > Reporter: Francisco Perez-Sorrosal > Assignee: Francisco Perez-Sorrosal > Labels: license, notice > Fix For: 0.9.0.0 > > > Some files were taken from ycsb so we need to say that in NOTICE file: > ./benchmarks/src/main/java/org/apache/omid/benchmarks/utils/Generator.java > ./benchmarks/src/main/java/org/apache/omid/benchmarks/utils/IntegerGenerator.java > ./benchmarks/src/main/java/org/apache/omid/benchmarks/utils/ScrambledZipfianGenerator.java > ./benchmarks/src/main/java/org/apache/omid/benchmarks/utils/ZipfianGenerator.java -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OMID-62) Use interface instead of TSOClient in AbstractTransactionManager
[ https://issues.apache.org/jira/browse/OMID-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Perez-Sorrosal updated OMID-62: - Fix Version/s: 0.9.0.0 > Use interface instead of TSOClient in AbstractTransactionManager > > > Key: OMID-62 > URL: https://issues.apache.org/jira/browse/OMID-62 > Project: Apache Omid > Issue Type: Improvement > Reporter: Francisco Perez-Sorrosal > Assignee: Francisco Perez-Sorrosal >Priority: Minor > Fix For: 0.9.0.0 > > > This will make it easy to mock AbstractTransactionManager dependencies -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OMID-54) Leak in Compactor Coprocessor that creates an increasing number of idle threads
[ https://issues.apache.org/jira/browse/OMID-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Perez-Sorrosal updated OMID-54: - Fix Version/s: (was: 0.8.3.0) > Leak in Compactor Coprocessor that creates an increasing number of idle > threads > - > > Key: OMID-54 > URL: https://issues.apache.org/jira/browse/OMID-54 > Project: Apache Omid > Issue Type: Bug >Affects Versions: 0.8.2.0 > Reporter: Francisco Perez-Sorrosal > Assignee: Francisco Perez-Sorrosal > > The use of an structure to reuse CommitTable.Client objects has introduced a > side effect that creates an increasing number of those objects, which in turn > contain idle threads that are connected to HBase. > This is what is observed with jstack: > Thread 3047696 (omid-completor-0): > State: WAITING > Blocked count: 0 > Waited count: 1 > Waiting on > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@76e5b0a > Stack: > sun.misc.Unsafe.park(Native Method) > java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > java.util.concurrent.ArrayBlockingQueue.take(ArrayBlockingQueue.java:403) > > com.yahoo.omid.committable.hbase.HBaseCommitTable$HBaseClient.run(HBaseCommitTable.java:221) > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > java.util.concurrent.FutureTask.run(FutureTask.java:266) > > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > java.lang.Thread.run(Thread.java:745) > Thread 3047652 (omid-completor-0): > State: WAITING > Blocked count: 0 > Waited count: 1 > Waiting on > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@6e27d8fb > Stack: > sun.misc.Unsafe.park(Native Method) > java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > java.util.concurrent.ArrayBlockingQueue.take(ArrayBlockingQueue.java:403) > > com.yahoo.omid.committable.hbase.HBaseCommitTable$HBaseClient.run(HBaseCommitTable.java:221) > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > java.util.concurrent.FutureTask.run(FutureTask.java:266) > > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > java.lang.Thread.run(Thread.java:745) > Thread 3041861 (omid-completor-0): > State: WAITING > Blocked count: 0 > Waited count: 1 > Waiting on > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@5a279424 > Stack: > sun.misc.Unsafe.park(Native Method) > java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > java.util.concurrent.ArrayBlockingQueue.take(ArrayBlockingQueue.java:403) > > com.yahoo.omid.committable.hbase.HBaseCommitTable$HBaseClient.run(HBaseCommitTable.java:221) > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > java.util.concurrent.FutureTask.run(FutureTask.java:266) > > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > java.lang.Thread.run(Thread.java:745) > Thread 3041286 (omid-completor-0): > State: WAITING > Blocked count: 0 > Waited count: 2 > Waiting on > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@536fd78 > Stack: > sun.misc.Unsafe.park(Native Method) > java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > java.util.concurrent.ArrayBlockingQueue.take(ArrayBlockingQueue.java:403) > > com.yahoo.omid.committable.hbase.HBaseCommitTable$HBaseClient.run(HBaseCommitTable.java:221) > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > java.util.concurrent.FutureTask.run(FutureTask.java:266) > > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > java.lang.Thread.run(Thread.java:745) > ... -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OMID-44) Add reference to Yahoo code in NOTICE file
[ https://issues.apache.org/jira/browse/OMID-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Perez-Sorrosal updated OMID-44: - Fix Version/s: (was: 0.8.3.0) > Add reference to Yahoo code in NOTICE file > -- > > Key: OMID-44 > URL: https://issues.apache.org/jira/browse/OMID-44 > Project: Apache Omid > Issue Type: Task >Affects Versions: 0.8.2.0 > Reporter: Francisco Perez-Sorrosal > Assignee: Francisco Perez-Sorrosal > Labels: license, notice > > Some files were taken from ycsb so we need to say that in NOTICE file: > ./benchmarks/src/main/java/org/apache/omid/benchmarks/utils/Generator.java > ./benchmarks/src/main/java/org/apache/omid/benchmarks/utils/IntegerGenerator.java > ./benchmarks/src/main/java/org/apache/omid/benchmarks/utils/ScrambledZipfianGenerator.java > ./benchmarks/src/main/java/org/apache/omid/benchmarks/utils/ZipfianGenerator.java -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OMID-42) Rat report
[ https://issues.apache.org/jira/browse/OMID-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Perez-Sorrosal updated OMID-42: - Fix Version/s: (was: 0.8.3.0) > Rat report > -- > > Key: OMID-42 > URL: https://issues.apache.org/jira/browse/OMID-42 > Project: Apache Omid > Issue Type: Bug >Affects Versions: 0.8.2.0 >Reporter: Flavio Junqueira > Attachments: omid-rat-report.txt > > > As part of voting for the the 0.8.2.0 release, I've run the rat tool to check > for licenses and such. I'll attach the report that the tool generated for me > locally. I don't think there is any blocker for the current RC, but going > forward, the warnings in here need to be fixed. > It'd be great if someone else had a look at the report to make sure there is > no blocker for this release, since the project is still incubating. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OMID-48) Remove KEYS file from Omid release, and use apache email to sign
[ https://issues.apache.org/jira/browse/OMID-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Perez-Sorrosal updated OMID-48: - Fix Version/s: (was: 0.8.3.0) > Remove KEYS file from Omid release, and use apache email to sign > > > Key: OMID-48 > URL: https://issues.apache.org/jira/browse/OMID-48 > Project: Apache Omid > Issue Type: Bug >Reporter: Daniel Dai >Assignee: Daniel Dai > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OMID-39) Add statistics to Compactor coprocessor
[ https://issues.apache.org/jira/browse/OMID-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Perez-Sorrosal updated OMID-39: - Fix Version/s: (was: 0.8.3.0) > Add statistics to Compactor coprocessor > --- > > Key: OMID-39 > URL: https://issues.apache.org/jira/browse/OMID-39 > Project: Apache Omid > Issue Type: Improvement >Affects Versions: 0.8.2.0 > Reporter: Francisco Perez-Sorrosal > Assignee: Francisco Perez-Sorrosal >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] incubator-omid pull request #9: [OMID-62] Use interface instead of TSOClient...
GitHub user francisco-perez-sorrosal opened a pull request: https://github.com/apache/incubator-omid/pull/9 [OMID-62] Use interface instead of TSOClient in AbstractTransactionMa⦠â¦nager This will make it easy to mock AbstractTransactionManager dependencies Change-Id: Ia3c0d59261d2c8abba4509ff7d97ada93e69c758 You can merge this pull request into a Git repository by running: $ git pull https://github.com/francisco-perez-sorrosal/incubator-omid improve-tsoclient-dependency Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-omid/pull/9.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 #9 commit 8bd81ca4c06e586399e3465e152f2de93e4008aa Author: Francisco Perez-Sorrosal Date: 2017-03-03T01:26:02Z [OMID-62] Use interface instead of TSOClient in AbstractTransactionManager This will make it easy to mock AbstractTransactionManager dependencies Change-Id: Ia3c0d59261d2c8abba4509ff7d97ada93e69c758 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Created] (OMID-62) Use interface instead of TSOClient in AbstractTransactionManager
Francisco Perez-Sorrosal created OMID-62: Summary: Use interface instead of TSOClient in AbstractTransactionManager Key: OMID-62 URL: https://issues.apache.org/jira/browse/OMID-62 Project: Apache Omid Issue Type: Improvement Reporter: Francisco Perez-Sorrosal Assignee: Francisco Perez-Sorrosal Priority: Minor This will make it easy to mock AbstractTransactionManager dependencies -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OMID-61) pom files in generated jar files do not include version numbers
Francisco Perez-Sorrosal created OMID-61: Summary: pom files in generated jar files do not include version numbers Key: OMID-61 URL: https://issues.apache.org/jira/browse/OMID-61 Project: Apache Omid Issue Type: Bug Reporter: Francisco Perez-Sorrosal Priority: Minor e.g. see https://mvnrepository.com/artifact/org.apache.omid/omid-hbase-client/0.8.2.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (OMID-7) Evaluate logo redesign
[ https://issues.apache.org/jira/browse/OMID-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Perez-Sorrosal closed OMID-7. --- Resolution: Not A Problem > Evaluate logo redesign > --- > > Key: OMID-7 > URL: https://issues.apache.org/jira/browse/OMID-7 > Project: Apache Omid > Issue Type: New Feature >Reporter: Igor Katkov >Assignee: Igor Katkov >Priority: Minor > Fix For: 0.8.3.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OMID-60) Provide Apache Incubator Report March 2017
[ https://issues.apache.org/jira/browse/OMID-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891153#comment-15891153 ] Francisco Perez-Sorrosal commented on OMID-60: -- Added to the Apache wiki here: https://wiki.apache.org/incubator/March2017 > Provide Apache Incubator Report March 2017 > -- > > Key: OMID-60 > URL: https://issues.apache.org/jira/browse/OMID-60 > Project: Apache Omid > Issue Type: Task > Reporter: Francisco Perez-Sorrosal > Assignee: Francisco Perez-Sorrosal > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OMID-60) Provide Apache Incubator Report March 2017
[ https://issues.apache.org/jira/browse/OMID-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15886400#comment-15886400 ] Francisco Perez-Sorrosal commented on OMID-60: -- See draft below. Please add comments: Omid Omid is a flexible, reliable, high performant and scalable ACID transactional framework that allows client applications to execute transactions on top of MVCC key/value-based NoSQL datastores (currently Apache HBase) providing Snapshot Isolation guarantees on the accessed data. Omid has been incubating since 2016-03-28. Three most important issues to address in the move towards graduation: 1. Boost project dissemination in the Apache community. 2. Collaborate/integrate Omid with other Apache projects. 3. Get positive feedback from other projects currently integrating/using Omid. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? N/A How has the community developed since the last report? Started integration with Apache Phoenix community. Omid presented in the SF HBase community event in Dec. Omid paper accepted in FAST 2017 How has the project developed since the last report? Started working in the next release. Quarter Stats (from: 2016-12-01 to: 2017-02-28): +-+ | Metric | counts | +-+ | # of msgs in dev list | 36| | Active Contributors (incl mentors)|6| | Jira New Issues |4| | Resolved Issues |2| | Pull Requests merged |0| | Pull Requests proposed|0| +-+ 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: 2016-06-24 When were the last committers or PPMC members elected? Signed-off-by: [ ](omid) Alan Gates Comments: [ ](omid) Lars Hofhansl Comments: [ ](omid) Flavio P. Junqueira Comments: [ ](omid) Thejas Nair Comments: [ ](omid) James Taylor Comments: IPMC/Shepherd notes: > Provide Apache Incubator Report March 2017 > -- > > Key: OMID-60 > URL: https://issues.apache.org/jira/browse/OMID-60 > Project: Apache Omid > Issue Type: Task > Reporter: Francisco Perez-Sorrosal > Assignee: Francisco Perez-Sorrosal > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (OMID-60) Provide Apache Incubator Report March 2017
[ https://issues.apache.org/jira/browse/OMID-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francisco Perez-Sorrosal updated OMID-60: - Due Date: 1/Mar/17 (was: 7/Dec/16) > Provide Apache Incubator Report March 2017 > -- > > Key: OMID-60 > URL: https://issues.apache.org/jira/browse/OMID-60 > Project: Apache Omid > Issue Type: Task > Reporter: Francisco Perez-Sorrosal > Assignee: Francisco Perez-Sorrosal > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OMID-60) Provide Apache Incubator Report March 2017
Francisco Perez-Sorrosal created OMID-60: Summary: Provide Apache Incubator Report March 2017 Key: OMID-60 URL: https://issues.apache.org/jira/browse/OMID-60 Project: Apache Omid Issue Type: Task Reporter: Francisco Perez-Sorrosal Assignee: Francisco Perez-Sorrosal -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OMID-59) Provide Apache Incubator Report Dec 2016
Francisco Perez-Sorrosal created OMID-59: Summary: Provide Apache Incubator Report Dec 2016 Key: OMID-59 URL: https://issues.apache.org/jira/browse/OMID-59 Project: Apache Omid Issue Type: Task Reporter: Francisco Perez-Sorrosal Assignee: Francisco Perez-Sorrosal -- This message was sent by Atlassian JIRA (v6.3.15#6346)
