Podling Report Reminder - June 2018
Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 20 June 2018, 10:30 am PDT. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, June 06). Please submit your report with sufficient time to allow the Incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Candidate names should not be made public before people are actually elected, so please do not include the names of potential committers or PPMC members in your report. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. * How does the podling rate their own maturity. This should be appended to the Incubator Wiki page at: https://wiki.apache.org/incubator/June2018 Note: This is manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC
[GitHub] incubator-omid pull request #36: [OMID-72] bug fix, accessed tables should b...
GitHub user ohadshacham opened a pull request: https://github.com/apache/incubator-omid/pull/36 [OMID-72] bug fix, accessed tables should be sent to transaction mana⦠â¦ger also for conflict free writes. This is because fences should also force conflict free transactions to abort. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ohadshacham/incubator-omid OMID-72-bug Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-omid/pull/36.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 #36 commit d96ff96e4fa264472ae684bdb1834e791a6d25ef Author: Ohad Shacham Date: 2018-06-03T13:41:45Z [OMID-72] bug fix, accessed tables should be sent to transaction manager also for conflict free writes. This is because fences should also force conflict free transactions to abort. ---
[GitHub] incubator-omid pull request #35: [OMID-100] James Taylor's patch to: https:/...
Github user ohadshacham closed the pull request at: https://github.com/apache/incubator-omid/pull/35 ---
[jira] [Commented] (OMID-72) Add fences to support secondary index in Phoenix
[ https://issues.apache.org/jira/browse/OMID-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16499422#comment-16499422 ] ASF GitHub Bot commented on OMID-72: GitHub user ohadshacham opened a pull request: https://github.com/apache/incubator-omid/pull/36 [OMID-72] bug fix, accessed tables should be sent to transaction mana… …ger also for conflict free writes. This is because fences should also force conflict free transactions to abort. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ohadshacham/incubator-omid OMID-72-bug Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-omid/pull/36.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 #36 commit d96ff96e4fa264472ae684bdb1834e791a6d25ef Author: Ohad Shacham Date: 2018-06-03T13:41:45Z [OMID-72] bug fix, accessed tables should be sent to transaction manager also for conflict free writes. This is because fences should also force conflict free transactions to abort. > Add fences to support secondary index in Phoenix > > > Key: OMID-72 > URL: https://issues.apache.org/jira/browse/OMID-72 > Project: Apache Omid > Issue Type: Sub-task >Reporter: Ohad Shacham >Assignee: Ohad Shacham >Priority: Major > > Add support for fences over a table. These fences guarantee that every > transaction started before the fence and writes to the table the fence was > created for will be aborted. > These fences are needed for creating a secondary index in Apache Phoenix. The > scenario was discussed in [TEPHRA-157] and [PHOENIX-2478]. Augmenting Omid > with this kind of transactions was also discussed in [OMID-56]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (OMID-72) Add fences to support secondary index in Phoenix
[ https://issues.apache.org/jira/browse/OMID-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham reopened OMID-72: -- Accessed tables should be sent to transaction manager also for conflict free writes. This is because fences should also force conflict free transactions to abort. > Add fences to support secondary index in Phoenix > > > Key: OMID-72 > URL: https://issues.apache.org/jira/browse/OMID-72 > Project: Apache Omid > Issue Type: Sub-task >Reporter: Ohad Shacham >Assignee: Ohad Shacham >Priority: Major > > Add support for fences over a table. These fences guarantee that every > transaction started before the fence and writes to the table the fence was > created for will be aborted. > These fences are needed for creating a secondary index in Apache Phoenix. The > scenario was discussed in [TEPHRA-157] and [PHOENIX-2478]. Augmenting Omid > with this kind of transactions was also discussed in [OMID-56]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OMID-99) Change TestNG version to 6.10
[ https://issues.apache.org/jira/browse/OMID-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham updated OMID-99: - Issue Type: Sub-task (was: Improvement) Parent: OMID-82 > Change TestNG version to 6.10 > - > > Key: OMID-99 > URL: https://issues.apache.org/jira/browse/OMID-99 > Project: Apache Omid > Issue Type: Sub-task >Reporter: Ohad Shacham >Assignee: Ohad Shacham >Priority: Major > > Change TestNG version to 6.10. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OMID-100) Throw non retriable exceptions from coprocessor and scanner implementors
[ https://issues.apache.org/jira/browse/OMID-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham updated OMID-100: -- Issue Type: Sub-task (was: Bug) Parent: OMID-82 > Throw non retriable exceptions from coprocessor and scanner implementors > > > Key: OMID-100 > URL: https://issues.apache.org/jira/browse/OMID-100 > Project: Apache Omid > Issue Type: Sub-task >Reporter: James Taylor >Assignee: Ohad Shacham >Priority: Major > Attachments: OMID-100.patch > > > HBase will retry 300+ times if an exception occurs on the server-side. To > prevent this, implementors need to wrap any exceptions that occur with a > DoNotRetryIOException > This should be done for OmidSnapshotFilter, OmidCompactor, and > OmidRegionScanner methods that implement HBase methods. For examples in > Phoenix, see: > * BaseScannerRegionObserver.postScannerOpen() > * NonAggregateRegionScannerFactory.getTopNScanner() anonymous > BaseRegionScanner implementation -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OMID-100) Throw non retriable exceptions from coprocessor and scanner implementors
[ https://issues.apache.org/jira/browse/OMID-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham reassigned OMID-100: - Assignee: Ohad Shacham > Throw non retriable exceptions from coprocessor and scanner implementors > > > Key: OMID-100 > URL: https://issues.apache.org/jira/browse/OMID-100 > Project: Apache Omid > Issue Type: Bug >Reporter: James Taylor >Assignee: Ohad Shacham >Priority: Major > Attachments: OMID-100.patch > > > HBase will retry 300+ times if an exception occurs on the server-side. To > prevent this, implementors need to wrap any exceptions that occur with a > DoNotRetryIOException > This should be done for OmidSnapshotFilter, OmidCompactor, and > OmidRegionScanner methods that implement HBase methods. For examples in > Phoenix, see: > * BaseScannerRegionObserver.postScannerOpen() > * NonAggregateRegionScannerFactory.getTopNScanner() anonymous > BaseRegionScanner implementation -- This message was sent by Atlassian JIRA (v7.6.3#76005)
