Hi Kenneth!
But even the tag v2.5.0 points to SNAPSHOT version for Maven:
https://github.com/apache/beam/blob/v2.5.0/pom.xml#L37
The same file in v2.4.0:
https://github.com/apache/beam/blob/v2.4.0/pom.xml#L37
I am looking to publish v2.5.0 artifacts via maven to a private
artifactory, and
What you have pointed to is the tip of the release-2.5.0 branch. The gradle
release plugin copies the maven release plugin. So it has rolled back the
version change so the branch is always at a snapshot version.
The commit before that is tag v2.5.0 and that is the final tag. Here is the
gradle
I take that back - misclicked on 0.5.0 (which has a correct tag).
On Wed, Jul 17, 2019 at 3:34 PM Kenneth Knowles wrote:
> Looks like it is this:
> https://github.com/apache/beam/tree/4838ae16c172252bc0a15e3a984e085f82e25c2d
>
> I believe the release manager created the tag to point to the tip
Looks like it is this:
https://github.com/apache/beam/tree/4838ae16c172252bc0a15e3a984e085f82e25c2d
I believe the release manager created the tag to point to the tip of the
release branch after the maven release plugin rolled that change back (this
is how the maven release plugin works since it
Hi!
Why is v2.5.0 tag for Beam 2.5.0 release SNAPSHOT version here?
https://github.com/apache/beam/blob/v2.5.0/pom.xml#L37
https://github.com/apache/beam/blob/release-2.5.0/gradle.properties#L25
Please let me know where to find final release 2.5.0 commit.
Thanks, Pablo! Looking forward to it! Hopefully, it will also be recorded
as well.
On Wed, Jul 17, 2019 at 2:50 PM Pablo Estrada wrote:
> Yes! So I will be working on a small feature request for Java's
> BigQueryIO: https://issues.apache.org/jira/browse/BEAM-7607
>
> Maybe I'll do something for
Yes! So I will be working on a small feature request for Java's BigQueryIO:
https://issues.apache.org/jira/browse/BEAM-7607
Maybe I'll do something for Python next month. : )
Best
-P.
On Wed, Jul 17, 2019 at 12:32 PM Rakesh Kumar wrote:
> +1, I really appreciate this initiative. It would be
I think full-blown SDF is not needed for this - someone just needs to
implement a MongoDbIO.readAll() variant, using a composite transform. The
regular pattern for this sort of thing will do (ParDo split, reshuffle,
ParDo read).
Whether it's worth replacing MongoDbIO.read() with a redirect to
Hello! To clarify, you want to do something like this?
PubSubIO.read() -> extract mongodb collection and range ->
MongoDbIO.read(collection, range) -> ...
If I'm not mistaken, it isn't possible with the implementation of MongoDbIO
(based on BoundedSource interface, requiring the collection to
