Build failed in Jenkins: beam_Release_NightlySnapshot #321

See Changes: [kirpichov] [BEAM-65] ProcessFn: support setup/teardown [klk] Remove extraneous chunking from GroupAlsoByWindowsViaOutputBufferDoFn [klk] Autoformat GroupAlsoByWindowsViaOutputBufferDoFn [klk] Remove

Re: Beam connector development for Hive as a data source

Hi Madhu, Welcome! I suggest subscribing to the dev@ mailing list and using the same email address when sending to the list, to avoid your email being caught in moderation. It would be great to have a connector for Apache Hive. Keep in mind that several folks have expressed interest in using and

Beam connector development for Hive as a data source

Hello, I am Big Data Architect working at eTouch Systems. We are GCP partners. We are planning to contribute to Beam by developing a connector for Apache Hive as a data source. I understand that before any development work begins, we need to submit our design to Beam community. I would like to

Report to the Board, February 2017 edition

We are expected to submit a project report to the ASF Board of Directors ahead of its next meeting. The report is due on Wednesday, 2/8. This is the second is the series of three monthly reports required for new projects. We'll need to report next month as well. If interested, please take a look

Re: BEAM-307(KafkaIO on Kafka 0.10)

This would be a great contribution, Mingmin! As a general rule, we'd like the connector to work with as many versions as possible, with as little code duplication as possible. Slightly orthogonal -- BigtableIO [1] is an example of a connector that separates API portions from the underlying

Re: BEAM-307(KafkaIO on Kafka 0.10)

I see. kafka-clients dependency could also be in 'provided' scope so that is simpler to use different versions at runtime. On Mon, Feb 6, 2017 at 12:05 PM, Xu Mingmin wrote: > The one I meet is external authentication added in 0.10, we use a > standalone token-based security

Re: BEAM-307(KafkaIO on Kafka 0.10)

Current KafkaIO works just fine with Kafka 0.10. I don't know of any incompatibilities or regressions. It does not take advantage of message timestamps, of course. It would be good to take handle tme in in a backward compatible way.. it might be required anyway if they are optional in 0.10. Not

Re: [VOTE] Apache Beam, version 0.5.0, release candidate #2

This vote is now complete. I'll summarize the results and next steps in a separate thread. On Mon, Feb 6, 2017 at 2:51 AM, Sergio Fernández wrote: > +1 (non-binding) > > So far I've successfully checked: > * signatures and digests > * source releases file layouts > * no