[jira] [Commented] (BEAM-3788) Implement a Kafka IO for Python SDK
[ https://issues.apache.org/jira/browse/BEAM-3788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16859396#comment-16859396 ] Willem Pienaar commented on BEAM-3788: -- [~chamikara]:Is there anything still blocking this from being implemented? Might have some time over the next few weeks. > Implement a Kafka IO for Python SDK > --- > > Key: BEAM-3788 > URL: https://issues.apache.org/jira/browse/BEAM-3788 > Project: Beam > Issue Type: New Feature > Components: sdk-py-core >Reporter: Chamikara Jayalath >Assignee: Chamikara Jayalath >Priority: Major > > This will be implemented using the Splittable DoFn framework. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (BEAM-7519) Improve work with SSL/TLS certificates in SDK IO, for Google Dataflow
Oleksandr Priadko created BEAM-7519: --- Summary: Improve work with SSL/TLS certificates in SDK IO, for Google Dataflow Key: BEAM-7519 URL: https://issues.apache.org/jira/browse/BEAM-7519 Project: Beam Issue Type: Wish Components: io-ideas, io-java-elasticsearch, io-java-gcp, io-java-kafka Reporter: Oleksandr Priadko Sinks like Kafka or Elasticsearch have worked with SSL/TLS. But all of these can read only certificates from a local machine (use java.io.File#File(java.lang.String). In the case of Google Dataflow, we can not easily copy files to a worker, I see two possible variants to read certificates from the worker: 1) somehow copy certificates to a worker from GC Storage 2) in Kafka IO or Elasticsearch IO read certificates directly from GC Storage Any thoughts about how I can solve this issue easily or mb other variants will be helpful. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (BEAM-6441) cut_release_branch.sh should not push to master without verification and a PR
[ https://issues.apache.org/jira/browse/BEAM-6441?focusedWorklogId=256529&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-256529 ] ASF GitHub Bot logged work on BEAM-6441: Author: ASF GitHub Bot Created on: 09/Jun/19 18:26 Start Date: 09/Jun/19 18:26 Worklog Time Spent: 10m Work Description: stale[bot] commented on issue #8223: [BEAM-6441] Revise release branch cut instructions URL: https://github.com/apache/beam/pull/8223#issuecomment-500234400 This pull request has been marked as stale due to 60 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that’s incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the PR at any time and @mention a reviewer or discuss it on the d...@beam.apache.org list. Thank you for your contributions. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 256529) Time Spent: 2h (was: 1h 50m) > cut_release_branch.sh should not push to master without verification and a PR > - > > Key: BEAM-6441 > URL: https://issues.apache.org/jira/browse/BEAM-6441 > Project: Beam > Issue Type: Bug > Components: build-system >Reporter: Kenneth Knowles >Assignee: Kenneth Knowles >Priority: Major > Time Spent: 2h > Remaining Estimate: 0h > > Currently, the cut_release_branch.sh does many things: > - Edits files in place to update the version > - Makes a local commit > - Pushing the local commit to master > - Creates a new branch > - Edits files in place to update the version > - Pushes the release branch > I think all of this except the push to master are OK. It is possible that we > have something - website, examples, new places where the version is > hardcoded, etc, that get broken in this process. Moving from x-SNAPSHOT to > (x+1)-SNAPSHOT is easy to do in a pull request and safe. The release branch > creation does not need to be synchronized with this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (BEAM-7456) Expand Link next to tables in capability matrix hard to see
[ https://issues.apache.org/jira/browse/BEAM-7456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reza ardeshir rokni reassigned BEAM-7456: - Assignee: Reza ardeshir rokni > Expand Link next to tables in capability matrix hard to see > --- > > Key: BEAM-7456 > URL: https://issues.apache.org/jira/browse/BEAM-7456 > Project: Beam > Issue Type: Improvement > Components: website >Reporter: Reza ardeshir rokni >Assignee: Reza ardeshir rokni >Priority: Trivial > Time Spent: 40m > Remaining Estimate: 0h > > Expand Link next to tables in capability matrix hard to see. Would be great > to make it easier to see that it is a clickable link. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (BEAM-7456) Expand Link next to tables in capability matrix hard to see
[ https://issues.apache.org/jira/browse/BEAM-7456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reza ardeshir rokni resolved BEAM-7456. --- Resolution: Fixed Fix Version/s: 2.13.0 PR #8773 > Expand Link next to tables in capability matrix hard to see > --- > > Key: BEAM-7456 > URL: https://issues.apache.org/jira/browse/BEAM-7456 > Project: Beam > Issue Type: Improvement > Components: website >Reporter: Reza ardeshir rokni >Assignee: Reza ardeshir rokni >Priority: Trivial > Fix For: 2.13.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Expand Link next to tables in capability matrix hard to see. Would be great > to make it easier to see that it is a clickable link. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (BEAM-6693) ApproximateUnique transform for Python SDK
[ https://issues.apache.org/jira/browse/BEAM-6693?focusedWorklogId=256629&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-256629 ] ASF GitHub Bot logged work on BEAM-6693: Author: ASF GitHub Bot Created on: 10/Jun/19 04:51 Start Date: 10/Jun/19 04:51 Worklog Time Spent: 10m Work Description: Hannah-Jiang commented on issue #8799: [BEAM-6693] replace mmh3 with default hash function URL: https://github.com/apache/beam/pull/8799#issuecomment-500290859 R: @pabloem This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 256629) Time Spent: 11.5h (was: 11h 20m) > ApproximateUnique transform for Python SDK > -- > > Key: BEAM-6693 > URL: https://issues.apache.org/jira/browse/BEAM-6693 > Project: Beam > Issue Type: New Feature > Components: sdk-py-core >Reporter: Ahmet Altay >Assignee: Hannah Jiang >Priority: Minor > Fix For: 2.14.0 > > Time Spent: 11.5h > Remaining Estimate: 0h > > Add a PTransform for estimating the number of distinct elements in a > PCollection and the number of distinct values associated with each key in a > PCollection KVs. > it should offer the same API as its Java counterpart: > https://github.com/apache/beam/blob/11a977b8b26eff2274d706541127c19dc93131a2/sdks/java/core/src/main/java/org/apache/beam/sdk/transforms/ApproximateUnique.java -- This message was sent by Atlassian JIRA (v7.6.3#76005)
