Apache account creation issues
Hi all - I submitted an ICLA to be a committer on Apache Druid (incubating) several months ago. I was notified some time ago that the ID that I chose was too short so I responded with a longer ID. Since then, I haven't heard anything back and my ID still hasn't been created. I was told I should email this list for help. The ID I would like to use is 'fjy'. Best, FJ
Re: [VOTE] Accept Doris into the Apache Incubator
+1 (binding) Sounds like a really interesting project. I hope to see more PPMC members from outside Baidu over time of course! On Fri, 6 Jul 2018 at 04:20, Timothy Chen wrote: > +1 (binding) > > Been following the discussions and knowing the mentors I believe the team > can continue to improve and learn how the Apache way works. > > Tim > On Fri, Jul 6, 2018 at 5:15 PM Bertrand Delacretaz < > bdelacre...@codeconsult.ch> wrote: > > > On Fri, Jul 6, 2018 at 10:11 AM Li,De(BDG) wrote: > > > ...None of them are affiliated with Baidu Inc., just initial committers > > are... > > > > Ok, thanks for clarifying! > > > > Here's my +1 > > > > -Bertrand > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > -- Matt Sicker
Re: [VOTE] Accept Doris into the Apache Incubator
+1 (binding) Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Fri, Jul 6, 2018 at 3:22 AM, Dave Fisher wrote: > Hi All, > > I would like to start a VOTE to bring the Doris project 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 Doris into the Apache Incubator > [] +0 Abstain. > [] -1 Do not accept Doris into the Apache Incubator because ... > > The proposal is listed below, but you can also access it on the wiki: > > https://wiki.apache.org/incubator/DorisProposal > > Best regards, > Dave > > = Apache Doris = > > == Abstract == > > Doris is a MPP-based interactive SQL data warehousing for reporting and > analysis. > > == Proposal == > > We propose to contribute the Doris codebase and associated artifacts (e.g. > documentation, web-site content etc.) to the Apache Software Foundation, > and aim to build an open community around Doris’s continued development in > the ‘Apache Way’. > > === Overview of Doris === > > Doris’s implementation consists of two daemons: Frontend (FE) and Backend > (BE). > > **Frontend daemon** consists of query coordinator and catalog manager. > Query coordinator is responsible for receiving users’ sql queries, > compiling queries and managing queries execution. Catalog manager is > responsible for managing metadata such as databases, tables, partitions, > replicas and etc. Several frontend daemons could be deployed to guarantee > fault-tolerance, and load balancing. > > **Backend daemon** stores the data and executes the query fragments. Many > backend daemons could also be deployed to provide scalability and > fault-tolerance. > > A typical Doris cluster generally composes of several frontend daemons and > dozens to hundreds of backend daemons. > > Users can use MySQL client tools to connect any frontend daemon to submit > SQL query. Frontend receives the query and compiles it into query plans > executable by the Backend. Then Frontend sends the query plan fragments to > Backend. Backend will build a query execution DAG. Data is fetched and > pipelined into the DAG. The final result response is sent to client via > Frontend. The distribution of query fragment execution takes minimizing > data movement and maximizing scan locality as the main goal. > > == Background == > > At Baidu, Prior to Doris, different tools were deployed to solve diverse > requirements in many ways. And when a use case requires the simultaneous > availability of capabilities that cannot all be provided by a single tool, > users were forced to build hybrid architectures that stitch multiple tools > together, but we believe that they shouldn’t need to accept such inherent > complexity. A storage system built to provide great performance across a > broad range of workloads provides a more elegant solution to the problems > that hybrid architectures aim to solve. Doris is the solution. > > Doris is designed to be a simple and single tightly coupled system, not > depending on other systems. Doris provides high concurrent low latency > point query performance, but also provides high throughput queries of > ad-hoc analysis. Doris provides bulk-batch data loading, but also provides > near real-time mini-batch data loading. Doris also provides high > availability, reliability, fault tolerance, and scalability. > > == Rationale == > > Doris mainly integrates the technology of Google Mesa and Apache Impala. > > Mesa is a highly scalable analytic data storage system that stores > critical measurement data related to Google's Internet advertising > business. Mesa is designed to satisfy complex and challenging set of users’ > and systems’ requirements, including near real-time data ingestion and > query ability, as well as high availability, reliability, fault tolerance, > and scalability for large data and query volumes. > > Impala is a modern, open-source MPP SQL engine architected from the ground > up for the Hadoop data processing environment. At present, by virtue of its > superior performance and rich functionality， Impala has been comparable to > many commercial MPP database query engine. Mesa can satisfy the needs of > many of our storage requirements, however Mesa itself does not provide a > SQL query engine; Impala is a very good MPP SQL query engine, but the lack > of a perfect distributed storage engine. So in the end we chose the > combination of these two technologies. > > Learning from Mesa’s data model, we developed a distributed storage > engine. Unlike Mesa, this storage engine does not rely on any distributed > file system. Then we deeply integrate this storage engine with Impala query > engine. Query compiling, query execution coordination and catalog > management of storage engine are integrated to be
Re: [VOTE] Release Apache Amaterasu (incubating) 0.2.0 (rc4)
Hi All, Just a reminder, we are still in need for reviews/votes. Thanks in advance, Yaniv On Thu, 5 Jul 2018 at 10:01 am, Yaniv Rodenski wrote: > Hi all, > > Just bumping this thread, we are still in need of reviews/votes. > > Thanks in advance, > Yaniv > > > On Sun, Jul 1, 2018 at 3:08 PM, Yaniv Rodenski wrote: > >> Hi All, >> >> The Apache Amaterasu (incubating) community has voted on and approved a >> proposal to release Apache Amaterasu 0.2.0-rc4. >> >> We now kindly request that the Incubator PMC members review and vote on >> this incubator release candidate. >> >> Apache Amaterasu is a Configuration Managment and Deployment >> Framework for Big Data Pipelines. >> >> The vote thread is available at: >> >> https://lists.apache.org/thread.html/4e57fefc663bf9458440bd2d77255f11f1296cf3b029f39414a8af15@%3Cdev.amaterasu.apache.org%3E >> >> >> and the result is available at: >> >> https://lists.apache.org/thread.html/67977aef91a0fc947b2b1c2a87196a0a99704c9747b04da7178da566@%3Cdev.amaterasu.apache.org%3E >> >> >> This is the first incubator release and it includes much-awaited >> improvements such as YARN support, PySpark and SparkSQL support and >> stability improvements. >> In addition, RC4 fixed the issues that ware detected in RC3 during the >> previous vote. >> >> All distribution packages, including signatures, digests, etc. can be >> found at: >> https://dist.apache.org/repos/dist/dev/incubator/amaterasu/0.2.0rc4/ >> >> >> This release has been signed with PGP key corresponding to >> ya...@apache.org, which is included in the repository's KEYS file ( >> https://dist.apache.org/repos/dist/dev/incubator/amaterasu/KEYS). >> >> The release candidate has been tagged in git with >> version-0.2.0-incubating-rc4: >> >> https://github.com/apache/incubator-amaterasu/releases/tag/version-0.2.0-incubating-rc4 >> >> Please review and vote. The vote will be open for at least 72 hours. >> >> Thank you very much, >> Yaniv >> >> > > > -- > Yaniv Rodenski > > +61 477 778 405 > ya...@shinto.io > > -- Yaniv Rodenski +61 477 778 405 ya...@shinto.io
Re: Apache account creation issues
I have submitted an account request. Sorry the original request got ignored by the Druid mentors, including myself. Just in case, please check your spam folder: I emailed you yesterday that I had submitted an account request, apparently before you sent this email, and it’s possible that other messages from apache have been lost. > On Jul 6, 2018, at 4:33 PM, Fangjin wrote: > > Hi all - > > I submitted an ICLA to be a committer on Apache Druid (incubating) several > months ago. I was notified some time ago that the ID that I chose was too > short so I responded with a longer ID. Since then, I haven't heard anything > back and my ID still hasn't been created. I was told I should email this > list for help. The ID I would like to use is 'fjy'. > > Best, > FJ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Doris into the Apache Incubator
My +1 no-binding. Welcome to join the community. Interesting project. -- Sheng Wu Apache SkyWalking -- Original -- From: "Matt Sicker"; Date: Sun, Jul 8, 2018 03:22 AM To: "general"; Subject: Re: [VOTE] Accept Doris into the Apache Incubator +1 (binding) Sounds like a really interesting project. I hope to see more PPMC members from outside Baidu over time of course! On Fri, 6 Jul 2018 at 04:20, Timothy Chen wrote: > +1 (binding) > > Been following the discussions and knowing the mentors I believe the team > can continue to improve and learn how the Apache way works. > > Tim > On Fri, Jul 6, 2018 at 5:15 PM Bertrand Delacretaz < > bdelacre...@codeconsult.ch> wrote: > > > On Fri, Jul 6, 2018 at 10:11 AM Li,De(BDG) wrote: > > > ...None of them are affiliated with Baidu Inc., just initial committers > > are... > > > > Ok, thanks for clarifying! > > > > Here's my +1 > > > > -Bertrand > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > -- Matt Sicker
Re: [VOTE] Accept Doris into the Apache Incubator
+1 (binding) Regards JB On 05/07/2018 21:22, Dave Fisher wrote: > Hi All, > > I would like to start a VOTE to bring the Doris project 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 Doris into the Apache Incubator > [] +0 Abstain. > [] -1 Do not accept Doris into the Apache Incubator because ... > > The proposal is listed below, but you can also access it on the wiki: > > https://wiki.apache.org/incubator/DorisProposal > > Best regards, > Dave > > = Apache Doris = > > == Abstract == > > Doris is a MPP-based interactive SQL data warehousing for reporting and > analysis. > > == Proposal == > > We propose to contribute the Doris codebase and associated artifacts > (e.g. documentation, web-site content etc.) to the Apache Software > Foundation, and aim to build an open community around Doris’s continued > development in the ‘Apache Way’. > > === Overview of Doris === > > Doris’s implementation consists of two daemons: Frontend (FE) and > Backend (BE). > > **Frontend daemon** consists of query coordinator and catalog manager. > Query coordinator is responsible for receiving users’ sql queries, > compiling queries and managing queries execution. Catalog manager is > responsible for managing metadata such as databases, tables, partitions, > replicas and etc. Several frontend daemons could be deployed to > guarantee fault-tolerance, and load balancing. > > **Backend daemon** stores the data and executes the query fragments. > Many backend daemons could also be deployed to provide scalability and > fault-tolerance. > > A typical Doris cluster generally composes of several frontend daemons > and dozens to hundreds of backend daemons. > > Users can use MySQL client tools to connect any frontend daemon to > submit SQL query. Frontend receives the query and compiles it into query > plans executable by the Backend. Then Frontend sends the query plan > fragments to Backend. Backend will build a query execution DAG. Data is > fetched and pipelined into the DAG. The final result response is sent to > client via Frontend. The distribution of query fragment execution takes > minimizing data movement and maximizing scan locality as the main goal. > > == Background == > > At Baidu, Prior to Doris, different tools were deployed to solve diverse > requirements in many ways. And when a use case requires the simultaneous > availability of capabilities that cannot all be provided by a single > tool, users were forced to build hybrid architectures that stitch > multiple tools together, but we believe that they shouldn’t need to > accept such inherent complexity. A storage system built to provide great > performance across a broad range of workloads provides a more elegant > solution to the problems that hybrid architectures aim to solve. Doris > is the solution. > > Doris is designed to be a simple and single tightly coupled system, not > depending on other systems. Doris provides high concurrent low latency > point query performance, but also provides high throughput queries of > ad-hoc analysis. Doris provides bulk-batch data loading, but also > provides near real-time mini-batch data loading. Doris also provides > high availability, reliability, fault tolerance, and scalability. > > == Rationale == > > Doris mainly integrates the technology of Google Mesa and Apache Impala. > > Mesa is a highly scalable analytic data storage system that stores > critical measurement data related to Google's Internet advertising > business. Mesa is designed to satisfy complex and challenging set of > users’ and systems’ requirements, including near real-time data > ingestion and query ability, as well as high availability, reliability, > fault tolerance, and scalability for large data and query volumes. > > Impala is a modern, open-source MPP SQL engine architected from the > ground up for the Hadoop data processing environment. At present, by > virtue of its superior performance and rich functionality， Impala has > been comparable to many commercial MPP database query engine. Mesa can > satisfy the needs of many of our storage requirements, however Mesa > itself does not provide a SQL query engine; Impala is a very good MPP > SQL query engine, but the lack of a perfect distributed storage engine. > So in the end we chose the combination of these two technologies. > > Learning from Mesa’s data model, we developed a distributed storage > engine. Unlike Mesa, this storage engine does not rely on any > distributed file system. Then we deeply integrate this storage engine > with Impala query engine. Query compiling, query execution coordination > and catalog management of storage engine are integrated to be frontend > daemon; query
Re: [VOTE] Release Apache Amaterasu (incubating) 0.2.0 (rc4)
+1 (binding) However, IMHO, the NOTICE file is not correct: it just mentions ASF included software, but actually, as it's the same NOTICE used for binary and source, it should mention other third parties like scala, slf4j, scopt, jetty, liftweb. IMHO, not a blocker for this release, but worth to fix that for next one. Regards JB On 01/07/2018 07:08, Yaniv Rodenski wrote: > Hi All, > > The Apache Amaterasu (incubating) community has voted on and approved a > proposal to release Apache Amaterasu 0.2.0-rc4. > > We now kindly request that the Incubator PMC members review and vote on > this incubator release candidate. > > Apache Amaterasu is a Configuration Managment and Deployment Framework for > Big Data Pipelines. > > The vote thread is available at: > https://lists.apache.org/thread.html/4e57fefc663bf9458440bd2d77255f11f1296cf3b029f39414a8af15@%3Cdev.amaterasu.apache.org%3E > > > and the result is available at: > https://lists.apache.org/thread.html/67977aef91a0fc947b2b1c2a87196a0a99704c9747b04da7178da566@%3Cdev.amaterasu.apache.org%3E > > > This is the first incubator release and it includes much-awaited > improvements such as YARN support, PySpark and SparkSQL support and > stability improvements. > In addition, RC4 fixed the issues that ware detected in RC3 during the > previous vote. > > All distribution packages, including signatures, digests, etc. can be > found at: > https://dist.apache.org/repos/dist/dev/incubator/amaterasu/0.2.0rc4/ > > > This release has been signed with PGP key corresponding to > ya...@apache.org, which is included in the repository's KEYS file ( > https://dist.apache.org/repos/dist/dev/incubator/amaterasu/KEYS). > > The release candidate has been tagged in git with version-0.2.0-incubating- > rc4: > https://github.com/apache/incubator-amaterasu/releases/tag/version-0.2.0-incubating-rc4 > > Please review and vote. The vote will be open for at least 72 hours. > > Thank you very much, > Yaniv > -- 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
