Re: FOSDEM 2020 Update
Hi Sharan, Am 16.02.20 um 06:02 schrieb Sharan Foga: > Hi Everyone > > (Sorry for the delayed post as I am currently travelling overseas and wont be > back to normal till early next month.) > > As usual during the first weekend in February FOSDEM was held in Brussels and > I wanted to to post a quick update. > > FOSDEM and rain. Rain and FOSDEM - they always seem to both go together but > that doesnt stop thousands of people turning up to meet, discuss and learn > about new open source technologies and ideas. > > Huge thanks to Martin van dem Bemt for being our FOSDEM swag storage > warehouse and also to Daniel Gruno for co-ordinating ASF swag central. We had > our banner, over booth cover and what seemed like millions of stickers. > People would walk by do a double take and look again...then take a picture of > all the stickers. Even with the stickers we had - we knew it wasnt them all. > > This year we were back on the first floor of K block right at the top of the > stairs so everyone had to pass by us . so we got some great foot traffic. I > got there at around 9am to find Martin, Daniel and Claude already there and > getting things setup. > > As well as stickers we gave away some balloons for the children (and adults > too), some fleece hats and bags left over from last year, some coffee thermos > containers, feather and committer pins plus lots and lots of pens. It all > disappeared! > > We had people from various projects take time on the booth - so thanks to Dan > (Dahn :-) Hogland from cloudstack, Claude Warren from Jena, the Open Office > team, as well as all the others who dropped by to say hello and spend some > time talking to people. People always seem to be amazed at the number of > projects and even without realising it that it is Apache Maven not just > Maven, Apache Hadoop not just Hadoop, Apache Spark, not just Spark. This is > one of the reasons that having a booth presence is great for outreach and > general community building. FOSDEM 2020 was really great and it was nice to meet you again! I also learned a lot about all those different ASF projects people were asking stickers for... But with my PMC hat on: It is "OpenOffice" not "Open Office" ;-) Regards, Matthias > > We also had the D&I team spend some time on the booth talking to people about > the ASF survey and encouraging people to go online and fill it out. > > For the last few years I have been involved with the Community Devroom but > till now had never managed to see a community talk. That changed this year > and I spent most of Sunday helping out in the Community Devroom and saw some > amazing talks. At several points the room was completely full with a queue > waiting outside the door. This shows that people are really keen to learn > about and understand topics related to open source communities so I would > encourage everyone to keep it on their radar for the next FOSDEM! > > While at FOSDEM I received several invitations for the ASF to have a booth at > other open source events including FOSSASIA, OpenExpo Europe and an open > source conference in Mauritius, so if you are interested in participating in > any of these events then please let me know. > > I would really like to thank everyone that was involved in helping out to > make the event a success. Looking forward to doing it all again next year if > we get the chance. > > I'm happy to hear about any other FOSDEM experiences, feedback, thoughts, > comments. > > Thanks > Sharan > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
[jira] [Created] (COMDEV-341) Apache RocketMQ Scaler for KEDA
duheng created COMDEV-341: - Summary: Apache RocketMQ Scaler for KEDA Key: COMDEV-341 URL: https://issues.apache.org/jira/browse/COMDEV-341 Project: Community Development Issue Type: Wish Components: GSoC/Mentoring ideas Reporter: duheng h3. Context KEDA allows for fine-grained autoscaling (including to/from zero) for event-driven Kubernetes workloads. KEDA serves as a Kubernetes Metrics Server and allows users to define autoscaling rules using a dedicated Kubernetes custom resource definition. KEDA has a number of “scalers” that can both detect if a deployment should be activated or deactivated, and feed custom metrics for a specific event source. In this topic, you need to implement the RocketMQ scalers. h3. You should learn before applying for this topic Helm/Apache RocketMQ Operator/Apache RocketMQ Docker Image Apache RocketMQ multi-replica mechanism(based on DLedger) How KEDA works h3. Mentor [wlliqip...@apache.org|mailto:wlliqip...@apache.org], [vongosl...@apache.org|mailto:vongosl...@apache.org] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Created] (COMDEV-342) Apache RocketMQ Connect Flink
duheng created COMDEV-342: - Summary: Apache RocketMQ Connect Flink Key: COMDEV-342 URL: https://issues.apache.org/jira/browse/COMDEV-342 Project: Community Development Issue Type: Wish Components: GSoC/Mentoring ideas Reporter: duheng h3. Context There are many ways that Apache Flink and Apache RocketMQ can integrate to provide elastic data processing at a large scale. RocketMQ can be used as a streaming source and streaming sink in Flink DataStream applications, which is the main implementation and popular usage in RocketMQ community. Developers can ingest data from RocketMQ into a Flink job that makes computations and processes real-time data, to then send the data back to a RocketMQ topic as a streaming sink. More details you could see from [https://github.com/apache/rocketmq-externals/tree/master/rocketmq-flink]. With more and more DW or OLAP engineers using RocketMQ for their data processing work, another potential integration needs arose. Developers can take advantage of as both a streaming source and a streaming table sink for Flink SQL or Table API queries. Also, Flink 1.9.0 makes the Table API a first-class citizen. It's time to support SQL in RocketMQ. This is the topic for Apache RocketMQ connect Flink. h3. You should learn before applying for this topic Apache RocketMQ Flink Connector Apache Flink Table API h3. Extension For some expertise students in the streaming field, you could continue to implements and provides an exactly-once streaming source and at-least-once(or exactly-once)streaming sink, like the issue [#500|https://github.com/apache/rocketmq-externals/issues/500] said. h3. Mentor [duhengfore...@apache.org|mailto:duhengfore...@apache.org], [vongosl...@apache.org|mailto:vongosl...@apache.org] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Created] (COMDEV-343) Apache RocketMQ Connect Hudi
duheng created COMDEV-343: - Summary: Apache RocketMQ Connect Hudi Key: COMDEV-343 URL: https://issues.apache.org/jira/browse/COMDEV-343 Project: Community Development Issue Type: Wish Components: GSoC/Mentoring ideas Reporter: duheng h3. Context Hudi could ingest and manage the storage of large analytical datasets over DFS (hdfs or cloud stores). It can act as either a source or sink for streaming processing platform such as Apache RocketMQ. it also can be used as a state store inside a processing DAG (similar to how rocksDB is used by Flink). This is an item on the roadmap of the Apache RocketMQ. This time, you should implement a fully hudi source and sink based on RocketMQ connect framework, which is a most important implementation of the OpenConnect. h3. You should learn before applying for this topic Apache RocketMQ Connect Framework Apache Hudi . h3. Mentor [vongosl...@apache.org|mailto:vongosl...@apache.org], [duhengfore...@apache.org|mailto:duhengfore...@apache.org] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Created] (COMDEV-344) Apache RocketMQ Ingestion for Druid
duheng created COMDEV-344:
-
Summary: Apache RocketMQ Ingestion for Druid
Key: COMDEV-344
URL: https://issues.apache.org/jira/browse/COMDEV-344
Project: Community Development
Issue Type: Wish
Components: GSoC/Mentoring ideas
Reporter: duheng
h3. Context
Druid is a real-time analytics database designed for fast slice-and-dice
analytics ("OLAP" queries) on large data sets. In this topic, you should
develop the RocketMQ indexing service enables the configuration of supervisors
on the Overlord, which facilitate ingestion from RocketMQ by managing the
creation and lifetime of RocketMQ indexing tasks. These indexing tasks read
events using RocketMQ's own partition and offset mechanism. The supervisor
oversees the state of the indexing tasks to coordinate handoffs, manage
failures, and ensure that the scalability and replication requirements are
maintained.
h3. You should learn before applying for this topic
Apache Druid Data Ingestion
h3. Mentor
[vongosl...@apache.org|mailto:vongosl...@apache.org],
[duhengfore...@apache.org|mailto:duhengfore...@apache.org]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Created] (COMDEV-345) Apache RocketMQ Channel for Knative
duheng created COMDEV-345: - Summary: Apache RocketMQ Channel for Knative Key: COMDEV-345 URL: https://issues.apache.org/jira/browse/COMDEV-345 Project: Community Development Issue Type: Wish Components: GSoC/Mentoring ideas Reporter: duheng h3. Context Knative is a kubernetes based platform for building, deploying and managing modern serverless applications. Knative to provide a set of middleware components that are essential to building modern, source-centric, and container-based applications that can run anywhere: on-premises, in the cloud, or even in a third-party data centre. Knative consists of the Serving and Eventing components. Eventing is a system that is designed to address a common need for cloud-native development and provides composable primitives to enable late-binding event sources and event consumers. Eventing also defines an event forwarding and persistence layer, called a Channel. Each channel is a separate Kubernetes Custom Resource. This topic requires you to implement rocketmqchannel based on Apache RocketMQ. h3. You should learn before applying for this topic How Knative works RocketMQSource for Knative Apache RocketMQ Operator h3. Mentor [wlliqip...@apache.org|mailto:wlliqip...@apache.org], [vongosl...@apache.org|mailto:vongosl...@apache.org] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Created] (COMDEV-346) CloudEvents support for RocketMQ
duheng created COMDEV-346: - Summary: CloudEvents support for RocketMQ Key: COMDEV-346 URL: https://issues.apache.org/jira/browse/COMDEV-346 Project: Community Development Issue Type: Wish Components: GSoC/Mentoring ideas Reporter: duheng h3. Context Events are everywhere. However, event producers tend to describe events differently. The lack of a common way of describing events means developers must constantly re-learn how to consume events. This also limits the potential for libraries, tooling and infrastructure to aide the delivery of event data across environments, like SDKs, event routers or tracing systems. The portability and productivity we can achieve from event data is hindered overall. [CloudEvents|https://github.com/cloudevents] is a specification for describing event data in common formats to provide interoperability across services, platforms and systems. RocketMQ as an event streaming platform, also hopes to improve the interoperability of different event platforms by being compatible with the CloudEvents standard and supporting CloudEvents SDK. In this topic, you need to improve the binding spec. and implement the RocketMQ CloudEvents SDK(Java、Golang or others). h3. You should learn before applying for this topic Apache RocketMQ/Apache RocketMQ SDK/CloudEvents h3. Mentor [duhengfore...@apache.org|mailto:duhengfore...@apache.org], [vongosl...@apache.org|mailto:vongosl...@apache.org] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Created] (COMDEV-347) Apache RocketMQ Schema Registry
duheng created COMDEV-347: - Summary: Apache RocketMQ Schema Registry Key: COMDEV-347 URL: https://issues.apache.org/jira/browse/COMDEV-347 Project: Community Development Issue Type: Wish Components: GSoC/Mentoring ideas Reporter: duheng h3. Content In order to help RocketMQ improve its event management capabilities, and at the same time better decouple the producer and receiver, keep the event forward compatible, so we need a service for event metadata management is called a schema registry. Schema registry will provide a GraphQL interface for developers to define standard schemas for their events, share them across the organization and safely evolve them in a way that is backward compatible and future proof. h3. You should learn before applying for this topic Apache RocketMQ/Apache RocketMQ SDK/ h3. Mentor [duhengfore...@apache.org|mailto:duhengfore...@apache.org], [vongosl...@apache.org|mailto:vongosl...@apache.org] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Created] (COMDEV-348) Apache RocketMQ CLI Admin Tool Developed by Golang
duheng created COMDEV-348: - Summary: Apache RocketMQ CLI Admin Tool Developed by Golang Key: COMDEV-348 URL: https://issues.apache.org/jira/browse/COMDEV-348 Project: Community Development Issue Type: Wish Components: GSoC/Mentoring ideas Reporter: duheng Apache rocketmq provides a cli admin tool developed by Java to querying, managing and diagnosing various problems. At the same time, it also provides a set of API interface, which can be called by Java application program to create, delete, query, message query and other functions. This topic requires the realization of CLI management tool and a set of API interface developed by golang language, through which go application can realize the creation, query and other operations of topic. h3. You should learn before applying for this topic Apache RocketMQ [Apache RocketMQ Go Client|https://github.com/apache/rocketmq-client-go/tree/native] h3. Mentor [wlliqip...@apache.org|mailto:wlliqip...@apache.org], [vongosl...@apache.org|mailto:vongosl...@apache.org] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Created] (COMDEV-349) RocketMQ Connect Elasticsearch
duheng created COMDEV-349: - Summary: RocketMQ Connect Elasticsearch Key: COMDEV-349 URL: https://issues.apache.org/jira/browse/COMDEV-349 Project: Community Development Issue Type: Wish Components: GSoC/Mentoring ideas Reporter: duheng h3. Content The Elasticsearch sink connector allows moving data from Apache RocketMQ to Elasticsearch 6.x, and 7.x. It writes data from a topic in Apache RocketMQ to an index in Elasticsearch and all data for a topic have the same type. [Elasticsearch|https://www.elastic.co/] is often used for text queries, analytics and as an key-value store (use cases). The connector covers both the analytics and key-value store use cases. For the analytics use case, each message is in RocketMQ is treated as an event and the connector uses topic+message queue+offset as a unique identifier for events, which then converted to unique documents in Elasticsearch. For the key-value store use case, it supports using keys from RocketMQ messages as document ids in Elasticsearch and provides configurations ensuring that updates to a key are written to Elasticsearch in order. So, in this project, you need to implement a sink connector based on OpenMessaging connect API, and will executed on RocketMQ connect runtime. h3. You should learn before applying for this topic [Elasticsearch|https://www.elastic.co/]/[Apache RocketMQ|https://rocketmq.apache.org/]/[Apache RocketMQ Connect|https://github.com/apache/rocketmq-externals/tree/master/rocketmq-connect]/ [OpenMessaging Connect API|https://github.com/openmessaging/openmessaging-connect] h3. Mentor [duhengfore...@apache.org|mailto:duhengfore...@apache.org], [vongosl...@apache.org|mailto:vongosl...@apache.org] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Created] (COMDEV-350) RocketMQ Connect IoTDB
duheng created COMDEV-350: - Summary: RocketMQ Connect IoTDB Key: COMDEV-350 URL: https://issues.apache.org/jira/browse/COMDEV-350 Project: Community Development Issue Type: Wish Components: GSoC/Mentoring ideas Reporter: duheng h3. Content The IoTDB sink connector allows moving data from Apache RocketMQ to IoTDB. It writes data from a topic in Apache RocketMQ to IoTDB. [IoTDB|https://iotdb.apache.org/#/] (Internet of Things Database) is a data management system for time series data, which can provide users specific services, such as, data collection, storage and analysis. Due to its lightweight structure, high performance and usable features together with its seamless integration with the Hadoop and Spark ecology, IoTDB meets the requirements of massive dataset storage, high throughput data input and complex data analysis in the industrial IoTDB field. In this project, there are some update operations for historical data, so it is necessary to ensure the sequential transmission and consumption of data via RocketMQ. If there is no update operation in use, then there is no need to guarantee the order of data. IoTDB will process these data which may be disorderly. So, in this project, you need to implement an IoTDB sink connector based on OpenMessaging connect API, and run it on RocketMQ connect runtime. h3. You should learn before applying for this topic [IoTDB|https://iotdb.apache.org/#/]/[Apache RocketMQ|https://rocketmq.apache.org/]/[Apache RocketMQ Connect|https://github.com/apache/rocketmq-externals/tree/master/rocketmq-connect]/ [OpenMessaging Connect API|https://github.com/openmessaging/openmessaging-connect] h3. Mentor [duhengfore...@apache.org|mailto:duhengfore...@apache.org], [wlliqip...@apache.org|mailto:wlliqip...@apache.org], [vongosl...@apache.org|mailto:vongosl...@apache.org] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-345) Apache RocketMQ Channel for Knative
[ https://issues.apache.org/jira/browse/COMDEV-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17041530#comment-17041530 ] Nitish Sharma commented on COMDEV-345: -- Hi Team, A quick introduction about myself, I am Nitish, currently working as Sr software Engineer at RedHat. I work mostly on java and python and hardcore linux admirer. I am an opensource contributor and would like to start contribute to apache. Can you please guide me, how can i assign it to myself ? I am interested in working on it. > Apache RocketMQ Channel for Knative > --- > > Key: COMDEV-345 > URL: https://issues.apache.org/jira/browse/COMDEV-345 > Project: Community Development > Issue Type: Wish > Components: GSoC/Mentoring ideas >Reporter: duheng >Priority: Major > Labels: RocketMQ, gsoc2020 > > h3. Context > Knative is a kubernetes based platform for building, deploying and managing > modern serverless applications. Knative to provide a set of middleware > components that are essential to building modern, source-centric, and > container-based applications that can run anywhere: on-premises, in the > cloud, or even in a third-party data centre. Knative consists of the Serving > and Eventing components. Eventing is a system that is designed to address a > common need for cloud-native development and provides composable primitives > to enable late-binding event sources and event consumers. Eventing also > defines an event forwarding and persistence layer, called a Channel. Each > channel is a separate Kubernetes Custom Resource. This topic requires you to > implement rocketmqchannel based on Apache RocketMQ. > h3. You should learn before applying for this topic > How Knative works > RocketMQSource for Knative > Apache RocketMQ Operator > h3. Mentor > [wlliqip...@apache.org|mailto:wlliqip...@apache.org], > [vongosl...@apache.org|mailto:vongosl...@apache.org] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Created] (COMDEV-351) The Operator for RocketMQ Exporter
duheng created COMDEV-351: - Summary: The Operator for RocketMQ Exporter Key: COMDEV-351 URL: https://issues.apache.org/jira/browse/COMDEV-351 Project: Community Development Issue Type: Wish Reporter: duheng he exporter exposes the endpoint of monitoring data collection to Prometheus server in the form of HTTP service. Prometheus server can obtain the monitoring data to be collected by accessing the endpoint endpoint provided by the exporter. [RocketMQ exporter |https://github.com/apache/rocketmq-exporter]is such an exporter. It first collects data from rocketmq cluster, and then normalizes the collected data to meet the requirements of Prometheus system with the help of the third-party client library provided by Prometheus. Prometheus regularly pulls data from the exporter. This topic needs to implement an operator of rocketmq exporter to facilitate the deployment of the exporter in kubenetes platform. h3. You should learn before applying for this topic [RocketMQ-Exporter Repo|https://github.com/apache/rocketmq-exporter] [RocketMQ-Exporter Overview|https://www.infoq.cn/article/NcSYj_2PQhBlqveuD1Kw?utm_source=related_read&utm_medium=article] [Kubetenes Operator|https://github.com/operator-framework/] [RocketMQ-Operator|https://github.com/apache/rocketmq-operator] h3. Mentor [wlliqip...@apache.org|mailto:wlliqip...@apache.org], [vongosl...@apache.org|mailto:vongosl...@apache.org] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Created] (COMDEV-353) RocketMQ Connect Cassandra
duheng created COMDEV-353: - Summary: RocketMQ Connect Cassandra Key: COMDEV-353 URL: https://issues.apache.org/jira/browse/COMDEV-353 Project: Community Development Issue Type: Wish Components: GSoC/Mentoring ideas Reporter: duheng |h3. Content The Cassandra sink connector allows writing data to Apache Cassandra. In this project, you need to implement a Cassandra sink connector based on OpenMessaging connect API, and run it on RocketMQ connect runtimeh3. You should learn before applying for this topic [Cassandra|http://cassandra.apache.org/]/[Apache RocketMQ|https://rocketmq.apache.org/]/[Apache RocketMQ Connect|https://github.com/apache/rocketmq-externals/tree/master/rocketmq-connect]/ [OpenMessaging Connect API|https://github.com/openmessaging/openmessaging-connect]h3. Mentor [duhengfore...@apache.org|mailto:duhengfore...@apache.org], [vongosl...@apache.org|mailto:vongosl...@apache.org]| -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Created] (COMDEV-352) RocketMQ Connect InfluxDB
duheng created COMDEV-352: - Summary: RocketMQ Connect InfluxDB Key: COMDEV-352 URL: https://issues.apache.org/jira/browse/COMDEV-352 Project: Community Development Issue Type: Wish Components: GSoC/Mentoring ideas Reporter: duheng h3. Content The InfluxDB sink connector allows moving data from Apache RocketMQ to InfluxDB. It writes data from a topic in Apache RocketMQ to InfluxDB. While The InfluxDB source connector is used to export data from InfluxDB Server to RocketMQ. In this project, you need to implement an InfluxDB sink connector(source connector is optional) based on OpenMessaging connect API. h3. You should learn before applying for this topic [InfluxDB|https://github.com/influxdata/influxdb]/[Apache RocketMQ|https://rocketmq.apache.org/]/[Apache RocketMQ Connect|https://github.com/apache/rocketmq-externals/tree/master/rocketmq-connect]/ [OpenMessaging Connect API|https://github.com/openmessaging/openmessaging-connect] h3. Mentor [duhengfore...@apache.org|mailto:duhengfore...@apache.org], [wlliqip...@apache.org|mailto:wlliqip...@apache.org], [vongosl...@apache.org|mailto:vongosl...@apache.org] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-305) GSoC2019 Apache RocketMQ Connector Project
[ https://issues.apache.org/jira/browse/COMDEV-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17041535#comment-17041535 ] Von Gosling commented on COMDEV-305: This can be turned off. > GSoC2019 Apache RocketMQ Connector Project > -- > > Key: COMDEV-305 > URL: https://issues.apache.org/jira/browse/COMDEV-305 > Project: Community Development > Issue Type: Wish > Components: GSoC/Mentoring ideas >Reporter: duheng >Priority: Major > Labels: GSoC2019, RocketMQ > > This is a project idea for [Google Summer of > Code|https://summerofcode.withgoogle.com/] (GSOC). > We would like to extend the data replicator capabilities adding MongoDB / > GridFS/Spark etc. as a new output connector for importing contents from one > or more repositories supported by Apache RocketMQ. In this way, we will help > developers on migrating contents from different data sources on different > data system or computing system. > You will be involved in the development of the following tasks, you will > learn how to: > * Write the RocketMQ connector implementation > * Implement unit tests > * Build all the integration tests for testing the connector inside the > framework > * Write the documentation for this connector > Prospective GSOC mentor: vongosl...@apache.org -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Comment Edited] (COMDEV-305) GSoC2019 Apache RocketMQ Connector Project
[ https://issues.apache.org/jira/browse/COMDEV-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17041535#comment-17041535 ] Von Gosling edited comment on COMDEV-305 at 2/21/20 4:15 AM: - This can be closed. RocketMQ community is preparing the GSoC 2020 topics, welcome to have a try :-) was (Author: vongosling): This can be turned off. > GSoC2019 Apache RocketMQ Connector Project > -- > > Key: COMDEV-305 > URL: https://issues.apache.org/jira/browse/COMDEV-305 > Project: Community Development > Issue Type: Wish > Components: GSoC/Mentoring ideas >Reporter: duheng >Priority: Major > Labels: GSoC2019, RocketMQ > > This is a project idea for [Google Summer of > Code|https://summerofcode.withgoogle.com/] (GSOC). > We would like to extend the data replicator capabilities adding MongoDB / > GridFS/Spark etc. as a new output connector for importing contents from one > or more repositories supported by Apache RocketMQ. In this way, we will help > developers on migrating contents from different data sources on different > data system or computing system. > You will be involved in the development of the following tasks, you will > learn how to: > * Write the RocketMQ connector implementation > * Implement unit tests > * Build all the integration tests for testing the connector inside the > framework > * Write the documentation for this connector > Prospective GSOC mentor: vongosl...@apache.org -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-305) GSoC2019 Apache RocketMQ Connector Project
[ https://issues.apache.org/jira/browse/COMDEV-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] duheng closed COMDEV-305. - Resolution: Fixed > GSoC2019 Apache RocketMQ Connector Project > -- > > Key: COMDEV-305 > URL: https://issues.apache.org/jira/browse/COMDEV-305 > Project: Community Development > Issue Type: Wish > Components: GSoC/Mentoring ideas >Reporter: duheng >Priority: Major > Labels: GSoC2019, RocketMQ > > This is a project idea for [Google Summer of > Code|https://summerofcode.withgoogle.com/] (GSOC). > We would like to extend the data replicator capabilities adding MongoDB / > GridFS/Spark etc. as a new output connector for importing contents from one > or more repositories supported by Apache RocketMQ. In this way, we will help > developers on migrating contents from different data sources on different > data system or computing system. > You will be involved in the development of the following tasks, you will > learn how to: > * Write the RocketMQ connector implementation > * Implement unit tests > * Build all the integration tests for testing the connector inside the > framework > * Write the documentation for this connector > Prospective GSOC mentor: vongosl...@apache.org -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Updated] (COMDEV-342) Apache RocketMQ Connect Flink
[ https://issues.apache.org/jira/browse/COMDEV-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] duheng updated COMDEV-342: -- Description: h3. Context There are many ways that Apache Flink and Apache RocketMQ can integrate to provide elastic data processing at a large scale. RocketMQ can be used as a streaming source and streaming sink in Flink DataStream applications, which is the main implementation and popular usage in RocketMQ community. Developers can ingest data from RocketMQ into a Flink job that makes computations and processes real-time data, to then send the data back to a RocketMQ topic as a streaming sink. More details you could see from [https://github.com/apache/rocketmq-externals/tree/master/rocketmq-flink]. With more and more DW or OLAP engineers using RocketMQ for their data processing work, another potential integration needs arose. Developers can take advantage of as both a streaming source and a streaming table sink for Flink SQL or Table API queries. Also, Flink 1.9.0 makes the Table API a first-class citizen. It's time to support SQL in RocketMQ. This is the topic for Apache RocketMQ connect Flink. h3. You should learn before applying for this topic Apache RocketMQ Flink Connector Apache Flink Table API h3. Extension For some expertise students in the streaming field, you could continue to implements and provides an exactly-once streaming source and at-least-once(or exactly-once)streaming sink, like the issue [#500|https://github.com/apache/rocketmq-externals/issues/500] said. h3. Mentor [|mailto:duhengfore...@apache.org] [nicholasji...@apache.org|mailto:nicholasji...@apache.org] [, duhengfore...@apache.org|mailto:duhengfore...@apache.org], [vongosl...@apache.org|mailto:vongosl...@apache.org] was: h3. Context There are many ways that Apache Flink and Apache RocketMQ can integrate to provide elastic data processing at a large scale. RocketMQ can be used as a streaming source and streaming sink in Flink DataStream applications, which is the main implementation and popular usage in RocketMQ community. Developers can ingest data from RocketMQ into a Flink job that makes computations and processes real-time data, to then send the data back to a RocketMQ topic as a streaming sink. More details you could see from [https://github.com/apache/rocketmq-externals/tree/master/rocketmq-flink]. With more and more DW or OLAP engineers using RocketMQ for their data processing work, another potential integration needs arose. Developers can take advantage of as both a streaming source and a streaming table sink for Flink SQL or Table API queries. Also, Flink 1.9.0 makes the Table API a first-class citizen. It's time to support SQL in RocketMQ. This is the topic for Apache RocketMQ connect Flink. h3. You should learn before applying for this topic Apache RocketMQ Flink Connector Apache Flink Table API h3. Extension For some expertise students in the streaming field, you could continue to implements and provides an exactly-once streaming source and at-least-once(or exactly-once)streaming sink, like the issue [#500|https://github.com/apache/rocketmq-externals/issues/500] said. h3. Mentor [duhengfore...@apache.org|mailto:duhengfore...@apache.org], [vongosl...@apache.org|mailto:vongosl...@apache.org] > Apache RocketMQ Connect Flink > - > > Key: COMDEV-342 > URL: https://issues.apache.org/jira/browse/COMDEV-342 > Project: Community Development > Issue Type: Wish > Components: GSoC/Mentoring ideas >Reporter: duheng >Priority: Major > Labels: RocketMQ, gsoc2020 > > h3. Context > There are many ways that Apache Flink and Apache RocketMQ can integrate to > provide elastic data processing at a large scale. RocketMQ can be used as a > streaming source and streaming sink in Flink DataStream applications, which > is the main implementation and popular usage in RocketMQ community. > Developers can ingest data from RocketMQ into a Flink job that makes > computations and processes real-time data, to then send the data back to a > RocketMQ topic as a streaming sink. More details you could see from > [https://github.com/apache/rocketmq-externals/tree/master/rocketmq-flink]. > With more and more DW or OLAP engineers using RocketMQ for their data > processing work, another potential integration needs arose. Developers can > take advantage of as both a streaming source and a streaming table sink for > Flink SQL or Table API queries. Also, Flink 1.9.0 makes the Table API a > first-class citizen. It's time to support SQL in RocketMQ. This is the topic > for Apache RocketMQ connect Flink. > h3. You should learn before applying for this topic > Apache RocketMQ Flink Connector > Apache Flink Table API > h3. Extension > For some expertise students in the streaming field, you could
[jira] [Updated] (COMDEV-342) Apache RocketMQ Connect Flink
[ https://issues.apache.org/jira/browse/COMDEV-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] duheng updated COMDEV-342: -- Description: h3. Context There are many ways that Apache Flink and Apache RocketMQ can integrate to provide elastic data processing at a large scale. RocketMQ can be used as a streaming source and streaming sink in Flink DataStream applications, which is the main implementation and popular usage in RocketMQ community. Developers can ingest data from RocketMQ into a Flink job that makes computations and processes real-time data, to then send the data back to a RocketMQ topic as a streaming sink. More details you could see from [https://github.com/apache/rocketmq-externals/tree/master/rocketmq-flink]. With more and more DW or OLAP engineers using RocketMQ for their data processing work, another potential integration needs arose. Developers can take advantage of as both a streaming source and a streaming table sink for Flink SQL or Table API queries. Also, Flink 1.9.0 makes the Table API a first-class citizen. It's time to support SQL in RocketMQ. This is the topic for Apache RocketMQ connect Flink. h3. You should learn before applying for this topic Apache RocketMQ Flink Connector Apache Flink Table API h3. Extension For some expertise students in the streaming field, you could continue to implements and provides an exactly-once streaming source and at-least-once(or exactly-once)streaming sink, like the issue [#500|https://github.com/apache/rocketmq-externals/issues/500] said. h3. Mentor [nicholasji...@apache.org|mailto:nicholasji...@apache.org] [, duhengfore...@apache.org|mailto:duhengfore...@apache.org], [vongosl...@apache.org|mailto:vongosl...@apache.org] was: h3. Context There are many ways that Apache Flink and Apache RocketMQ can integrate to provide elastic data processing at a large scale. RocketMQ can be used as a streaming source and streaming sink in Flink DataStream applications, which is the main implementation and popular usage in RocketMQ community. Developers can ingest data from RocketMQ into a Flink job that makes computations and processes real-time data, to then send the data back to a RocketMQ topic as a streaming sink. More details you could see from [https://github.com/apache/rocketmq-externals/tree/master/rocketmq-flink]. With more and more DW or OLAP engineers using RocketMQ for their data processing work, another potential integration needs arose. Developers can take advantage of as both a streaming source and a streaming table sink for Flink SQL or Table API queries. Also, Flink 1.9.0 makes the Table API a first-class citizen. It's time to support SQL in RocketMQ. This is the topic for Apache RocketMQ connect Flink. h3. You should learn before applying for this topic Apache RocketMQ Flink Connector Apache Flink Table API h3. Extension For some expertise students in the streaming field, you could continue to implements and provides an exactly-once streaming source and at-least-once(or exactly-once)streaming sink, like the issue [#500|https://github.com/apache/rocketmq-externals/issues/500] said. h3. Mentor [|mailto:duhengfore...@apache.org] [nicholasji...@apache.org|mailto:nicholasji...@apache.org] [, duhengfore...@apache.org|mailto:duhengfore...@apache.org], [vongosl...@apache.org|mailto:vongosl...@apache.org] > Apache RocketMQ Connect Flink > - > > Key: COMDEV-342 > URL: https://issues.apache.org/jira/browse/COMDEV-342 > Project: Community Development > Issue Type: Wish > Components: GSoC/Mentoring ideas >Reporter: duheng >Priority: Major > Labels: RocketMQ, gsoc2020 > > h3. Context > There are many ways that Apache Flink and Apache RocketMQ can integrate to > provide elastic data processing at a large scale. RocketMQ can be used as a > streaming source and streaming sink in Flink DataStream applications, which > is the main implementation and popular usage in RocketMQ community. > Developers can ingest data from RocketMQ into a Flink job that makes > computations and processes real-time data, to then send the data back to a > RocketMQ topic as a streaming sink. More details you could see from > [https://github.com/apache/rocketmq-externals/tree/master/rocketmq-flink]. > With more and more DW or OLAP engineers using RocketMQ for their data > processing work, another potential integration needs arose. Developers can > take advantage of as both a streaming source and a streaming table sink for > Flink SQL or Table API queries. Also, Flink 1.9.0 makes the Table API a > first-class citizen. It's time to support SQL in RocketMQ. This is the topic > for Apache RocketMQ connect Flink. > h3. You should learn before applying for this topic > Apache RocketMQ Flink Connector > Apache Flink Table API > h3. Extension
