RE: [MENTORS] Sign off on Incubator Reports

[Gangumalla, Uma]

Hi Justin,

I have just signed off and added my comments. 

Thank you.

Regards,
Uma

-Original Message-
From: Justin Mclean  
Sent: Thursday, December 12, 2019 6:03 PM
To: general@incubator.apache.org
Subject: [MENTORS] Sign off on Incubator Reports

Hi,

The report has been submitted but we’re still missing some sign offs.

If you haevn't signed off the report please do so over at:
https://whimsy.apache.org/board/agenda/2019-12-18/Incubator

It would be good to see more sign off for:
BatchEE
Druid
Hivemall
Marvin-AI
MesaTEE
Samoa
Spot (still missing sign off but only has one mentor) ShardingSphere 
Streampipes Superset

Congratulation to Brpc, Crail, and  Apisix where all the mentors signed off the 
report.

Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

RE: Podling reports due Wednesday

[Gangumalla, Uma]

HI Justin and Felix,

 I have just put my sign off.
 Yes, you are right. I am not sure where its going. I only see 1 or 2 members 
in lists that to very rarely. 
 I feel it is still far away to come to graduation. I also don’t see any 
releases from long time.

This project's PPMC is not active.

BTW, thanks for volunteering. Let's if any Spot PPMC comments here about 
getting new Mentor to their project. :-)

Regards,
Uma  

-Original Message-
From: Felix Cheung [mailto:felixche...@apache.org] 
Sent: Monday, June 10, 2019 3:38 PM
To: general@incubator.apache.org
Subject: Re: Podling reports due Wednesday

I don’t mind taking on as a mentor for Spot but it seems the volume of 
interaction (commits, dev@) has gone down significantly in the last 6-9 months?


On Mon, Jun 10, 2019 at 3:21 PM Justin Mclean 
wrote:

> Hi,
>
> Currently we’re missing only one sign off and that is for:
> Spot
>
> Which, I forgot to mention in my last list.
>
> This is one podling that needs more mentors, is anyone available to help?
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

RE: [VOTE] Graduate Apache ServiceComb (incubating)

[Gangumalla, Uma]

+1 (binding)

Regards,
Uma

-Original Message-
From: Dave Fisher [mailto:dave2w...@comcast.net] 
Sent: Wednesday, September 26, 2018 11:31 AM
To: general@incubator.apache.org
Subject: Re: [VOTE] Graduate Apache ServiceComb (incubating)

+1 (binding)

> On Sep 26, 2018, at 12:06 AM, Roman Shaposhnik  wrote:
> 
> Hi!
> 
> given that we've got only positive feedback on the DISCUSS thread I'd 
> like to start an official VOTE thread now.
> 
> Please vote on the resolution pasted below to graduate Apache 
> ServiceComb from the incubator to the top level project.
> 
> [ ] +1 Graduate Apache ServiceComb from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache ServiceComb from the Incubator because...
> 
> This vote will be open for at least 72 hours.
> 
> Many thanks to our mentors and everyone else for their support, Roman 
> (on behalf of the Apache ServiceComb PPMC).
> 
> ## Resolution to create a TLP from graduating Incubator podling
> 
> X. Establish the Apache ServiceComb Project
> 
> WHEREAS, the Board of Directors deems it to be in the best interests 
> of the Foundation and consistent with the Foundation's purpose to 
> establish a Project Management Committee charged with the creation and 
> maintenance of open-source software, for distribution at no charge to 
> the public, related to a microservice framework that provides a set of 
> tools and components to make development and deployment of cloud 
> applications easier.
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee 
> (PMC), to be known as the "Apache ServiceComb Project", be and hereby 
> is established pursuant to Bylaws of the Foundation; and be it further
> 
> RESOLVED, that the Apache ServiceComb Project be and hereby is 
> responsible for the creation and maintenance of software related to a 
> microservice framework that provides a set of tools and components to 
> make development and deployment of cloud applications easier; and be 
> it further
> 
> RESOLVED, that the office of "Vice President, Apache ServiceComb" be 
> and hereby is created, the person holding such office to serve at the 
> direction of the Board of Directors as the chair of the Apache 
> ServiceComb Project, and to have primary responsibility for management 
> of the projects within the scope of responsibility of the Apache 
> ServiceComb Project; and be it further
> 
> RESOLVED, that the persons listed immediately below be and hereby are 
> appointed to serve as the initial members of the Apache ServiceComb
> Project:
> 
> * Aray Chenchu Sukesh 
> * Bao Liu 
> * Eric Lee 
> * Jean-Baptiste Onofré 
> * Jimin Wu 
> * Linzhinan 
> * Mohammad Asif Siddiqui 
> * Qi Zhang 
> * Roman Shaposhnik 
> * Timothy Chen 
> * Willem Ning Jiang 
> * Yang Bo 
> * Yihua Cui 
> * Yin Xiang 
> * Zheng Feng 
> * zhengyangyong 
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Willem Ning Jiang be 
> appointed to the office of Vice President, Apache ServiceComb, to 
> serve in accordance with and subject to the direction of the Board of 
> Directors and the Bylaws of the Foundation until death, resignation, 
> retirement, removal or disqualification, or until a successor is 
> appointed; and be it further
> 
> RESOLVED, that the Apache ServiceComb Project be and hereby is tasked 
> with the migration and rationalization of the Apache Incubator 
> ServiceComb podling; and be it further
> 
> RESOLVED, that all responsibilities pertaining to the Apache Incubator 
> ServiceComb podling encumbered upon the Apache Incubator PMC are 
> hereafter discharged.
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

RE: [VOTE] Release Apache Ratis (incubating) 0.2.0 (rc2)

[Gangumalla, Uma]

+1 (binding)

DISCLAIMER exists
LICENSE & NOTICE looks good.
Build is fine and passed
Incubating tag exists in name

Regards,
Uma

From: Elek, Marton [e...@apache.org]
Sent: Thursday, July 05, 2018 8:59 PM
To: general@incubator.apache.org
Subject: [VOTE] Release Apache Ratis (incubating) 0.2.0 (rc2)

Hi All,

The Apache Ratis community has voted on and approved a proposal to
release Apache Ratis 0.2.0-rc2.

We now kindly request that the Incubator PMC members review and vote on
this incubator release candidate.

The problems from the previous vote are fixed
(https://mail-archives.apache.org/mod_mbox/incubator-general/201805.mbox/%3C8BB8FABD-E3F7-4DB3-9417-DDB552675416%40classsoftware.com%3E)

• The name contains incubating (not incubator)
• Separated LICENSE and NOTICE for bin/source releases
• The missing BSD license (for Crc32 files) is added to the LICENSE

Apache Ratis is a highly customizable Raft protocol implementation in Java.

The vote thread is at:

https://mail-archives.apache.org/mod_mbox/ratis-dev/201806.mbox/%3C7ddfb4cd-4501-e15a-4bc2-d9a86b9d0d9d%40apache.org%3E

and the result is at:

https://mail-archives.apache.org/mod_mbox/ratis-dev/201807.mbox/%3Cde45e7c7-d2b0-935e-6595-870f87bf1a51%40apache.org%3E

This is the second incubator release and it includes more than 120
improvements and fixes since the previous 0.1.0-alpha release. This is
the first release
which includes a binary package with ready to use examples.

All distribution packages, including signatures, digests, etc. can be
found at:

https://dist.apache.org/repos/dist/dev/incubator/ratis/0.2.0/rc2

Staged artifacts can be found at:

https://repository.apache.org/content/repositories/orgapacheratis-1005

This release has been signed with PGP key 0EE79B28, corresponding to
e...@apache.org, which is included in the repository's KEYS file
(https://dist.apache.org/repos/dist/dev/incubator/ratis/KEYS).

This key can be found on keyservers, such as:

http://pgp.mit.edu/pks/lookup?op=get=0x0EE79B28

Or in the apache phonebook:

https://people.apache.org/keys/committer/elek.asc

The release candidate has been tagged in git with ratis-0.2.0-rc2 (4d14160)

https://github.com/apache/incubator-ratis/releases/tag/ratis-0.2.0-rc2

Please review and vote. The vote will be open for at least 72 hours or
until necessary number of votes are reached.

# Review/testing

  You can build the project from the source code package with

```
mvn clean install  assembly:single -DskipTests=true
```

The binary papckage can be smoketested with:

./examples/bin/start-all.sh
./examples/bin/client.sh assign --name a --value 2
./examples/bin/client.sh get --name a

Thank you very much,
Marton Elek


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Dr. Elephant Incubator Proposal

[Gangumalla, Uma]

I would +1 to have as a separate project instead of pushing under Hadoop. When 
a project can sustain by having potential to build community on its own and can 
run logically as independent module, I feel that’s good enough to start as 
separate project.  

I could not recall the discussions on removal of Vaidya package from Hadoop. If 
someone remembers, it would be great to know the reasons for removal of that 
package from Hadoop base. [ probably at the time of mavenization ? ]

Regards,
Uma

On 3/6/18, 3:17 PM, "md...@cloudera.com on behalf of Mike Drob" 
 wrote:

Why does Dr. Elephant make sense as a separate project instead of
contributing to Hadoop directly?

What is the relationship between Dr. Elephant and the (now seemingly
defunct) Hadoop Vaidya?

On Tue, Mar 6, 2018 at 5:08 PM, Carl Steinbach  wrote:

> Hi,
>
> I would like to propose Dr. Elephant as an Apache Incubator
> project. The proposal is available as a draft at
> https://wiki.apache.org/incubator/DrElephantProposal. I have also
> included the text of the proposal below.
>
> Any feedback from the community is much appreciated.
>
> Thanks.
>
> - Carl
>
>
> = ABSTRACT =
>
> Dr. Elephant is a performance monitoring and tuning service for Apache
> Hadoop and Apache Spark jobs and workflows. While the system is
> primarily aimed at developers, we have discovered that it is also
> popular with cluster operators who use it to monitor the health of
> workloads running on their clusters.
>
> = PROPOSAL =
>
> Dr. Elephant was open sourced by LinkedIn in 2016 and is currently
> hosted on GitHub. We believe that being a part of the Apache Software
> Foundation will improve the diversity and help form a strong community
> around the project.
>
> LinkedIn submits this proposal to donate the code base to the Apache
> Software Foundation. The code is already under Apache License 2.0.
> Both the source code and documentation are hosted on Github.
>
>  * Code: http://github.com/linkedin/dr-elephant
>  * Documentation: https://github.com/linkedin/dr-elephant/wiki
>
> = Background =
>
> Dr. Elephant is a service that helps users of Apache Hadoop and Apache
> Spark understand, analyze, and improve the performance of jobs and
> workflows running on their clusters. It automatically gathers metrics,
> performs analysis, and presents the results along with actionable
> advice. The goal of the project is to improve developer productivity
> and increase cluster efficiency by reducing the time and domain
> expertise required to diagnose and treat sick jobs. It analyzes Hadoop
> and Spark jobs using a set of configurable, extensible, rule-based
> heuristics that provide insights on job performance, and then uses
> this information to provide recommendations about how to tune jobs to
> make them run more efficiently.
>
> Dr. Elephant was open sourced in 2016 after two years of
> successful production use at Linkedin. In the time since many new
> features have been added including support for the Oozie and Airflow
> workflow schedulers, improved metrics, and enhancements to the Spark
> history fetcher and Spark heuristics. It is also important to note
> that many of these contributions came from developers outside of
> LinkedIn. We have also been happy to see that many people have been
> able to benefit from running Dr. Elephant including companies like
> Airbnb, Foursquare, Hulu, and Pinterest.
>
> = RATIONALE =
>
> Dr. Elephant's entry to the ASF will be beneficial to both the
> Dr. Elephant and Apache communities. Dr. Elephant has greatly
> benefited from its open source roots. Its community and adoption has
> grown greatly as a result. More importantly, the feedback from the
> community, whether through interactions at meetups or through the
> mailing list, have allowed for a rich exchange of ideas. We believe a
> partnership with the Apache Foundation is the logical next step. The
> Dr. Elephant community will greatly benefit from the established
> development and consensus processes that have worked well for other
> projects. The Apache process has served many other open source
> projects well and we believe that the Dr. Elephant community will
> greatly benefit from these practices as well.
>
> = CURRENT STATUS =
>
> Dr. Elephant is currently open sourced under the Apache License
> Version 2.0 and is available at github.com/linkedin/dr-elephant. All
> of the development is done using GitHub Pull Requests.
>
> We are aware of at least 10 organizations that are running
> Dr. Elephant, and many of these organizations have also contributed
 

Re: [VOTE] Accept ServiceComb into the Apache Incubator

[Gangumalla, Uma]

+1 (binding)

Regards,
Uma

On 11/13/17, 10:15 PM, "Willem Jiang"  wrote:

Hi All,

I would like to start a VOTE to bring the ServiceComb project in as an
Apache incubator podling.

The ASF voting rules are described:

https://www.apache.org/foundation/voting.html

A vote for accepting a new Apache Incubator podling is a majority vote for
which only Incubator PMC member votes are binding.

This vote will run for at least 72 hours. Please VOTE as follows
[] +1 Accept ServiceComb into the Apache Incubator
[] +0 Abstain.
[] -1 Do not accept ServiceComb into the Apache Incubator because ...

The proposal is listed below, but you can also access it on the wiki:

https://wiki.apache.org/incubator/ServiceCombProposal

Best regards,

Willem Jiang

= ServiceComb Proposal =

== Abstract ==

ServiceComb is a microservice framework that provides a set of tools and
components to make development and deployment of cloud applications easier.
It provides functionalities such as service contract enforcement, service
registration, service discovery, load balance, service reliability (latency
and fault tolerance, flow control and graceful degradation, handler chain
tracing), eventual data consistency and so forth.

== Proposal ==

The goal of this proposal is to bring the existing ServiceComb codebase and
existing developers into the Apache Software Foundation (ASF) in order to
build a vibrant, diverse and self-governed open source community around the
technology.
So far the major contributors to the project have been affiliated with
Huawei and Huawei is planning to continue market and sell the Cloud Service
Engine leveraging the ServiceComb framework.
ServiceComb is currently a registered trademark owned by Huawei, and Huawei
is happy to donate this trademark to Apache.

Huawei is submitting this proposal to donate the Service source code and
associated artifacts (documentation, web site content, wiki, etc.) to the
Apache Software Foundation Incubator under the Apache License, Version 2.0
and is asking Incubator PMC to establish an open source community. These
artifacts are currently available on GitHub at
https://github.com/ServiceComb/ and include:
 * Java Chassis: a multi-protocol (RPC & Restful) microservice framework
which adopts contract-first design
 * Service Center: a service registry that enforces service contract upon
service registration and discovery
 * Saga: a distributed coordinator to achieve eventual data consistency
based on the paper "Sagas" by Hector Garcia-Molina and Kenneth Salem
 * ServiceComb.github.io:  the website repo of ServiceComb.
 * The other projects will be moved to another place if ServiceComb is
accepted by Apache as an incubator project.

== Background ==

Microservices is a variant of the service-oriented architecture (SOA)
architectural style that structures an application as a collection of
loosely coupled services. ServiceComb is an open source microservice
framework initiated as part of Huawei CSE projects (Cloud Service Engine)
which was developed in 2015. It is a part of ServiceStage of Huawei Public
Cloud which is one-stop PaaS platform for enterprises and developers.
Besides ServiceStage, it’s  also used in the Huawei Core Network IOT
Platform and Huawei consumer cloud. The number of  companies using
ServiceComb to develop their enterprise applications, they are
chinasofti.com, isoftstone.com, pactera.com,zbj.com,movit-tech.com, and the
number is over 5 and counting.

== Rationale ==

ServiceComb has been developed as a total, open source solution for
developing cloud native applications. So far ServiceComb has existed as a
GitHub project with committers mostly working for Huawei. We feel that
moving it to a neutral organization like Apache, with its strong governance
model, is expected to help get more contributions from various
organizations and developers, who may be concerned by exclusive control of
ServiceComb by Huawei.

== Initial Goals ==

Our initial goals are to bring ServiceComb into the ASF, transition
internal engineering processes into the open, and foster a collaborative
development model according to the "Apache Way." Huawei and the current
contributors to ServiceComb plan to develop new functionality in an open,
community-driven way. To get there, the existing internal build, test and
release processes will be refactored to support open development.

 1. More specifically, our initial plan of moving ServiceComb to ASF is
focused on:
 2. open up the governance model in order to simplify and streamline
contributions from the community
 3. 

Re: [VOTE] Resolution to graduate Apache Impala to TLP

[Gangumalla, Uma]

+1 (binding)

Regards,
Uma

On Nov 8, 2017 8:28 PM, "Jim Apple"  wrote:

> The graduation of Impala to a TLP has been discussed[0] on dev@impala,
> voted on[1] on dev@impala, and discussed[2] on general@incubator. All
> threads were open 72 hours or more, and all seem to have quiesced.
>
> This is a call for a VOTE to graduate Impala to a TLP. The draft 
resolution
> is below. Please select from:
>
> [ ] +1: Graduate Impala to a TLP
> [ ] +-0: Neither graduate nor do not graduate Impala to a TLP
> [ ] -1: Do NOT graduate Impala to a TLP, because ...
>
> 
>
> [0]: <
> https://lists.apache.org/thread.html/2f5db4788aff9b0557354b9106c032
> 8a29c1f90c1a74a228163949d2@%3Cdev.impala.apache.org%3E
> >
>
> [1]: <
> https://lists.apache.org/thread.html/a5a7c6895b3e019347d6e4e4cf49d6
> 7d094d31b8f2c7b4d59200f3e4@%3Cdev.impala.apache.org%3E
> >
>
> [2]: <
> https://lists.apache.org/thread.html/6b8598408f76a472532923c5a7fc51
> 0470b21671677ba3486568c57e@%3Cgeneral.incubator.apache.org%3E
> >
>
> 
>
> Establish the Apache Impala Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to a high-performance distributed SQL engine.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Impala Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Impala Project be and hereby is responsible
> for the creation and maintenance of software related to a
> high-performance distributed SQL engine; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Impala" be and
> hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the Apache Impala
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Impala
> Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache Impala Project:
>
> * Alex Behm 
> * Bharath Vissapragada 
> * Brock Noland 
> * Carl Steinbach 
> * Casey Ching 
> * Daniel Hecht 
> * Dimitris Tsirogiannis 
> * Henry Robinson 
> * Ishaan Joshi 
> * Jim Apple 
> * John Russell 
> * Juan Yu 
> * Lars Volker 
> * Lenni Kuff 
> * Marcel Kornacker 
> * Martin Grund 
> * Matthew Jacobs 
> * Michael Brown 
> * Michael Ho 
> * Sailesh Mukil 
> * Skye Wanderman-Milne 
> * Taras Bobrovytsky 
> * Tim Armstrong 
> * Todd Lipcon 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jim Apple be appointed to
> the office of Vice President, Apache Impala, to serve in accordance with
> and subject to the direction of the Board of Directors and the Bylaws of
> the Foundation until death, resignation, retirement, removal or
> disqualification, or until a successor is appointed; and be it further
>
> RESOLVED, that the initial Apache Impala PMC be and hereby is tasked
> with the creation of a set of bylaws intended to encourage open
> development and increased participation in the Apache Impala Project;
> and be it further
>
> RESOLVED, that the Apache Impala Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator Impala
> podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Impala podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
>

Re: [VOTE] Release of Apache Mnemonic-0.10.0-incubating [rc1]

[Gangumalla, Uma]

+1 (binding)

Regards,
Uma

On 11/14/17, 1:41 PM, "Gang(Gary) Wang"  wrote:

+1 Thanks!

Best,
Gary


On Tue, Nov 14, 2017 at 9:27 AM, solrac...@apache.org 
wrote:

> +1
>
> 2017-11-14 11:19 GMT-06:00 Johnu George :
>
> > Hi everyone,
> >Can you please vote for this new release?
> >
> > Thanks,
> > Johnu
> >
> > On Thu, Nov 9, 2017 at 11:47 AM, Johnu George  wrote:
> > > Hello incubator PMCs,
> > >
> > > The Apache Mnemonic community PPMCs and developers have voted and
> > > approved the proposal to release Apache Mnemonic 0.10.0 (incubating).
> > > Apache Mnemonic is an advanced hybrid memory storage oriented library,
> > > it's proposed a non-volatile/durable Java object model and durable
> > > computing model that bring several advantages to significantly improve
> > > the performance of massive real-time data processing/analytics.
> > > Developers can use this library to design their cache-less and SerDe
> > > less high performance applications.
> > >
> > >
> > > [VOTE] thread:
> > >
> > > http://mail-archives.apache.org/mod_mbox/incubator-
> > mnemonic-dev/201711.mbox/%3CCALuGr6auOV9BqQ5FNmQ_V%
> > 2B5qbzrNfiaH6gYyxk-H%2BLBhmo%3DwuA%40mail.gmail.com%3E
> > >
> > > http://mail-archives.apache.org/mod_mbox/incubator-
> > mnemonic-dev/201711.mbox/%3CCANLc_9%2BeJ%2BZURAZT%2BTfr-
> > U3AgV5q0h5R7o%3DdA_rd6nf0nd%3DNHA%40mail.gmail.com%3E
> > >
> > > [VOTE RESULT] thread:
> > >
> > > http://mail-archives.apache.org/mod_mbox/incubator-
> > mnemonic-dev/201711.mbox/%3CCABtC0%2Bj2eV1fAMSJU4PEVOsoDUfPBUdQvb
> > nXd5HTN4oSpjauKg%40mail.gmail.com%3E
> > >
> > > We now kindly request the Incubator PMC members review and vote on
> > > this incubator release.
> > >
> > > The Apache Mnemonic-0.10.0-incubating release candidate is now
> > > available with the following artifacts for a project vote:
> > >
> > > The source tarball, including signatures, digests, etc. can be found
> at:
> > > https://dist.apache.org/repos/dist/dev/incubator/mnemonic/0.
> > 10.0-incubating-rc1/src/
> > >
> > > The tag to be voted upon is v0.10.0-incubating:
> > > https://git-wip-us.apache.org/repos/asf?p=incubator-
> > mnemonic.git;a=shortlog;h=refs/tags/v0.10.0-incubating
> > >
> > > The release hash is 0e6cf3534b2f1a6407021e0d99073d794690f71b:
> > > https://git-wip-us.apache.org/repos/asf?p=incubator-
> > mnemonic.git;a=commit;h=0e6cf3534b2f1a6407021e0d99073d794690f71b
> > >
> > > Release artifacts are signed with the following key:
> > > https://dist.apache.org/repos/dist/dev/incubator/mnemonic/KEYS
> > >
> > > KEYS file available:
> > > https://dist.apache.org/repos/dist/dev/incubator/mnemonic/KEYS
> > >
> > > For information about the contents of this release, see:
> > > https://dist.apache.org/repos/dist/dev/incubator/mnemonic/0.
> > 10.0-incubating-rc1/CHANGES.txt
> > >
> > > The vote will be open for ~72 hours.
> > > Please download the release candidate and evaluate the necessary items
> > > including checking hashes, signatures, build from source, and test.
> The
> > > please vote:
> > >
> > > [ ] +1 Release this package as apache-mnemonic-0.10.0-incubating
> > > [ ] +0 no opinion
> > > [ ] -1 Do not release this package because...
> > >
> > > Thanks,
> > > Johnu on behalf of the Apache Mnemonic (incubating) community
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [VOTE] Graduate Apache Mnemonic project from Incubator

[Gangumalla, Uma]

+1 (binding)

Regards,
Uma

On 9/19/17, 10:16 AM, "Gang(Gary) Wang"  wrote:

>Hello IPMC and everyone,
>
>The Mnemonic community has voted on its Dev list to graduate, The vote
>passed with
>14 +1s (including  +9s from the PPMC) and 0 -1s.
>
>Here is the vote result thread in the Dev list:
>https://lists.apache.org/thread.html/bbc187108b73d57fddec0d6a6c294527b626c
>7c439a7cdab991ea84e@%3Cdev.mnemonic.apache.org%3E
>
>and the vote thread:
>https://lists.apache.org/thread.html/a49e82d507bb00839413e90b05cb8b9448ea2
>42aeb021622f5deb323@%3Cdev.mnemonic.apache.org%3E
>
>With the discussion having settled down, I would now like to call for
>a recommendation VOTE to present the ASF board with the following
>resolution
>to graduate from incubation and establish Apache Mnemonic
>as a top-level project (TLP).
>https://lists.apache.org/thread.html/94664579041db58bfe2893af6e9d549576526
>53b278d4007e914c672@%3Cgeneral.incubator.apache.org%3E
>
>Apache Mnemonic entered incubation in March 2016. Since then there have
>been nine releases and four committers and two PMC candidate members
>have been added to the project. For each release, source artifacts
>have been made available. Based on the completed maturity evaluation,
>we believe that the project is ready to graduate from the incubator.
>More checklist info about graduation, please refer to
>https://cwiki.apache.org/confluence/display/MNEMONIC/Maturity+Evaluation
>
>Please vote on whether to graduate Mnemonic from incubator and
>recommend the following graduation resolution to the ASF Board.
>
>[ ] +1 Graduate Apache Mnemonic from the Incubator
>[ ] +0 Don't care
>[ ] -1 Don't graduate Apache Mnemonic from the Incubator because...
>
>This VOTE will be open for at least 72 hours.
>Thanks to all Mentors and Apache Mnemonic Project members
>for their support and contributions again.
>
>The full text of the resolution is below.
>If approved by the Apache Incubator PMC members,
>the proposed resolution will be submitted to
>the Board of Directors for their consideration.
>--
>Establish the Apache Mnemonic Project
>
>WHEREAS, the Board of Directors deems it to be in the best interests of
>the Foundation and consistent with the Foundation's purpose to establish
>a Project Management Committee charged with the creation and maintenance
>of open-source software, for distribution at no charge to the public,
>related to a transparent nonvolatile hybrid memory oriented library for
>Big data, High-performance computing, and Analytics.
>
>NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>(PMC), to be known as the "Apache Mnemonic Project", be and hereby is
>established pursuant to Bylaws of the Foundation, and be it further
>
>RESOLVED, that the Apache Mnemonic Project be and hereby is responsible
>for the creation and maintenance of software related to a transparent
>nonvolatile hybrid memory oriented library for Big data,
>High-performance computing and Analytics; and be it further
>
>RESOLVED, that the office of "Vice President, Apache Mnemonic" be and
>hereby is created, the person holding such office to serve at the
>direction of the Board of Directors as the chair of the Apache Mnemonic
>Project, and to have primary responsibility for management of the
>projects within the scope of responsibility of the Apache Mnemonic
>Project, and be it further
>
>RESOLVED, that the persons listed immediately below be and hereby are
>appointed to serve as the initial members of the Apache Mnemonic
>Project:
>
> * Andrew Kyle Purtell  
> * Debojyoti Dutta  
> * Gang Wang
> * Hao Cheng
> * James R. Taylor  
> * Johnu George 
> * Kai Zheng
> * Patrick D. Hunt  
> * Rakesh Radhakrishnan 
> * Uma Maheswara Rao G  
> * Yanping Wang 
>
>NOW, THEREFORE, BE IT FURTHER RESOLVED, that Gang Wang be appointed to
>the office of Vice President, Apache Mnemonic, to serve in accordance
>with and subject to the direction of the Board of Directors and the
>Bylaws of the Foundation until death, resignation, retirement, removal
>or disqualification, or until a successor is appointed, and be it
>further
>
>RESOLVED, that the initial Apache Mnemonic PMC be and hereby is tasked
>with the creation of a set of bylaws intended to encourage open
>development and increased participation in the Apache Mnemonic Project;
>and be it further
>
>RESOLVED, that the Apache Mnemonic Project be and hereby is tasked with
>the migration and rationalization of the Apache Incubator Mnemonic
>podling; and be it further
>
>RESOLVED, that all responsibilities pertaining to the Apache Incubator
>Mnemonic podling encumbered upon the Apache Incubator PMC are 

Re: [DISCUSS] The draft graduation resolution

[Gangumalla, Uma]

Content looks good to me. +1

Regards,
Uma

On 9/12/17, 11:15 AM, "Gang(Gary) Wang"  wrote:

>Hi everyone
>
>Please give your feedback on this draft graduation resolution below,
>that is proposed by our community and hope we can reach a
>consensus on this resolution here before we start recommendation
>vote.
>
>Thanks!
>
>
>
>Establish the Apache Mnemonic Project
>
>WHEREAS, the Board of Directors deems it to be in the best interests of
>the Foundation and consistent with the Foundation's purpose to establish
>a Project Management Committee charged with the creation and maintenance
>of open-source software, for distribution at no charge to the public,
>related to a transparent nonvolatile hybrid memory oriented library for
>Big data, High-performance computing, and Analytics.
>
>NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>(PMC), to be known as the "Apache Mnemonic Project", be and hereby is
>established pursuant to Bylaws of the Foundation, and be it further
>
>RESOLVED, that the Apache Mnemonic Project be and hereby is responsible
>for the creation and maintenance of software related to a transparent
>nonvolatile hybrid memory oriented library for Big data,
>High-performance computing and Analytics; and be it further
>
>RESOLVED, that the office of "Vice President, Apache Mnemonic" be and
>hereby is created, the person holding such office to serve at the
>direction of the Board of Directors as the chair of the Apache Mnemonic
>Project, and to have primary responsibility for management of the
>projects within the scope of responsibility of the Apache Mnemonic
>Project, and be it further
>
>RESOLVED, that the persons listed immediately below be and hereby are
>appointed to serve as the initial members of the Apache Mnemonic
>Project:
>
> * Andrew Kyle Purtell  
> * Debo 
> * Gang Wang
> * Hao Cheng
> * James R. Taylor  
> * Johnu George 
> * Kai Zheng
> * Patrick D. Hunt  
> * Rakesh Radhakrishnan 
> * Uma Maheswara Rao G  
> * Yanping Wang 
>
>NOW, THEREFORE, BE IT FURTHER RESOLVED, that Gang Wang be appointed to
>the office of Vice President, Apache Mnemonic, to serve in accordance
>with and subject to the direction of the Board of Directors and the
>Bylaws of the Foundation until death, resignation, retirement, removal
>or disqualification, or until a successor is appointed, and be it
>further
>
>RESOLVED, that the initial Apache Mnemonic PMC be and hereby is tasked
>with the creation of a set of bylaws intended to encourage open
>development and increased participation in the Apache Mnemonic Project;
>and be it further
>
>RESOLVED, that the Apache Mnemonic Project be and hereby is tasked with
>the migration and rationalization of the Apache Incubator Mnemonic
>podling; and be it further
>
>RESOLVED, that all responsibilities pertaining to the Apache Incubator
>Mnemonic podling encumbered upon the Apache Incubator PMC are hereafter
>discharged.


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release of Apache Mnemonic-0.9.0-incubating [rc2]

[Gangumalla, Uma]

Forwarding my +1 from dev list.


+1 (binding)

Regards,
Uma

On 9/7/17, 3:14 PM, "Johnu George"  wrote:

>Hello incubator PMCs,
>
>The Apache Mnemonic community PPMCs and developers have voted and approved
>the proposal to release Apache Mnemonic 0.9.0 (incubating).
>Apache Mnemonic is an advanced hybrid memory storage oriented library,
>it's
>proposed a non-volatile/durable Java object model and
>durable computing model that bring several advantages to significantly
>improve the performance of massive real-time data processing/analytics.
>developers are able to use this library to design their cache-less and
>SerDe-less high performance applications.
>
>[VOTE] thread:
>
>http://mail-archives.apache.org/mod_mbox/incubator-mnemonic-dev/201709.mbo
>x/
>
>
>http://mail-archives.apache.org/mod_mbox/incubator-mnemonic-dev/201709.mbo
>x/
>
>
>http://mail-archives.apache.org/mod_mbox/incubator-mnemonic-dev/201709.mbo
>x/

Re: [RESULT][VOTE] Graduate Apache CarbonData Project from the Incubator

[Gangumalla, Uma]

My +1 (binding) [carrying my vote from carbondata private list]

Sorry for my late vote on this


Regards,
Uma

On 3/21/17, 10:18 PM, "Jean-Baptiste Onofré"  wrote:

>Hi,
>
>this vote passed with the following result:
>
>+1 (binding): Niclas Hedhman, Julian Hyde, Henry Saputra, John D. Ament
>+1 (non binding): Pierre Smits, Timothy Chen
>
>Thanks all for the vote.
>
>I will prepare the resolution submission for the next board meeting.
>
>Regards
>JB
>
>On 03/15/2017 01:39 PM, Jean-Baptiste Onofré wrote:
>> Hi IPMC,
>>
>> Following the previous discussion, please vote on the draft resolution
>>proposed
>> by the Apache CarbonData PPMC below, which establishes Apache
>>CarbonData as a
>> new top-level project at the Apache Software Foundation, as follows:
>>
>> [ ] +1, Graduate Apache CarbonData from the Incubator.
>> [ ] +0, Don't care.
>> [ ] -1, Don't graduate Apache CarbonData from the Incubator (provide
>>details)
>>
>> The full text of the resolution is bellow.
>>
>> If approved by the Apache Incubator PMC members, the proposed
>>resolution will be
>> submitted to the Board of Directors for their consideration.
>>
>> Thanks !
>>
>> Regards
>> JB
>>
>> The full-text of the draft resolution proposed by the Apache CarbonData
>>PPMC:
>>
>>  X. Establish the Apache CarbonData Project
>>
>>WHEREAS, the Board of Directors deems it to be in the best
>>interests of the Foundation and consistent with the
>>Foundation's purpose to establish a Project Management
>>Committee charged with the creation and maintenance of
>>open-source software, for distribution at no charge to
>>the public, related to an indexed columnar data format
>>for fast analytics on big data platform.
>>
>>NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>>Committee (PMC), to be known as the "Apache CarbonData Project",
>>be and hereby is established pursuant to Bylaws of the
>>Foundation; and be it further
>>
>>RESOLVED, that the Apache CarbonData Project be and hereby is
>>responsible for the creation and maintenance of software
>>related to a unified programming model for both batch and
>>streaming data processing, enabling efficient execution across
>>diverse distributed execution engines and providing extensibility
>>points for connecting to different technologies and user
>>communities; and be it further
>>
>>RESOLVED, that the office of "Vice President, Apache CarbonData"be
>>and hereby is created, the person holding such office to
>>serve at the direction of the Board of Directors as the chair
>>of the Apache CarbonData Project, and to have primary responsibility
>>for management of the projects within the scope of
>>responsibility of the Apache CarbonData Project; and be it further
>>
>>RESOLVED, that the persons listed immediately below be and
>>hereby are appointed to serve as the initial members of the
>>Apache CarbonData Project:
>>
>> * Liang Chen 
>> * Jean-Baptiste Onofré 
>> * Henry Saputra 
>> * Uma Maheswara Rao G 
>> * Jenny MA 
>> * Jacky Li 
>> * Vimal Das Kammath 
>> * Jarray Qiu 
>>
>>NOW, THEREFORE, BE IT FURTHER RESOLVED, that Liang Chen be
>>appointed to the office of Vice President, Apache CarbonData, to
>>serve in accordance with and subject to the direction of the
>>Board of Directors and the Bylaws of the Foundation until
>>death, resignation, retirement, removal or disqualification,
>>or until a successor is appointed; and be it further
>>
>>RESOLVED, that the initial Apache CarbonData PMC be and hereby is
>>tasked with the creation of a set of bylaws intended to
>>encourage open development and increased participation in the
>>Apache CarbonData Project; and be it further
>>
>>RESOLVED, that the Apache CarbonData Project be and hereby
>>is tasked with the migration and rationalization of the Apache
>>Incubator CarbonData podling; and be it further
>>
>>RESOLVED, that all responsibilities pertaining to the Apache
>>Incubator CarbonData podling encumbered upon the Apache Incubator
>>Project are hereafter discharged.
>>
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>
>-- 
>Jean-Baptiste Onofré
>jbono...@apache.org
>http://blog.nanthrax.net
>Talend - http://www.talend.com
>
>-
>To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>For additional commands, e-mail: general-h...@incubator.apache.org
>


-

Re: [VOTE] Apache CarbonData 1.0.0-incubating release (RC2)

[Gangumalla, Uma]

+1 (binding)

Regards,
Uma

On 1/24/17, 4:59 AM, "Jacky Li" <13561...@qq.com> wrote:

>Hi Incubator PMC, 
>
>Please vote on releasing the following candidate as Apache
>CarbonData(incubating) version 1.0.0.
>
>PPMC has passed the vote,  here's the PPMC vote thread for 1.0.0 release:
>http://apache-carbondata-mailing-list-archive.1130556.n5.nabble.com/VOTE-A
>pache-CarbonData-1-0-0-incubating-release-RC2-td7016.html
>
>The source distribution, with signatures is there:
>https://dist.apache.org/repos/dist/dev/incubator/carbondata/1.0.0-incubati
>ng-rc2/
>
>Build guide(need install Apache Thrift 0.9.3, use command: mvn clean
>-DskipTests -Pbuild-with-format -Pspark-1.6 install), please find the
>detail:
>https://github.com/apache/incubator-carbondata/tree/master/build
>
>The Git Tag is :  
>https://git-wip-us.apache.org/repos/asf?p=incubator-carbondata.git;a=commi
>t;h=39efa332be094772daed05976b29241593da309f
>
>The artifacts have been signed with this key:
>https://dist.apache.org/repos/dist/dev/incubator/carbondata/KEYS
>
>Please vote to approve this release:
>
>[ ] +1 Approve the release
>[ ] -1 Don't approve the release (please provide specific comments)
>
>This vote will be open for at least 72 hours.
>
>Regards,
>Jacky Li
>
>
>
>
>--
>View this message in context:
>http://apache-incubator-general.996316.n3.nabble.com/VOTE-Apache-CarbonDat
>a-1-0-0-incubating-release-RC2-tp53517.html
>Sent from the Apache Incubator - General mailing list archive at
>Nabble.com.
>
>-
>To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>For additional commands, e-mail: general-h...@incubator.apache.org
>


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Bring Griffin to Apache Incubator

[Gangumalla, Uma]

+1 (binding)

Regards,
Uma

On 11/30/16, 10:40 PM, "Henry Saputra"  wrote:

>Hi All,
>
>As the champion for Griffin, I would like to start VOTE to bring  the
>project as Apache incubator podling.
>
>Here is the direct quote from the abstract:
>
>"
>Griffin is a Data Quality Service platform built on Apache Hadoop and
>Apache Spark. It provides a framework process for defining data
>quality model, executing data quality measurement, automating data
>profiling and validation, as well as a unified data quality
>visualization across multiple data systems. It tries to address the
>data quality challenges in big data and streaming context.
>"
>
>Please cast your vote:
>
>[ ] +1, bring Griffin into Incubator
>[ ] +0, I don't care either way,
>[ ] -1, do not bring Griffin into Incubator, because...
>
>This vote will be open at least for 72 hours and only votes from the
>Incubator PMC are binding.
>
>The VOTE will end 12/5 9am PST to pass through weekend.
>
>
>Here is the link to the proposal:
>
>https://wiki.apache.org/incubator/GriffinProposal
>
>I have copied the proposal below for easy access
>
>
>Thanks,
>
>- Henry
>
>
>
>Griffin Proposal
>
>Abstract
>
>Griffin is a Data Quality Service platform built on Apache Hadoop and
>Apache Spark. It provides a framework process for defining data
>quality model, executing data quality measurement, automating data
>profiling and validation, as well as a unified data quality
>visualization across multiple data systems. It tries to address the
>data quality challenges in big data and streaming context.
>
>Proposal
>
>Griffin is a open source Data Quality solution for distributed data
>systems at any scale in both streaming or batch data context. When
>people use open source products (e.g. Apache Hadoop, Apache Spark,
>Apache Kafka, Apache Storm), they always need a data quality service
>to build his/her confidence on data quality processed by those
>platforms. Griffin creates a unified process to define and construct
>data quality measurement pipeline across multiple data systems to
>provide:
>
>Automatic quality validation of the data
>Data profiling and anomaly detection
>Data quality lineage from upstream to downstream data systems.
>Data quality health monitoring visualization
>Shared infrastructure resource management
>
>Overview of Griffin
>
>Griffin has been deployed in production at eBay serving major data
>systems, it takes a platform approach to provide generic features to
>solve common data quality validation pain points. Firstly, user can
>register the data asset which user wants to do data quality check. The
>data asset can be batch data in RDBMS (e.g.Teradata), Apache Hadoop
>system or near real-time streaming data from Apache Kafka, Apache
>Storm and other real time data platforms. Secondly, user can create
>data quality model to define the data quality rule and metadata.
>Thirdly, the model or rule will be executed automatically (by the
>model engine) to get the sample data quality validation results in a
>few seconds for streaming data. Finally, user can analyze the data
>quality results through built-in visualization tool to take actions.
>
>Griffin includes:
>
>Data Quality Model Engine
>
>Griffin is model driven solution, user can choose various data quality
>dimension to execute his/her data quality validation based on selected
>target data-set or source data-set ( as the golden reference data). It
>has a corresponding library supporting it in back-end for the
>following measurement:
>
>Accuracy - Does data reflect the real-world objects or a verifiable source
>Completeness - Is all necessary data present
>Validity - Are all data values within the data domains specified by the
>business
>Timeliness - Is the data available at the time needed
>Anomaly detection - Pre-built algorithm functions for the
>identification of items, events or observations which do not conform
>to an expected pattern or other items in a dataset
>Data Profiling - Apply statistical analysis and assessment of data
>values within a dataset for consistency, uniqueness and logic.
>
>Data Collection Layer
>
>We support two kinds of data sources, batch data and real time data.
>
>For batch mode, we can collect data source from Apache Hadoop based
>platform by various data connectors.
>
>For real time mode, we can connect with messaging system like Kafka to
>near real time analysis.
>
>Data Process and Storage Layer
>
>For batch analysis, our data quality model will compute data quality
>metrics in our spark cluster based on data source in Apache Hadoop.
>
>For near real time analysis, we consume data from messaging system,
>then our data quality model will compute our real time data quality
>metrics in our spark cluster. for data storage, we use time series
>database in our back end to fulfill front end request.
>
>Griffin Service
>
>We have RESTful web services to accomplish all the functionalities of
>Griffin, such as register data asset, create data quality 

Re: [VOTE] Apache CarbonData 0.2.0-incubating release

[Gangumalla, Uma]

Disclaimer exist
LICENSE.txt exist
Signature file fine
Contains incubating

I think Readme.md file can have section about Prerequisites and point to
https://cwiki.apache.org/confluence/display/CARBONDATA/Building+CarbonData+
And+IDE+Configuration

>From Wiki
==
If PPMC/IPMC need to verify release before formally publishing, please use
the following command to build.
If user wants to change format module's thrift files, he can use the
following command to build the carbondata-format.
(Note: in the above mentioned build steps carbondata-format is not built
but downloaded from snapshot repository, it will facilitate general users
who don't need to install thrift.)
$ mvn clean -DskipTests -Pbuild-with-format install
==


I think above note can be added at top in building section. Also its not
only for PPMC and IPMC, This note should be for any user who is trying to
verify release


Other than this 

+1

Regards,
Uma

On 11/13/16, 7:33 AM, "Liang Chen"  wrote:

>Hi all,
>
>PPMC vote for the release Apache CarbonData 0.2.0-incubating has passed.
>Now, we kindly submit this release to the IPMC.
>
>Here's the PPMC vote thread for 0.2.0 release:
>http://apache-carbondata-mailing-list-archive.1130556.n5.nabble.com/RESULT
>-VOTE-Apache-CarbonData-0-2-0-incubating-release-td2823.html
>
>The source distribution, with signatures is there:
>https://dist.apache.org/repos/dist/dev/incubator/carbondata/0.2.0-incubati
>ng/
>
>The git tag is:
>https://git-wip-us.apache.org/repos/asf?p=incubator-carbondata.git;a=commi
>t;h=848d3c03b63d2eba4160b25e60c097fc38aeb1e3
>
>Staging Repository:
>https://repository.apache.org/content/repositories/orgapachecarbondata-100
>6
>
>The artifacts have been signed with this key:
>https://dist.apache.org/repos/dist/dev/incubator/carbondata/KEYS
>
>The Release Notes is:
>https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320220;
>version=12337896
>
>Please vote to approve this release:
>
>[ ] +1 Approve the release
>[ ] -1 Don't approve the release (please provide specific comments)
>
>This vote will be open for at least 72 hours.
>
>Thanks !
>Regards


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache CarbonData 0.1.1-incubating release

[Gangumalla, Uma]

+1 (binding)
Thanks for making the release.

Build is fine
DISCLAIMER exists.
It has Œincubating¹ tag
NOTICE & LICENCE files exists

Regards,
Uma

On 10/5/16, 3:06 AM, "Liang Big data"  wrote:

>Hi all,
>
>PPMC vote for the release Apache CarbonData 0.1.1-incubating has passed.
>
>Now, we kindly submit this release to the IPMC.
>
>Here's the PPMC vote thread for 0.1.1 release:
>https://lists.apache.org/thread.html/5b70a2eea0c0249d7947df4e3a789b90867f3
>c0f4822f1f868ee926d@%3Cdev.carbondata.apache.org%3E
>
>The source distribution, with signatures is there:
>https://dist.apache.org/repos/dist/dev/incubator/carbondata/0.1.1-incubati
>ng/
>
>The git tag is:
>https://git-wip-us.apache.org/repos/asf?p=incubator-carbondata.git;a=commi
>t;h=7fa00c3618b7f92bf00c9836cd265e9d1343bcfb
>
>The artifacts have been signed with this key:
>https://dist.apache.org/repos/dist/dev/incubator/carbondata/KEYS
>
>Please vote to approve this release:
>
>[ ] +1 Approve the release
>[ ] -1 Don't approve the release (please provide specific comments)
>
>This vote will be open for at least 72 hours.
>
>Thanks !
>Regards


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [RESULT] [VOTE] Accept Spot into the Apache Incubator

[Gangumalla, Uma]

Thanks Doug. No problem at all. :-)

Regards,
Uma

On 9/24/16, 10:15 AM, "Doug Cutting" <cutt...@gmail.com> wrote:

>On Sat, Sep 24, 2016 at 12:03 AM, Gangumalla, Uma
><uma.ganguma...@intel.com> wrote:
>> BTW, there were 5 binding votes.
>
>Oops.  Sorry for the miscount!  I mistakenly searched for "Gangumalla"
>rather than "umamahesh" in
>http://people.apache.org/committers-by-project.html#incubator-pmc, but
>I should have known better regardless.  My sincere apologies.
>
>Doug
>
>-
>To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>For additional commands, e-mail: general-h...@incubator.apache.org
>


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [RESULT] [VOTE] Accept Spot into the Apache Incubator

[Gangumalla, Uma]

Congrats Spot team.

BTW, there were 5 binding votes.

Regards,
Uma

On 9/23/16, 3:33 PM, "Doug Cutting" <cutt...@gmail.com> wrote:

>The vote passes, with 7 +1 votes (4 binding) and no -1 votes.
>
>+1 Jarek Jarcec Cecho (binding)
>+1 Gangumalla, Uma
>+1 Todd Lipcon (binding)
>+1 Tom White (binding)
>+1 Zheng, Kai
>+1 Stack (binding)
>+1 Debo Dutta
>
>Thanks all for voting.
>
>Spot has been accepted for Incubation at Apache.  Welcome Spot!
>
>Doug
>
>-
>To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>For additional commands, e-mail: general-h...@incubator.apache.org
>


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept Spot into the Apache Incubator

[Gangumalla, Uma]

+1(binding)
 Accept Spot into the Apache Incubator


Regards,
Uma

On 9/20/16, 11:15 AM, "Doug Cutting"  wrote:

>Following the discussion thread, I would like to call a vote on
>accepting Spot into the Apache Incubator.
>
>[] +1 Accept Spot into the Apache Incubator
>[] +0 Abstain.
>[] -1 Do not accept Spot into the Apache Incubator because ...
>
>This vote will run for the usual 72 hours.
>
>The proposal is attached, but you can also access it on the wiki:
>   https://wiki.apache.org/incubator/SpotProposal
>
>Thanks,
>
>Doug
>
>= SpotProposal =
>
>== Abstract ==
>
>Spot is an open source platform for network telemetry (packet, flow,
>and proxy at the moment) built on an open data model and Apache
>Hadoop.
>
>== Proposal ==
>
>Spot (formerly Open Network Insight, or ONI) is an open source
>solution for network telemetry (packet, flow, and proxy at the moment)
>built on an open data model and Apache Hadoop. It provides ingestion
>and transformation of binary data, scalable machine learning, and
>interactive visualization for identifying threats in network flows and
>DNS packets.
>
>Spot has a pluggable architecture that can accommodate multiple open
>data models. Although cybersecurity/network-intrusion analysis is the
>initial use case for Spot, we are actively encouraging the
>contribution of new models that will enable other adjacent
>applications, such as fraud detection or IT-operational analytics such
>as performance and health monitoring. Because these models are open,
>users maintain control of their own data.
>
>More information on Spot can be found at the existing project website
>at http://open-network-insight.org/.
>
>== Background ==
>
>It almost goes without saying that cybersecurity is an acute and
>paramount concern globally, for organizations of all types and
>sizes. Fortunately, thanks to the availability of massively scalable
>(in the PBs) data infrastructure, security professionals can now make
>authentically data-driven decisions about how they protect their
>assets. For example, records of network traffic, captured as network
>flows, are often stored and analyzed for use in network management,
>and this same information can provide valuable insights into network
>vulnerabilities.
>
>Cybersecurity is just one example, however: There are other examples
>of adjacent use cases, such as user fraud detection or IT-operations
>analytics, that would benefit from the combination of Spot
>functionality and PB-scale data sets for analysis.
>
>== Rationale ==
>
>Although cybersecurity is its initial use case/data model, Spot is
>intended to more generally tackle the dual challenges of facilitating
>the development of big data-driven analytic solutions, while helping
>vendors avoid having to create one/off infrastructure for each use
>case. Spot will eliminate issues related to vendor data models that
>create silos between solutions, and that make it difficult for users
>to consume these innovations from multiple vendors. In summary, Spot
>will accelerate the development of new massively scalable analytic
>applications that give users more flexibility, and more choices.
>
>As an initial effort, we are now seeking to build an ecosystem of
>developers, data scientists, and security professionals to make Spot
>the open, community-driven, cybersecurity platform standard it needs
>to become. By bringing Spot to Apache, we hope to galvanize these
>groups to cooperate in this highly matrixed effort, and to build a
>global, and diverse, Spot community.
>
>== Initial Goals ==
>
>Move the existing codebase, website, documentation, and mailing lists
>to Apache-hosted infrastructure Work with the infrastructure team to
>implement and approve our build and testing workflows in the context
>of the ASF Incremental development and releases per Apache guidelines
>
>== Current Status ==
>
>=== Releases ===
>
>Spot has undergone one public release (1.0). This initial release was
>not performed in the typical ASF fashion; we will adopt the ASF source
>release process upon joining the incubator.
>
>=== Source ===
>
>Spot¹s source, including core platform and associated submodules, is
>currently hosted in several GitHub repositories under the indicated
>licenses:
>
> * Core (Apache License 2.0)
> * Oni-ingest (Apache License 2.0)
> * Oni-ml (Apache License 2.0
> * Oni-oa (BSD & MIT)
> * Oni-setup (Apache License 2.0)
> * Oni-nfdump (BSD)
> * Oni-lda-c (GNU General Public License version 2)
>
>The repositories will be transitioned to Apache¹s git hosting during
>incubation.  Issues related to GPL code will be resolved during
>incubation.
>
>
>=== Issue Tracking ===
>
>Spot¹s bug and feature tracking is hosted on Github at:
>
> * https://github.com/Open-Network-Insight/open-network-insight/issues
>
>Issue tracking will be transitioned to Apache¹s JIRA instance during
>incubation.
>
>=== Code review ===
>
>Spot maintainers currently use ³LGTM² (Looks Good to Me) in comments
>on the code review to 

Re: [VOTE] Release of Apache Mnemonic-0.2.0-incubating [rc3]

[Gangumalla, Uma]

+1 (binding) [ forwarding my +1 from Mnemonic dev list vote ]

Regards,
Uma

On 7/29/16, 2:43 PM, "Gary"  wrote:

>Hello incubator PMC,
>
>The Apache Mnemonic community has voted and approved the proposal to
>release Apache Mnemonic 0.2.0 (incubating).
>
>Apache Mnemonic is an advanced hybrid memory storage oriented library,
>it've proposed a non-volatile/durable Java object model and durable
>computing service that bring several advantages to significantly improve
>the performance of massive real-time data processing/analytics.
>developers are able to use this library to design their cache-less and
>SerDe-less high performance applications.
>
>[VOTE] thread:
>http://mail-archives.apache.org/mod_mbox/incubator-mnemonic-dev/201607.mbo
>x/%3CCANLc_9KsRKk7G7NZfJdLpJRErQEoYYA4oev9YQ6nDN47zT%2BjVA%40mail.gmail.co
>m%3E
>http://mail-archives.apache.org/mod_mbox/incubator-mnemonic-dev/201607.mbo
>x/%3CCAG7vPRJDPfj%3D%2BZaT%3D_f8NnnLj5czvEZ%2BpDxw%3DCDLrLSfHZmG2w%40mail.
>gmail.com%3E
>http://mail-archives.apache.org/mod_mbox/incubator-mnemonic-dev/201607.mbo
>x/%3C0cfc3b3d-2634-3f42-1c1b-f632d1122c45%40apache.org%3E
>http://mail-archives.apache.org/mod_mbox/incubator-mnemonic-dev/201607.mbo
>x/%3C80833ADD533E324CA05C160E41B63661051C044B%40shsmsx102.ccr.corp.intel.c
>om%3E
>http://mail-archives.apache.org/mod_mbox/incubator-mnemonic-dev/201607.mbo
>x/%3C9037BCED616A964EB486B12FCA9DCFCF03B68109%40shsmsx102.ccr.corp.intel.c
>om%3E
>http://mail-archives.apache.org/mod_mbox/incubator-mnemonic-dev/201607.mbo
>x/%3CCALuGr6aXjmXroHaE41OwLooaf4jK9bf44NbBrF51-sQNuPkUjQ%40mail.gmail.com%
>3E
>http://mail-archives.apache.org/mod_mbox/incubator-mnemonic-dev/201607.mbo
>x/%3CCAHB_t6p0T0bQ_aWdRh%3DoWyFFyvJ9SNjPd0iA9992ZFagbQawRQ%40mail.gmail.co
>m%3E
>http://mail-archives.apache.org/mod_mbox/incubator-mnemonic-dev/201607.mbo
>x/%3CD3C0F6DA.213D0%25uma.gangumalla%40intel.com%3E
>
>[VOTE RESULT] thread:
>http://mail-archives.apache.org/mod_mbox/incubator-mnemonic-dev/201607.mbo
>x/%3C23f1a523-6843-dc5e-6ac6-231fa4ef6b99%40apache.org%3E
>
>We now kindly request the Incubator PMC members review and vote on this
>incubator release.
>
>The Apache Mnemonic-0.2.0-incubating release candidate is now available
>with the following artifacts for a project vote:
>
>The source tarball, including signatures, digests, etc. can be found at:
>https://dist.apache.org/repos/dist/dev/incubator/mnemonic/0.2.0-incubating
>-rc3/src/
>
>The tag to be voted upon is v0.2.0-incubating:
>https://git-wip-us.apache.org/repos/asf?p=incubator-mnemonic.git;a=shortlo
>g;h=refs/tags/v0.2.0-incubating
>
>The release hash is 6203b6f06177a48c860d63f72afb78eaae556ebc:
>https://git-wip-us.apache.org/repos/asf?p=incubator-mnemonic.git;a=commit;
>h=6203b6f06177a48c860d63f72afb78eaae556ebc
>
>Release artifacts are signed with the following key:
>https://dist.apache.org/repos/dist/dev/incubator/mnemonic/KEYS
>
>KEYS file available:
>https://dist.apache.org/repos/dist/dev/incubator/mnemonic/KEYS
>
>For information about the contents of this release, see:
>https://dist.apache.org/repos/dist/dev/incubator/mnemonic/0.2.0-incubating
>-rc3/CHANGES.txt
>
>The vote will be open for 72 hours.
>Please download the release candidate and evaluate the necessary items
>including checking hashes, signatures, build from source, and test.
>please vote:
>
>[ ] +1 Release this candidate
>[ ] +0 no opinion
>[ ] -1 Do not release this package because because...
>
>Thanks,
>Gary on behalf of the Apache Mnemonic (incubating) team
>
>
>
>
>
>
>
>


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Wiki access

[Gangumalla, Uma]

Hi,

 Can some one grant write access to my Wiki account?
 UserName: Uma Maheswara Rao G

Regards,
Uma

Re: [VOTE] Accept CarbonData into the Apache Incubator

[Gangumalla, Uma]

+1 (binding)

Regards,
Uma

On 5/25/16, 1:24 PM, "Jean-Baptiste Onofré"  wrote:

>Hi all,
>
>following the discussion thread, I'm now calling a vote to accept
>CarbonData into the Incubator.
>
>​[ ] +1 Accept CarbonData into the Apache Incubator
>[ ] +0 Abstain
>[ ] -1 Do not accept CarbonData into the Apache Incubator, because ...
>
>This vote is open for 72 hours.
>
>The proposal follows, you can also access the wiki page:
>https://wiki.apache.org/incubator/CarbonDataProposal
>
>Thanks !
>Regards
>JB
>
>= Apache CarbonData =
>
>== Abstract ==
>
>Apache CarbonData is a new Apache Hadoop native file format for faster
>interactive
>query using advanced columnar storage, index, compression and encoding
>techniques
>to improve computing efficiency, in turn it will help speedup queries an
>order of
>magnitude faster over PetaBytes of data.
>
>CarbonData github address: https://github.com/HuaweiBigData/carbondata
>
>== Background ==
>
>Huawei is an ICT solution provider, we are committed to enhancing
>customer experiences for telecom carriers, enterprises, and consumers on
>big data, In order to satisfy the following customer requirements, we
>created a new Hadoop native file format:
>
>  * Support interactive OLAP-style query over big data in seconds.
>  * Support fast query on individual record which require touching all
>fields.
>  * Fast data loading speed and support incremental load in period of
>minutes.
>  * Support HDFS so that customer can leverage existing Hadoop cluster.
>  * Support time based data retention.
>
>Based on these requirements, we investigated existing file formats in
>the Hadoop eco-system, but we could not find a suitable solution that
>satisfying requirements all at the same time, so we start designing
>CarbonData.
>
>== Rationale ==
>
>CarbonData contains multiple modules, which are classified into two
>categories:
>
>  1. CarbonData File Format: which contains core implementation for file
>format such as columnar,index,dictionary,encoding+compression,API for
>reading/writing etc.
>  2. CarbonData integration with big data processing framework such as
>Apache Spark, Apache Hive etc. Apache Beam is also planned to abstract
>the execution runtime.
>
>=== CarbonData File Format ===
>
>CarbonData file format is a columnar store in HDFS, it has many features
>that a modern columnar format has, such as splittable, compression
>schema ,complex data type etc. And CarbonData has following unique
>features:
>
> Indexing 
>
>In order to support fast interactive query, CarbonData leverage indexing
>technology to reduce I/O scans. CarbonData files stores data along with
>index, the index is not stored separately but the CarbonData file itself
>contains the index. In current implementation, CarbonData supports 3
>types of indexing:
>
>1. Multi-dimensional Key (B+ Tree index)
>  The Data block are written in sequence to the disk and within each
>data blocks each column block is written in sequence. Finally, the
>metadata block for the file is written with information about byte
>positions of each block in the file, Min-Max statistics index and the
>start and end MDK of each data block. Since, the entire data in the file
>is in sorted order, the start and end MDK of each data block can be used
>to construct a B+Tree and the file can be logically  represented as a
>B+Tree with the data blocks as leaf nodes (on disk) and the remaining
>non-leaf nodes in memory.
>2. Inverted index
>  Inverted index is widely used in search engine. By using this index,
>it helps processing/query engine to do filtering inside one HDFS block.
>Furthermore, query acceleration for count distinct like operation is
>made possible when combining bitmap and inverted index in query time.
>3. MinMax index
>  For all columns, minmax index is created so that processing/query
>engine can skip scan that is not required.
>
> Global Dictionary 
>
>Besides I/O reduction, CarbonData accelerates computation by using
>global dictionary, which enables processing/query engines to perform all
>processing on encoded data without having to convert the data (Late
>Materialization). We have observed dramatic performance improvement for
>OLAP analytic scenario where table contains many columns in string data
>type. The data is converted back to the user readable form just before
>processing/query engine returning results to user.
>
> Column Group 
>
>Sometimes users want to perform processing/query on multi-columns in one
>table, for example, performing scan for individual record in
>troubleshooting scenario. In this case, row format is more efficient
>than columnar format since all columns will be touched by the workload.
>To accelerate this, CarbonData supports storing a group of column in row
>format, so data in column group is stored together and enable fast
>retrieval.
>
> Optimized for multiple use cases 
>
>CarbonData indices and dictionary is highly configurable. To make
>storage 

Re: [DISCUSS] CarbonData incubation proposal

[Gangumalla, Uma]

+1 (binding)


Regards,
Uma

On 5/18/16, 8:52 PM, "Jean-Baptiste Onofré"  wrote:

>Hi all,
>
>We would like to discuss about a new proposal for the incubator:
>CarbonData.
>
>CarbonData is a new Apache Hadoop native file format for faster
>interactive query using advanced columnar storage, index, compression
>and encoding techniques to improve computing efficiency, in turn it will
>help speedup queries an order of magnitude faster over PetaBytes of data.
>
>The proposal is included below and also available on the wiki:
>
>https://wiki.apache.org/incubator/CarbonDataProposal
>
>Please, provide any feedback or comment.
>
>Thanks !
>Regards
>JB
>
>= Apache CarbonData =
>
>== Abstract ==
>
>Apache CarbonData is a new Apache Hadoop native file format for faster
>interactive
>query using advanced columnar storage, index, compression and encoding
>techniques
>to improve computing efficiency, in turn it will help speedup queries an
>order of
>magnitude faster over PetaBytes of data.
>
>CarbonData github address: https://github.com/HuaweiBigData/carbondata
>
>== Backgrounad ==
>
>Huawei is an ICT solution provider, we are committed to enhancing
>customer experiences for telecom carriers, enterprises, and consumers on
>big data, In order to satisfy the following customer requirements, we
>created a new Hadoop native file format:
>
>  * Support interactive OLAP-style query over big data in seconds.
>  * Support fast query on individual record which require touching all
>fields.
>  * Fast data loading speed and support incremental load in period of
>minutes.
>  * Support HDFS so that customer can leverage existing Hadoop cluster.
>  * Support time based data retention.
>
>Based on these requirements, we investigated existing file formats in
>the Hadoop eco-system, but we could not find a suitable solution that
>satisfying requirements all at the same time, so we start designing
>CarbonData.
>
>== Rationale ==
>
>CarbonData contains multiple modules, which are classified into two
>categories:
>
>  1. CarbonData File Format: which contains core implementation for file
>format such as columnar,index,dictionary,encoding+compression,API for
>reading/writing etc.
>  2. CarbonData integration with big data processing framework such as
>Apache Spark, Apache Hive etc. Apache Beam is also planned to abstract
>the execution runtime.
>
>=== CarbonData File Format ===
>
>CarbonData file format is a columnar store in HDFS, it has many features
>that a modern columnar format has, such as splittable, compression
>schema ,complex data type etc. And CarbonData has following unique
>features:
>
> Indexing 
>
>In order to support fast interactive query, CarbonData leverage indexing
>technology to reduce I/O scans. CarbonData files stores data along with
>index, the index is not stored separately but the CarbonData file itself
>contains the index. In current implementation, CarbonData supports 3
>types of indexing:
>
>1. Multi-dimensional Key (B+ Tree index)
>  The Data block are written in sequence to the disk and within each
>data blocks each column block is written in sequence. Finally, the
>metadata block for the file is written with information about byte
>positions of each block in the file, Min-Max statistics index and the
>start and end MDK of each data block. Since, the entire data in the file
>is in sorted order, the start and end MDK of each data block can be used
>to construct a B+Tree and the file can be logically  represented as a
>B+Tree with the data blocks as leaf nodes (on disk) and the remaining
>non-leaf nodes in memory.
>2. Inverted index
>  Inverted index is widely used in search engine. By using this index,
>it helps processing/query engine to do filtering inside one HDFS block.
>Furthermore, query acceleration for count distinct like operation is
>made possible when combining bitmap and inverted index in query time.
>3. MinMax index
>  For all columns, minmax index is created so that processing/query
>engine can skip scan that is not required.
>
> Global Dictionary 
>
>Besides I/O reduction, CarbonData accelerates computation by using
>global dictionary, which enables processing/query engines to perform all
>processing on encoded data without having to convert the data (Late
>Materialization). We have observed dramatic performance improvement for
>OLAP analytic scenario where table contains many columns in string data
>type. The data is converted back to the user readable form just before
>processing/query engine returning results to user.
>
> Column Group 
>
>Sometimes users want to perform processing/query on multi-columns in one
>table, for example, performing scan for individual record in
>troubleshooting scenario. In this case, row format is more efficient
>than columnar format since all columns will be touched by the workload.
>To accelerate this, CarbonData supports storing a group of column in row
>format, so data in column group is stored together and enable fast

Re: [VOTE] Accept PredictionIO into the Apache Incubator

[Gangumalla, Uma]

+1 (binding)

Regards,
Uma

On 5/23/16, 3:22 PM, "Andrew Purtell"  wrote:

>Since discussion on the matter of PredictionIO has died down, I would like
>to call a VOTE
>on accepting PredictionIO into the Apache Incubator.
>
>Proposal: https://wiki.apache.org/incubator/PredictionIO
>
>​[ ] +1 Accept PredictionIO into the Apache Incubator
>[ ] +0 Abstain
>[ ] -1 Do not accept PredictionIO into the Apache Incubator, because ...
>
>This vote will be open for at least 72 hours.
>
>My vote is +1 (binding)
>
>--
>
>PredictionIO Proposal
>
>Abstract
>
>PredictionIO is an open source Machine Learning Server built on top of
>state-of-the-art open source stack, that enables developers to manage and
>deploy production-ready predictive services for various kinds of machine
>learning tasks.
>
>Proposal
>
>The PredictionIO platform consists of the following components:
>
>   * PredictionIO framework - provides the machine learning stack for
> building, evaluating and deploying engines with machine learning
> algorithms. It uses Apache Spark for processing.
>
>   * Event Server - the machine learning analytics layer for unifying
>events
> from multiple platforms. It can use Apache HBase or any JDBC backends
> as its data store.
>
>The PredictionIO community also maintains a Template Gallery, a place to
>publish and download (free or proprietary) engine templates for different
>types of machine learning applications, and is a complemental part of the
>project. At this point we exclude the Template Gallery from the proposal,
>as it has a separate set of contributors and we’re not familiar with an
>Apache approved mechanism to maintain such a gallery.
>
>Background
>
>PredictionIO was started with a mission to democratize and bring machine
>learning to the masses.
>
>Machine learning has traditionally been a luxury for big companies like
>Google, Facebook, and Netflix. There are ML libraries and tools lying
>around the internet but the effort of putting them all together as a
>production-ready infrastructure is a very resource-intensive task that is
>remotely reachable by individuals or small businesses.
>
>PredictionIO is a production-ready, full stack machine learning system
>that
>allows organizations of any scale to quickly deploy machine learning
>capabilities. It comes with official and community-contributed machine
>learning engine templates that are easy to customize.
>
>Rationale
>
>As usage and number of contributors to PredictionIO has grown bigger and
>more diverse, we have sought for an independent framework for the project
>to keep thriving. We believe the Apache foundation is a great fit. Joining
>Apache would ensure that tried and true processes and procedures are in
>place for the growing number of organizations interested in contributing
>to PredictionIO. PredictionIO is also a good fit for the Apache
>foundation.
>PredictionIO was built on top of several Apache projects (HBase, Spark,
>Hadoop). We are familiar with the Apache process and believe that the
>democratic and meritocratic nature of the foundation aligns with the
>project goals.
>
>Initial Goals
>
>The initial milestones will be to move the existing codebase to Apache and
>integrate with the Apache development process. Once this is accomplished,
>we plan for incremental development and releases that follow the Apache
>guidelines, as well as growing our developer and user communities.
>
>Current Status
>
>PredictionIO has undergone nine minor releases and many patches.
>PredictionIO is being used in production by Salesforce.com as well as many
>other organizations and apps. The PredictionIO codebase is currently
>hosted at GitHub, which will form the basis of the Apache git repository.
>
>Meritocracy
>
>We plan to invest in supporting a meritocracy. We will discuss the
>requirements in an open forum. We intend to invite additional developers
>to participate. We will encourage and monitor community participation so
>that privileges can be extended to those that contribute.
>
>Community
>
>Acceptance into the Apache foundation would bolster the already strong
>user and developer community around PredictionIO. That community includes
>many contributors from various other companies, and an active mailing list
>composed of hundreds of users.
>
>Core Developers
>
>The core developers of our project are listed in our contributors and
>initial PPMC below. Though many are employed at Salesforce.com, there are
>also engineers from ActionML, and independent developers.
>
>Alignment
>
>The ASF is the natural choice to host the PredictionIO project as its goal
>is democratizing Machine Learning by making it more easily accessible to
>every user/developer. PredictionIO is built on top of several top level
>Apache projects as outlined above.
>
>Known Risks
>
>Orphaned Products
>
>PredictionIO has a solid and growing community. It is deployed on
>production environments by companies of all sizes to run various kinds of

Re: [DISCUSS] CarbonData incubation proposal

[Gangumalla, Uma]

Since the Parquet is ASF project, referencing may make sense to me,Yes, I
think Parquet project guys can comment on this point whether is it make
sense for them.
>With the usual precautions of a BD scan on the incoming
IP and ongoing diligence by the PPMC we'll be fine.
Thanks Julian for this point. So this should be action item for PPMC. So,
we can be good with voting on proposal I guess right?

Appreciate on the reviews. We can list out if any other points to fix
before code movement may be. Thanks Jacky for cleanup unused or refined
stuff.

Regards,
Uma


On 5/23/16, 4:19 PM, "Henry Saputra"  wrote:

>I thought the concern had been addressed?
>
>For Julian concern about Mondrian, the code was inspired by Mondrian but
>do
>not have direct derivatives of the code.
>According to Jacky, the old code is no longer used.
>
>As for Julien concern about Parquet, the design seemed to be inspired by
>Parquet and ORC.
>And if needed, we could add reference to Parquet in the code
>documentation.
>Since Parquet is ASF project, I believe we are in good shape in CarbonData
>goes to ASF.
>
>If any other action item is needed please do suggest so we could make
>correction as part of incubation process.
>
>
>- Henry
>
>On Mon, May 23, 2016 at 4:12 PM, Roman Shaposhnik 
>wrote:
>
>> On Mon, May 23, 2016 at 3:44 PM, Marvin Humphrey
>>
>> wrote:
>> > On Sun, May 22, 2016 at 10:57 PM, Jean-Baptiste Onofré
>>
>> wrote:
>> >> Hi Luke,
>> >>
>> >> I fully agree with you. The committers are already involved to
>>clean-up
>> the
>> >> repo (PRs have been created).
>> >>
>> >> IMHO, this step is decoupled from the proposal vote itself: the only
>> >> requirement is to do it for the code donation, after the proposal
>>vote.
>> >
>> > What will the process for this be?  On this thread we have two outside
>> > authors recognizing their own work, but that's obviously not a
>> > realistic mechanism for identifying all potentially problematic IP.
>>
>> Given that this is a donation from a corporate entity a request for BD
>> (or similar)
>> scan results (if they are available) may help. That's how every
>> corporate-sponsored
>> donation (at least dozens I've been involved in) does risk mitigation
>> anyway.
>>
>> Thanks,
>> Roman.
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release of Apache Mnemonic-0.1.2-incubating [rc2] (Revised)

[Gangumalla, Uma]

+1 (binding)



Thanks Justin.
Good idea, we will update README.txt. Here is the JIRA ticket filed by
Gary to track it.
https://issues.apache.org/jira/browse/MNEMONIC-51


BTW, below is the build success with mvn -pl
'!mnemonic-memory-services/mnemonic-nvml-vmem-service' clean package
This is in my OS X platform.


[INFO] 

[INFO] Reactor Summary:
[INFO] 
[INFO] mnemonic-parent  SUCCESS [
14.172 s]
[INFO] mnemonic-core .. SUCCESS [
10.495 s]
[INFO] mnemonic-collections ... SUCCESS [
1.456 s]
[INFO] mnemonic-examples .. SUCCESS [
0.720 s]
[INFO] mnemonic-memory-services ... SUCCESS [
0.361 s]
[INFO] mnemonic-pmalloc-service ... SUCCESS [
8.365 s]
[INFO] 

[INFO] BUILD SUCCESS
[INFO] 

[INFO] Total time: 36.047 s
[INFO] Finished at: 2016-05-20T12:24:28-07:00
[INFO] Final Memory: 35M/279M
[INFO] 

jcowher-mobl6:apache-mnemonic-0.1.2-incubating umgangum$ mvn -pl
'!mnemonic-memory-services/mnemonic-nvml-vmem-service' clean package

@Justin/Patrick, do you mind pasting the error details you are getting
while building into the JIRA?
https://issues.apache.org/jira/browse/MNEMONIC-51
And we continue discussion in that JIRA.


Regards,
Uma

On 5/20/16, 11:48 AM, "Wang, Gang1"  wrote:

>Hi Justin,
>
>   Thanks for your review and advices, we will create a ticket to add
>that  to README for OSX platform, Thanks.
>
>Best Regards
>B.R,
>+Gary
>
>-Original Message-
>From: Justin Mclean [mailto:jus...@classsoftware.com]
>Sent: Thursday, May 19, 2016 7:37 PM
>To: general@incubator.apache.org
>Subject: Re: [VOTE] Release of Apache Mnemonic-0.1.2-incubating [rc2]
>(Revised)
>
>Hi,
>
>+1 binding
>
>I checked:
>- file name contains incubating
>- DISCLAIMER exits
>- LICENSE and NOTICE correct
>- All source files have headers
>- No binary files in release
>- Unable to build from source
>
>Other than the build issue also a very easy release to review.
>
>I was unable to build from source on OSX even with:
> mvn -pl '!mnemonic-memory-services/mnemonic-nvml-vmem-service' clean
>package
>
>But assuming it¹s my setup.
>
>Would be nice for the README could have slightly clearer instructions on
>how to build on different platforms.
>
>Thanks,
>Justin
>-
>To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>For additional commands, e-mail: general-h...@incubator.apache.org
>


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Request to join Incubator PMC

[Gangumalla, Uma]

Hi Suneel,

 I think we may need to send mail to private@incubator as this is
generally to deal in private.
 I also sent a mail but waiting for response from IPMC. :-)


Regards,
Uma

On 3/29/16, 10:24 AM, "Suneel Marthi"  wrote:

>Hi All,
>
>I am interested in joining the incubator PMC.
>
>Regards,
>Suneel


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept Quickstep into the Apache Incubator

[Gangumalla, Uma]

+1 (non-binding)

Regards,
Uma

On 3/22/16, 2:01 PM, "shaposh...@gmail.com on behalf of Roman Shaposhnik"
 wrote:

>Hi!
>
>Quickstep proposal was made available for discussion last week
>https://wiki.apache.org/incubator/QuickstepProposal
>and the feedback so far seems to be positive.
>
>Please vote to accept Quickstep into the Apache Incubator.
>The vote will be open until Mon 3/28 noon PST.
>
>[ ] +1 Accept Quickstep into the Apache Incubator
>[ ] +0 Abstain
>[ ] -1 Don't accept Quickstep into the Apache Incubator because ...
>
>== Abstract ==
>
>Quickstep is a high-performance database engine. It is designed to (1)
>convert data to insights at bare-metal speed, (2) support multiple
>query surfaces including SQL (the first (and current) version only
>supports SQL, and (3) deliver bare-metal performance on any hardware
>(including running on a laptop, running on a high-end (single node)
>server, and running on a distributed cluster). Since its inception,
>the project has been planned to deliver a high-performance single node
>system first, followed by a distributed system.
>
>Quickstep is composed of several different modules that handle
>different concerns of a database system. The main modules are:
>  * Utility - Reusable general-purpose code that is used by many other
>modules.
>  * Threading - Provides a cross-platform abstraction for threads and
>synchronization primitives that abstract the underlying OS threading
>features.
>  * Types - The core type system used across all of Quickstep. Handles
>details of how SQL types are stored, parsed, serialized &
>deserialized, and converted. Also includes basic containers for typed
>values (tuples and column-vectors) and low-level operations that apply
>to typed values (e.g. basic arithmetic and comparisons).
>  * Catalog - Tracks database schema as well as physical storage
>information for relations (e.g. which physical blocks store a
>relation's data, and any physical partitioning and placement
>information).
>  * Storage - Physically stores relational data in self-contained,
>self-describing blocks, both in-memory and on persistent storage (disk
>or a distributed filesystem). Also includes some heavyweight run-time
>data structures used in query processing (e.g. hash tables for join
>and aggregation). Includes a buffer manager component for managing
>memory use and a file manager component that handles data persistence.
>  * Compression - Implements ordered dictionary compression. Several
>storage formats in the Storage module are capable of storing
>compressed column data and evaluating some expressions directly on
>compressed data without decompressing. The common code supporting
>compression is in this module.
>  * Expressions - Builds on the simple operations provided by the
>Types module to support arbitrarily complex expressions over data,
>including scalar expressions, predicates, and aggregate functions with
>and without grouping.
>  * Relational Operators - This module provides the building blocks
>for queries in Quickstep. A query is represented as a directed acyclic
>graph of relational operators, each of which is responsible for
>applying some relational-algebraic operation(s) to transform its
>input. Operators generate individual self-contained "work orders" that
>can be executed independently. Most operators are parallelism-friendly
>and generate one work-order per storage block of input.
>  * Query Execution - Handles the actual scheduling and execution of
>work from a query at runtime. The central class is the Foreman, an
>independent thread with a global view of the query plan and progress.
>The Foreman dispatches work-orders to stateless Worker threads and
>monitors their progress, and also coordinates streaming of partial
>results between producers and consumers in a query plan DAG to
>maximize parallelism. This module also includes the QueryContext
>class, which holds global shared state for an individual query and is
>designed to support easy serialization/deserialization for distributed
>execution.
>  * Parser - A simple SQL lexer and parser that parses SQL syntax into
>an abstract syntax tree for consumption by the Query Optimizer.
>  * Query Optimizer - Takes the abstract syntax tree generated by the
>parser and transforms it into a runable query-plan DAG for the Query
>Execution module. The Query Optimizer is responsible for resolving
>references to relations and attributes in the query, checking it for
>semantic correctness, and applying optimizations (e.g. filter
>pushdown, column pruning, join ordering) as part of the transformation
>process.
>  * Command-Line Interface - An interactive SQL shell interface to
>Quickstep.
>
>Quickstep is implemented in C++ and does not require many external
>libraries to run. Quickstep is currently an open source project
>licensed under the Apache License Version 2.0 and governed by a group
>of engineers at Pivotal.
>
>Quickstep began in 

Re: [DISCUSS] [PROPOSAL] Omid for Apache Incubator

[Gangumalla, Uma]

Proposal looks very good and clear. This project should be a good addition.

+1 (non-binding)

Regards,
Uma

On 3/17/16, 1:17 PM, "Daniel Dai"  wrote:

>Hi,
>
>I would like to propose Omid as an Apache Incubator project:
>
>https://wiki.apache.org/incubator/OmidProposal
>
>I've posted posted the text of the proposal below:
>
>Thanks,
>Daniel
>
>= Omid Proposal =
>
>=== Abstract ===
>
>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.
>
>
>=== Proposal ===
>
>Omid is a flexible open-source transactional framework that provides
>ACID transactions with Snapshot Isolation guarantees on top of NoSQL
>datastores. In particular, the current codebase brings the concept of
>transactions to the popular Apache HBase datastore. Omid offers great
>performance, it is highly available, and scalable. Omid's current
>version is able to scale to thousands of clients triggering concurrent
>transactions on application data stored in HBase. Omid can scale
>beyond 100K transactions per second on mid-range hardware while
>incurring in a minimal impact on the speed of data access in the
>datastore. We¹re currently experimenting with a prototype version that
>can improve the performance up to ~380K TPS.
>
>
>Omid has been publicly available as an open-source project in Github
>under Apache License Version 2.0 since 2011 [1]. During these years,
>it has generated certain interest in the open source community,
>especially since the public presentation of the first version in
>Hadoop Summit 2013 [2]. Currently the Github project has 241 Stars and
>93 forks. Yahoo Inc. submits this proposal to the Apache Software
>Foundation with the aim to transfer the Omid project -including its
>source code and documentation- to Apache in order to start the build
>of a stable open source community around it.
>
>
>[1] https://github.com/yahoo/omid
>
>[2] Omid presentation at Hadoop Summit 2013:
>https://www.youtube.com/watch?v=Rhdmo9pVGgU=68=PLSAiKuajRe2luyq
>LU464Nxz4aQe7EPBus
>
>
>=== Background ===
>
>An Omid prototype was first released as an open-source project back in
>2011. Inspired by Google Percolator [1], it offered a lock-free
>approach to transactions in NoSQL datastores (See [2]). However,
>during these years, the design of Omid has evolved significantly.
>Whilst the current open-sourced version maintains many aspects of the
>original implementation, it is the result of a major redesign of the
>first prototype released in 2011.
>
>
>Omid has now a more decentralized design that does not sacrifice the
>consistency and performance of the original version. The current
>design also enables Omid to scale to thousands of clients executing
>transactions concurrently on application data stored in HBase.
>Internally, Omid still utilizes a lock-free approach to support
>multiple concurrent clients. Its design also relies on a centralized
>conflict detection component, the TSO, which now resolves in an
>efficient manner writeset collisions among concurrent transactions
>without having to piggyback commit information to the clients. Another
>important benefit of Omid is that it doesn't require any modification
>of the underlying key-value datastore, HBase in this case. Moreover,
>the recently added high availability algorithm allows to eliminate the
>single point of failure represented by the TSO in those system
>deployments requiring a higher degree of dependability. Last but not
>least, the provided user API is very simple, mimicking transaction
>managers in the relational world: begin, commit, rollback.
>
>
>Omid is used internally at Yahoo. Sieve, Yahoo¹s web-scale content
>management platform powering some of next-generation search and
>personalization products is using Omid as a transaction manager in its
>processing pipeline. Sieve essentially acts as a huge processing hub
>between content feeds and serving systems. It provides an environment
>for highly customizable, real-time, streamed information processing,
>with typical discovery-to-service latencies of just a few seconds. In
>terms of scale and availability, Omid¹s new design was largely driven
>by Sieve¹s requirements.
>
>
>At Yahoo, we are also making an effort to disseminate the current
>status of the project through blog entries (See [3], [4] and [5]) and
>submissions to technical and academic conferences such as ATC 2016,
>Hadoop Summit 2016, HBaseConf 2016. Last but not least, Omid also
>appeared in a TechCrunch article in the last quarter of 2015 (See [6])
>
>
>[1] D. Peng and F. Dabek, Large-scale Incremental Processing Using
>Distributed Transactions and Notifications. USENIX Symposium on
>Operating Systems Design and Implementation, 2010
>
>[2] D. Gomez-Ferro, F. Junqueira, I. Kelly, B. Reed, and M. Yabandeh.
>Omid: Lock-free 

Re: [VOTE] Accept Tephra into the Apache Incubator

[Gangumalla, Uma]

+1 (non binding)

Regards,
Uma

On 3/3/16, 5:29 PM, "Poorna Chandra"  wrote:

>Hi All,
>
>Tephra proposal was sent out for discussion last week. The proposal is
>available at https://wiki.apache.org/incubator/TephraProposal
>
>Please vote to accept Tephra into the Apache Incubator. The vote will be
>open for the next 72 hours.
>
>[ ] +1 Accept Tephra as an Apache Incubator podling.
>[ ] +0 Abstain.
>[ ] -1 Don¹t accept Tephra as an Apache Incubator podling because ...
>
>Thanks,
>Poorna.
>
>--
>
>= Abstract =
>
>Tephra is a system for providing globally consistent transactions on
>top of Apache HBase and other storage engines.
>
>= Proposal =
>
>Tephra is a transaction engine for distributed data stores like Apache
>HBase.
>It provides ACID semantics for concurrent data operations that span over
>region
>boundaries in HBase using Optimistic Concurrency Control.
>
>= Background =
>
>HBase provides strong consistency with row- or region-level ACID
>operations. However, it sacrifices cross-region and cross-table
>consistency in favor of scalability. This trade-off requires application
>developers to handle  the complexity of ensuring consistency when their
>modifications span region boundaries. By providing support for global
>transactions that span regions, tables, or multiple RPCs,
>Tephra simplifies application development on top of HBase, without a
>significant impact on performance or scalability for many workloads.
>
>Tephra leverages HBase¹s native data versioning to provide multi-versioned
>concurrency control (MVCC) for transactional reads and writes.
>With MVCC capability, each transaction sees its own consistent ³snapshot²
>of
>data, providing snapshot isolation of concurrent transactions.
>MVCC along with conflict detection and handling enables Optimistic
>Concurrency
>Control.
>
>Tephra consists of three main components:
> * Transaction Server ­ maintains global view of transaction state,
>assigns
>   new transaction IDs and performs conflict detection;
> * Transaction Client ­ coordinates start, commit, and rollback of
>transactions; and
> * Transaction Processor Coprocessor ­ applies filtering to the data read
>(based
>   on a given transaction¹s state) and cleans up any data from old
>   (no longer visible) transactions.
>
>Although Tephra only supports HBase now, it can be extended to support
>transactions on any store that has multi-versioning and rollback
>support. The transactions
>can span over multiple stores and storage paradigms.
>
>= Rationale =
>
>Tephra has simple abstractions which can be used by an application to
>add transaction support over HBase. By abstracting away transaction
>handling using Tephra, the application is freed of
>transaction logic, and the application developer can focus on the use
>case.
>Also, Tephra can be extended to support transactions on data sources other
>than HBase.
>
>By making Tephra an Apache open source project, we believe that there will
>be wider adoption and more opportunities for Tephra to be integrated
>into other Apache projects.
>
>= Current Status =
>
>Tephra was built at Cask Data Inc. initially as part of
>open-source framework Cask Data Application Platform (CDAP)
>[[http://cdap.io/]].
>It was later converted into an independent open source project with
>Apache 2.0 License [[https://github.com/caskdata/tephra]].
>
>Tephra is used in CDAP as the transaction engine. As part of CDAP, Tephra
>has been deployed at multiple companies.
>
>Apache Phoenix is using Tephra as transaction engine in the next release.
>
>== Meritocracy ==
>
>Our intent with this incubator proposal is to start building a diverse
>developer community around Tephra following the Apache meritocracy model.
>Since Tephra was initially developed in early 2013, we have had fast
>adoption and contributions within Cask Data. We are looking forward to
>new contributors. We wish to build a community based on Apache's
>meritocracy principles, working with those who contribute significantly to
>the project and welcoming them to be committers both during the incubation
>process and beyond.
>
>== Community ==
>
>Core developers of Tephra are at Cask Data. Recently the developer
>community
>has expanded to include folks from Apache Phoenix. We hope to extend our
>contributor base significantly and we will invite all who are interested
>in working on distributed transaction engine.
>
>== Core Developers ==
>
>A few engineers from Cask Data and outside have developed Tephra:
>Andreas Neumann, Terence Yim, Gary Helmling, Andrew Purtell and
>Poorna Chandra.
>
>
>== Alignment ==
>
>The ASF is the natural choice to host the Tephra project as its goal of
>encouraging community-driven open source projects fits with our vision for
>Tephra.
>
>Additionally, many other projects with which we are familiar and expect
>Tephra to integrate with, such as Phoenix, Zookeeper, HDFS, log4j, and
>others
>mentioned in the External Dependencies section are Apache projects, and

Re: [VOTE] Accept Gearpump into the Apache Incubator

[Gangumalla, Uma]

+1 (non-binding)

Regards,
Uma

On 3/1/16, 4:53 PM, "Andrew Purtell"  wrote:

>Greetings,
>
>The discussion of the Gearpump proposal has concluded. Please vote to
>accept Gearpump into the Apache Incubator. I will leave this vote open for
>at least the next 72 hours and will aim to close it Monday the 7th of
>March, 2016 at midnight PT. Gearpump is a flexible, efficient, and
>scalable
>micro-service based real-time big data streaming engine. The text of the
>proposal is included below and is also available at
>https://wiki.apache.org/incubator/GearpumpProposal
>
>[ ] +1 Accept Gearpump as an Apache Incubator podling.
>[ ] +0 Abstain.
>[ ] -1 Don’t accept Gearpump as an Apache Incubator podling because ...
>
>Note that while votes from Incubator PMC members are binding, all are most
>definitely welcome to vote!
>
>I am +1 (binding).
>
>Best regards,
>
>   - Andy
>
>​-
>
>= Gearpump Proposal =
>
>=== Abstract ===
>Gearpump is a flexible, efficient and scalable micro-service based
>real-time big data streaming engine developed by Intel Corporation which
>has been licensed by Intel under the Apache License 2.0.
>
>=== Proposal ===
>Gearpump is a reactive real-time streaming engine; completely based on the
>micro-service Actor model. Gearpump provides extremely high performance
>stream processing while maintaining millisecond latency message delivery.
>It enables reusable, composable flows or partial graphs that can be
>remotely deployed and executed in a diverse set of environments, including
>IoT edge devices. These flows may be deployed and modified at runtime -- a
>capability few real time streaming frameworks provide today.
>
>The goal of this proposal is to incubate Gearpump as an Apache project in
>order to build a diverse, healthy, and self-governed open source community
>around this project.
>
>=== Background ===
>In past decade, there have been many advances within real-time streaming
>frameworks. Despite many advances, users of streaming frameworks often
>complain about flexibility, efficiency, and scalability. Gearpump
>endeavors
>to solve these challenges by adopting the micro-service Actor model. The
>Actor model was proposed by Carl Hewitt in 1973. In the Actor model, each
>actor is a message driven micro-service; actors are the basic building
>blocks of concurrent computation. By leveraging Actor Model’s location
>transparency feature,Gearpump allows a graph to be composed of several
>partial graphs, where, for example, some parts may be deployed to remote
>IoT edge devices, and other parts to a data center. This division and
>deployment model can be changed at runtime to adapt to a changing physical
>environment, providing extreme flexibility and elasticity in solving
>various ingestion and analytics problems. We’ve found Actors to be a much
>smaller computation unit compared with threads, where smaller usually
>means
>better concurrency, and potentially better CPU utilization.
>
>=== Rationale ===
>Gearpump tightly integrates and enhances the big data community of Apache
>projects. Intel believes Gearpump can bring benefits to the Apache
>community in a number of ways:
>
>1. Gearpump complements many existing Apache projects, in particular,
>those
>commonly found within the big data space. Users of this project are also
>users of other Apache projects, such as Hadoop ecosystem projects. It is
>beneficial to align these projects under the ASF umbrella. In real-time
>streaming, Gearpump offers some special features that are useful for
>Apache
>users, such as exactly-once processing with millisecond message level
>latency and dynamic DAGs that allow online topology modifications.
>
>2. Gearpump tightly integrates with Apache big data projects. It supports
>for Apache HDFS, YARN, Kafka, and HBase. It uses Apache YARN for resource
>scheduling and Apache HDFS as the essential distributed storage system.
>
>3. The micro-service model of reusable flows that Gearpump has adopted is
>very unique, and it may become common in the future.Gearpump sets a good
>example about how distributed software can be implemented within a
>micro-service model.  An open project is of best interest to our users. By
>joining Apache, it will be a neutral infrastructure platform that will
>benefit everyone.
>
>4. The process and development philosophy of Apache will help Gearpump
>grow,
>and build a diverse, healthy, and self-governed open source community.
>
>=== Initial Goals ===
>1. Migrate the existing codebase to Apache.
>
>2. Setup Jira, website and other development tools by following Apache
>best
>practices.
>
>3. Start the first release per Apache guidelines as soon as possible.
>
>=== Current Status ===
>Gearpump is hosted on Github. It has 1922 commits, 38284 line of code, and
>31 major or minor releases, with release notes highlighting the changes
>for
>every release. It is licensed under Apache License Version 2. There is a
>documentation site at http://gearpump.io
>​ ​
>including a 

Re: [VOTE] Accept Mnemonic into the Apache Incubator

[Gangumalla, Uma]

+1 (non-binding)

Regards,
Uma

On 2/29/16, 9:37 AM, "Patrick Hunt"  wrote:

>Hi folks,
>
>OK the discussion is now completed. Please VOTE to accept Mnemonic
>into the Apache Incubator. I¹ll leave the VOTE open for at least
>the next 72 hours, with hopes to close it Thursday the 3rd of
>March, 2016 at 10am PT.
>https://wiki.apache.org/incubator/MnemonicProposal
>
>[ ] +1 Accept Mnemonic as an Apache Incubator podling.
>[ ] +0 Abstain.
>[ ] -1 Don¹t accept Mnemonic as an Apache Incubator podling because..
>
>Of course, I am +1 on this. Please note VOTEs from Incubator PMC
>members are binding but all are welcome to VOTE!
>
>Regards,
>
>Patrick
>
>
>= Mnemonic Proposal =
>=== Abstract ===
>Mnemonic is a Java based non-volatile memory library for in-place
>structured data processing and computing. It is a solution for generic
>object and block persistence on heterogeneous block and
>byte-addressable devices, such as DRAM, persistent memory, NVMe, SSD,
>and cloud network storage.
>
>=== Proposal ===
>Mnemonic is a structured data persistence in-memory in-place library
>for Java-based applications and frameworks. It provides unified
>interfaces for data manipulation on heterogeneous
>block/byte-addressable devices, such as DRAM, persistent memory, NVMe,
>SSD, and cloud network devices.
>
>The design motivation for this project is to create a non-volatile
>programming paradigm for in-memory data object persistence, in-memory
>data objects caching, and JNI-less IPC.
>Mnemonic simplifies the usage of data object caching, persistence, and
>JNI-less IPC for massive object oriented structural datasets.
>
>Mnemonic defines Non-Volatile Java objects that store data fields in
>persistent memory and storage. During the program runtime, only
>methods and volatile fields are instantiated in Java heap,
>Non-Volatile data fields are directly accessed via GET/SET operation
>to and from persistent memory and storage. Mnemonic avoids SerDes and
>significantly reduces amount of garbage in Java heap.
>
>Major features of Mnemonic:
>* Provides an abstract level of viewpoint to utilize heterogeneous
>block/byte-addressable device as a whole (e.g., DRAM, persistent
>memory, NVMe, SSD, HD, cloud network Storage).
>
>* Provides seamless support object oriented design and programming
>without adding burden to transfer object data to different form.
>
>* Avoids the object data serialization/de-serialization for data
>retrieval, caching and storage.
>
>* Reduces the consumption of on-heap memory and in turn to reduce and
>stabilize Java Garbage Collection (GC) pauses for latency sensitive
>applications.
>
>* Overcomes current limitations of Java GC to manage much larger
>memory resources for massive dataset processing and computing.
>
>* Supports the migration data usage model from traditional NVMe/SSD/HD
>to non-volatile memory with ease.
>
>* Uses lazy loading mechanism to avoid unnecessary memory consumption
>if some data does not need to use for computing immediately.
>
>* Bypasses JNI call for the interaction between Java runtime
>application and its native code.
>
>* Provides an allocation aware auto-reclaim mechanism to prevent
>external memory resource leaking.
>
>
>=== Background ===
>Big Data and Cloud applications increasingly require both high
>throughput and low latency processing. Java-based applications
>targeting the Big Data and Cloud space should be tuned for better
>throughput, lower latency, and more predictable response time.
>Typically, there are some issues that impact BigData applications'
>performance and scalability:
>
>1) The Complexity of Data Transformation/Organization: In most cases,
>during data processing, applications use their own complicated data
>caching mechanism for SerDes data objects, spilling to different
>storage and eviction large amount of data. Some data objects contains
>complex values and structure that will make it much more difficulty
>for data organization. To load and then parse/decode its datasets from
>storage consumes high system resource and computation power.
>
>2) Lack of Caching, Burst Temporary Object Creation/Destruction Causes
>Frequent Long GC Pauses: Big Data computing/syntax generates large
>amount of temporary objects during processing, e.g. lambda, SerDes,
>copying and etc. This will trigger frequent long Java GC pause to scan
>references, to update references lists, and to copy live objects from
>one memory location to another blindly.
>
>3) The Unpredictable GC Pause: For latency sensitive applications,
>such as database, search engine, web query, real-time/streaming
>computing, require latency/request-response under control. But current
>Java GC does not provide predictable GC activities with large on-heap
>memory management.
>
>4) High JNI Invocation Cost: JNI calls are expensive, but high
>performance applications usually try to leverage native code to
>improve performance, however, JNI calls need to convert Java objects
>into 

Re: [DISCUSS] Mnemonic incubator proposal

[Gangumalla, Uma]

Hi Liang,

Thank you for your interest. Sure we would consider you adding in
interested contributors list.
 
>Mnemonic is trying to solve performance issues associated
with serialization/deserialization of java object when dealing with JVM &
disk directly as well as GC pressure caused by caching ?

Yes.

>whether Mnemonic could solve Hadoop Namenode pressure of large
scale of cluster scenaros, or not?
Yeah, we are thinking on some aspects considering memory and GC overheads
in Namenode too.
Example couple of JIRAs already there in HDFS to move some of data
structure to off heap. So, we had plans to get the standard data
structures from this library and can make use of them push.
Also we could make advantage if persistence here.


@Yanping/Gary, may be you could add more points if you have?

Regards,
Uma

On 2/23/16, 6:48 PM, "Liang Chen"  wrote:

>Interesting, would love to become the contributor
>
>My understanding: Mnemonic is trying to solve performance issues
>associated
>with serialization/deserialization of java object when dealing with JVM &
>disk directly as well as GC pressure caused by caching ?
>
>one question: whether Mnemonic could solve Hadoop Namenode pressure of
>large
>scale of cluster scenaros, or not?
>
>
>
>--
>View this message in context:
>http://apache-incubator-general.996316.n3.nabble.com/DISCUSS-Mnemonic-incu
>bator-proposal-tp48502p48533.html
>Sent from the Apache Incubator - General mailing list archive at
>Nabble.com.
>
>-
>To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>For additional commands, e-mail: general-h...@incubator.apache.org
>


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org