Podling Report Reminder - March 2018

2018-03-04 Thread johndament
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, 21 March 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, March 07).

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.

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/March2018

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 #15: [OMID-77] Fix coprocessor for HBase 0.9x an...

2018-03-04 Thread asfgit
Github user asfgit closed the pull request at:

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


---


[GitHub] incubator-omid pull request #23: [OMID-89] Fix metrics in Persistence proces...

2018-03-04 Thread asfgit
Github user asfgit closed the pull request at:

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


---


[jira] [Commented] (OMID-77) Omid Coprocessor is not working in HBase version 0.98 after adding the shims

2018-03-04 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on OMID-77:


Github user asfgit closed the pull request at:

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


> 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
>Assignee: Francisco Perez-Sorrosal
>Priority: Major
>  Labels: 0.9x, coprocessor, hbase, shims
> Fix For: 0.9.0.0
>
>
> 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
(v7.6.3#76005)


[jira] [Commented] (OMID-89) Fix metrics in PersistenceProcesssorHandlers

2018-03-04 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on OMID-89:


Github user asfgit closed the pull request at:

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


> 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
>Priority: Minor
>  Labels: handler, metrics, persistence, processor
> 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)