[jira] [Work logged] (BEAM-313) Enable the use of an existing spark context with the SparkPipelineRunner

[ASF GitHub Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-313?focusedWorklogId=138312&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-138312
 ]

ASF GitHub Bot logged work on BEAM-313:
---

Author: ASF GitHub Bot
Created on: 27/Aug/18 08:02
Start Date: 27/Aug/18 08:02
Worklog Time Spent: 10m 
  Work Description: kohlerm commented on issue #401: [BEAM-313] Enable the 
use of an existing spark context with the SparkPipelineRunner
URL: https://github.com/apache/beam/pull/401#issuecomment-416147962
 
 
   Thanks for the quick replies!
   @iemejia  @jbonofre @amitsela  
   All I want to do is to use Beam on top of spark and use the SJS to start it, 
because the Spark cluster I have access to only allows starting jobs with SJS.  
   Is there a code snippet somewhere , how to do this (if it's possible at all)?
   
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on 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: 138312)
Time Spent: 40m  (was: 0.5h)

> Enable the use of an existing spark context with the SparkPipelineRunner
> 
>
> Key: BEAM-313
> URL: https://issues.apache.org/jira/browse/BEAM-313
> Project: Beam
>  Issue Type: New Feature
>  Components: runner-spark
>Reporter: Abbass Marouni
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 0.3.0-incubating
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> The general use case is that the SparkPipelineRunner creates its own Spark 
> context and uses it for the pipeline execution.
> Another alternative is to provide the SparkPipelineRunner with an existing 
> spark context. This can be interesting for a lot of use cases where the Spark 
> context is managed outside of beam (context reuse, advanced context 
> management, spark job server, ...).
> code sample : 
> https://github.com/amarouni/incubator-beam/commit/fe0bb517bf0ccde07ef5a61f3e44df695b75f076



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Work logged] (BEAM-3310) Push metrics to a backend in an runner agnostic way

[ASF GitHub Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-3310?focusedWorklogId=138316&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-138316
 ]

ASF GitHub Bot logged work on BEAM-3310:


Author: ASF GitHub Bot
Created on: 27/Aug/18 08:14
Start Date: 27/Aug/18 08:14
Worklog Time Spent: 10m 
  Work Description: echauchot commented on issue #4548: [BEAM-3310] Metrics 
pusher
URL: https://github.com/apache/beam/pull/4548#issuecomment-416150665
 
 
   @JozoVilcek is correct: Beam metrics are reported to flink metrics cf my 
comment above (same as the code line sent by @JozoVilcek)


This is an automated message from the Apache Git Service.
To respond to the message, please log on 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: 138316)
Time Spent: 17h 50m  (was: 17h 40m)

> Push metrics to a backend in an runner agnostic way
> ---
>
> Key: BEAM-3310
> URL: https://issues.apache.org/jira/browse/BEAM-3310
> Project: Beam
>  Issue Type: New Feature
>  Components: runner-extensions-metrics, sdk-java-core
>Reporter: Etienne Chauchot
>Assignee: Etienne Chauchot
>Priority: Major
>  Time Spent: 17h 50m
>  Remaining Estimate: 0h
>
> The idea is to avoid relying on the runners to provide access to the metrics 
> (either at the end of the pipeline or while it runs) because they don't have 
> all the same capabilities towards metrics (e.g. spark runner configures sinks 
>  like csv, graphite or in memory sinks using the spark engine conf). The 
> target is to push the metrics in the common runner code so that no matter the 
> chosen runner, a user can get his metrics out of beam.
> Here is the link to the discussion thread on the dev ML: 
> https://lists.apache.org/thread.html/01a80d62f2df6b84bfa41f05e15fda900178f882877c294fed8be91e@%3Cdev.beam.apache.org%3E
> And the design doc:
> https://s.apache.org/runner_independent_metrics_extraction



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Work logged] (BEAM-313) Enable the use of an existing spark context with the SparkPipelineRunner

[ASF GitHub Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-313?focusedWorklogId=138318&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-138318
 ]

ASF GitHub Bot logged work on BEAM-313:
---

Author: ASF GitHub Bot
Created on: 27/Aug/18 08:15
Start Date: 27/Aug/18 08:15
Worklog Time Spent: 10m 
  Work Description: kohlerm edited a comment on issue #401: [BEAM-313] 
Enable the use of an existing spark context with the SparkPipelineRunner
URL: https://github.com/apache/beam/pull/401#issuecomment-416147962
 
 
   Thanks for the quick replies!
   @iemejia  @jbonofre @amitsela  
   All I want to do is to use Beam on top of spark and use the SJS to start it, 
because the Spark cluster I have access to only allows starting jobs with SJS.  
   Is there a code (Java) snippet somewhere , how to do this (if it's possible 
at all)?
   Sorry for my ignorance, but I'm neither a Spark nor a Beam expert yet. 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on 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: 138318)
Time Spent: 50m  (was: 40m)

> Enable the use of an existing spark context with the SparkPipelineRunner
> 
>
> Key: BEAM-313
> URL: https://issues.apache.org/jira/browse/BEAM-313
> Project: Beam
>  Issue Type: New Feature
>  Components: runner-spark
>Reporter: Abbass Marouni
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 0.3.0-incubating
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> The general use case is that the SparkPipelineRunner creates its own Spark 
> context and uses it for the pipeline execution.
> Another alternative is to provide the SparkPipelineRunner with an existing 
> spark context. This can be interesting for a lot of use cases where the Spark 
> context is managed outside of beam (context reuse, advanced context 
> management, spark job server, ...).
> code sample : 
> https://github.com/amarouni/incubator-beam/commit/fe0bb517bf0ccde07ef5a61f3e44df695b75f076



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Work logged] (BEAM-313) Enable the use of an existing spark context with the SparkPipelineRunner

[ASF GitHub Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-313?focusedWorklogId=138319&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-138319
 ]

ASF GitHub Bot logged work on BEAM-313:
---

Author: ASF GitHub Bot
Created on: 27/Aug/18 08:15
Start Date: 27/Aug/18 08:15
Worklog Time Spent: 10m 
  Work Description: kohlerm edited a comment on issue #401: [BEAM-313] 
Enable the use of an existing spark context with the SparkPipelineRunner
URL: https://github.com/apache/beam/pull/401#issuecomment-416147962
 
 
   Thanks for the quick replies!
   @iemejia  @jbonofre @amitsela  
   All I want to do is to use Beam on top of spark and use the SJS to start it, 
because the Spark cluster I have access to only allows starting jobs with SJS.  
   Is there a code (Java) snippet somewhere , how to do this (if it's possible 
at all)?
   Sorry for my ignorance, but I'm neither a Spark nor a Beam expert yet. 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on 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: 138319)
Time Spent: 1h  (was: 50m)

> Enable the use of an existing spark context with the SparkPipelineRunner
> 
>
> Key: BEAM-313
> URL: https://issues.apache.org/jira/browse/BEAM-313
> Project: Beam
>  Issue Type: New Feature
>  Components: runner-spark
>Reporter: Abbass Marouni
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 0.3.0-incubating
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> The general use case is that the SparkPipelineRunner creates its own Spark 
> context and uses it for the pipeline execution.
> Another alternative is to provide the SparkPipelineRunner with an existing 
> spark context. This can be interesting for a lot of use cases where the Spark 
> context is managed outside of beam (context reuse, advanced context 
> management, spark job server, ...).
> code sample : 
> https://github.com/amarouni/incubator-beam/commit/fe0bb517bf0ccde07ef5a61f3e44df695b75f076



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Work logged] (BEAM-3310) Push metrics to a backend in an runner agnostic way

[ASF GitHub Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-3310?focusedWorklogId=138317&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-138317
 ]

ASF GitHub Bot logged work on BEAM-3310:


Author: ASF GitHub Bot
Created on: 27/Aug/18 08:15
Start Date: 27/Aug/18 08:15
Worklog Time Spent: 10m 
  Work Description: echauchot edited a comment on issue #4548: [BEAM-3310] 
Metrics pusher
URL: https://github.com/apache/beam/pull/4548#issuecomment-416150665
 
 
   @JozoVilcek is correct: Beam metrics are reported to flink metrics cf my 
comment above (@JozoVilcek re-sent the link)


This is an automated message from the Apache Git Service.
To respond to the message, please log on 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: 138317)
Time Spent: 18h  (was: 17h 50m)

> Push metrics to a backend in an runner agnostic way
> ---
>
> Key: BEAM-3310
> URL: https://issues.apache.org/jira/browse/BEAM-3310
> Project: Beam
>  Issue Type: New Feature
>  Components: runner-extensions-metrics, sdk-java-core
>Reporter: Etienne Chauchot
>Assignee: Etienne Chauchot
>Priority: Major
>  Time Spent: 18h
>  Remaining Estimate: 0h
>
> The idea is to avoid relying on the runners to provide access to the metrics 
> (either at the end of the pipeline or while it runs) because they don't have 
> all the same capabilities towards metrics (e.g. spark runner configures sinks 
>  like csv, graphite or in memory sinks using the spark engine conf). The 
> target is to push the metrics in the common runner code so that no matter the 
> chosen runner, a user can get his metrics out of beam.
> Here is the link to the discussion thread on the dev ML: 
> https://lists.apache.org/thread.html/01a80d62f2df6b84bfa41f05e15fda900178f882877c294fed8be91e@%3Cdev.beam.apache.org%3E
> And the design doc:
> https://s.apache.org/runner_independent_metrics_extraction



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (BEAM-5171) org.apache.beam.sdk.io.CountingSourceTest.test[Un]boundedSourceSplits tests are flaky in Spark runner

[Etienne Chauchot (JIRA)]

[ 
https://issues.apache.org/jira/browse/BEAM-5171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16593293#comment-16593293
 ] 

Etienne Chauchot commented on BEAM-5171:


[~apilloud] Several tests that fail to write to /tmp on jenkins. Definitely a 
jenkins issue IMHO.

> org.apache.beam.sdk.io.CountingSourceTest.test[Un]boundedSourceSplits tests 
> are flaky in Spark runner
> -
>
> Key: BEAM-5171
> URL: https://issues.apache.org/jira/browse/BEAM-5171
> Project: Beam
>  Issue Type: Bug
>  Components: runner-spark
>Reporter: Valentyn Tymofieiev
>Assignee: Etienne Chauchot
>Priority: Major
>
> Two tests: 
>  org.apache.beam.sdk.io.CountingSourceTest.testUnboundedSourceSplits 
>  org.apache.beam.sdk.io.CountingSourceTest.testBoundedSourceSplits
> failed in a PostCommit [Spark Validates Runner test 
> suite|https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Spark_Gradle/1277/testReport/]
>  with an error that seems to be common for Spark. Could this be due to 
> misconfiguration of Spark cluster? 
> Task serialization failed: java.io.IOException: Failed to create local dir in 
> /tmp/blockmgr-de91f449-e5d1-4be4-acaa-3ee06fdfa95b/1d.
>  java.io.IOException: Failed to create local dir in 
> /tmp/blockmgr-de91f449-e5d1-4be4-acaa-3ee06fdfa95b/1d.
>  at 
> org.apache.spark.storage.DiskBlockManager.getFile(DiskBlockManager.scala:70)
>  at org.apache.spark.storage.DiskStore.remove(DiskStore.scala:116)
>  at 
> org.apache.spark.storage.BlockManager.removeBlockInternal(BlockManager.scala:1511)
>  at org.apache.spark.storage.BlockManager.doPut(BlockManager.scala:1045)
>  at 
> org.apache.spark.storage.BlockManager.doPutIterator(BlockManager.scala:1083)
>  at org.apache.spark.storage.BlockManager.putIterator(BlockManager.scala:841)
>  at org.apache.spark.storage.BlockManager.putSingle(BlockManager.scala:1404)
>  at 
> org.apache.spark.broadcast.TorrentBroadcast.writeBlocks(TorrentBroadcast.scala:123)
>  at 
> org.apache.spark.broadcast.TorrentBroadcast.(TorrentBroadcast.scala:88)
>  at 
> org.apache.spark.broadcast.TorrentBroadcastFactory.newBroadcast(TorrentBroadcastFactory.scala:34)
>  at 
> org.apache.spark.broadcast.BroadcastManager.newBroadcast(BroadcastManager.scala:62)
>  at org.apache.spark.SparkContext.broadcast(SparkContext.scala:1482)
>  at 
> org.apache.spark.scheduler.DAGScheduler.submitMissingTasks(DAGScheduler.scala:1039)
>  at 
> org.apache.spark.scheduler.DAGScheduler.org$apache$spark$scheduler$DAGScheduler$$submitStage(DAGScheduler.scala:947)
>  at 
> org.apache.spark.scheduler.DAGScheduler.handleJobSubmitted(DAGScheduler.scala:891)
>  at 
> org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.doOnReceive(DAGScheduler.scala:1780)
>  at 
> org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.onReceive(DAGScheduler.scala:1772)
>  at 
> org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.onReceive(DAGScheduler.scala:1761)
>  at org.apache.spark.util.EventLoop$$anon$1.run(EventLoop.scala:48)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (BEAM-5221) Complile error: invalid LOC header (bad signature)

[Shantanu Kirkire (JIRA)]

Shantanu Kirkire created BEAM-5221:
--

 Summary: Complile error: invalid LOC header (bad signature) 
 Key: BEAM-5221
 URL: https://issues.apache.org/jira/browse/BEAM-5221
 Project: Beam
  Issue Type: Bug
  Components: beam-model
Affects Versions: 2.6.0
 Environment: pring Tool Suite 

Version: 3.9.2.RELEASE
Build Id: 201712210947
Platform: Eclipse Oxygen.2 (4.7.2)
Maven 3.3.9
Reporter: Shantanu Kirkire
Assignee: Kenneth Knowles


[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on 
project linking: Compilation failure: Compilation failure:
[ERROR] error reading 
C:\Users\SKirkire\.m2\repository\org\apache\beam\beam-model-pipeline\2.6.0\beam-model-pipeline-2.6.0.jar;
 invalid LOC header (bad signature)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (BEAM-5172) org.apache.beam.sdk.io.elasticsearch/ElasticsearchIOTest is flaky

[Etienne Chauchot (JIRA)]

[ 
https://issues.apache.org/jira/browse/BEAM-5172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16593378#comment-16593378
 ] 

Etienne Chauchot commented on BEAM-5172:


Actually for testRead:
- insert test docs is a simple loop
- IO.read() has been tested a lot and there is no duplicated record 
- index suppression is synchronous with no exception raising
=> I now bet on parallel inserts on the same index. I will try setting an index 
name different for tests that can be run in parallel

> org.apache.beam.sdk.io.elasticsearch/ElasticsearchIOTest is flaky
> -
>
> Key: BEAM-5172
> URL: https://issues.apache.org/jira/browse/BEAM-5172
> Project: Beam
>  Issue Type: Bug
>  Components: io-java-elasticsearch, test-failures
>Reporter: Valentyn Tymofieiev
>Assignee: Etienne Chauchot
>Priority: Major
>
> In a recent PostCommit builld, 
> https://builds.apache.org/job/beam_PostCommit_Java_GradleBuild/1290/testReport/junit/org.apache.beam.sdk.io.elasticsearch/ElasticsearchIOTest/testRead/
>  failed with:
> Error Message
> java.lang.AssertionError: Count/Flatten.PCollections.out: 
> Expected: <400L>
>  but: was <470L>
> Stacktrace
> java.lang.AssertionError: Count/Flatten.PCollections.out: 
> Expected: <400L>
>  but: was <470L>
>   at 
> org.apache.beam.sdk.testing.PAssert$PAssertionSite.capture(PAssert.java:168)
>   at org.apache.beam.sdk.testing.PAssert.thatSingleton(PAssert.java:413)
>   at org.apache.beam.sdk.testing.PAssert.thatSingleton(PAssert.java:404)
>   at 
> org.apache.beam.sdk.io.elasticsearch.ElasticsearchIOTestCommon.testRead(ElasticsearchIOTestCommon.java:124)
>   at 
> org.apache.beam.sdk.io.elasticsearch.ElasticsearchIOTest.testRead(ElasticsearchIOTest.java:125)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at 
> org.junit.rules.ExpectedException$ExpectedExceptionStatement.evaluate(ExpectedException.java:239)
>   at 
> org.apache.beam.sdk.testing.TestPipeline$1.evaluate(TestPipeline.java:319)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>   at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:106)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
>   at 
> org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:66)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.l

[jira] [Work logged] (BEAM-3310) Push metrics to a backend in an runner agnostic way

[ASF GitHub Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-3310?focusedWorklogId=138327&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-138327
 ]

ASF GitHub Bot logged work on BEAM-3310:


Author: ASF GitHub Bot
Created on: 27/Aug/18 09:25
Start Date: 27/Aug/18 09:25
Worklog Time Spent: 10m 
  Work Description: aljoscha commented on issue #4548: [BEAM-3310] Metrics 
pusher
URL: https://github.com/apache/beam/pull/4548#issuecomment-416169053
 
 
   Double confirmation: @echauchot and @JozoVilcek are correct. 👌 


This is an automated message from the Apache Git Service.
To respond to the message, please log on 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: 138327)
Time Spent: 18h 10m  (was: 18h)

> Push metrics to a backend in an runner agnostic way
> ---
>
> Key: BEAM-3310
> URL: https://issues.apache.org/jira/browse/BEAM-3310
> Project: Beam
>  Issue Type: New Feature
>  Components: runner-extensions-metrics, sdk-java-core
>Reporter: Etienne Chauchot
>Assignee: Etienne Chauchot
>Priority: Major
>  Time Spent: 18h 10m
>  Remaining Estimate: 0h
>
> The idea is to avoid relying on the runners to provide access to the metrics 
> (either at the end of the pipeline or while it runs) because they don't have 
> all the same capabilities towards metrics (e.g. spark runner configures sinks 
>  like csv, graphite or in memory sinks using the spark engine conf). The 
> target is to push the metrics in the common runner code so that no matter the 
> chosen runner, a user can get his metrics out of beam.
> Here is the link to the discussion thread on the dev ML: 
> https://lists.apache.org/thread.html/01a80d62f2df6b84bfa41f05e15fda900178f882877c294fed8be91e@%3Cdev.beam.apache.org%3E
> And the design doc:
> https://s.apache.org/runner_independent_metrics_extraction



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (BEAM-4861) Hadoop Filesystem silently fails

[Tim Robertson (JIRA)]

[ 
https://issues.apache.org/jira/browse/BEAM-4861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16593406#comment-16593406
 ] 

Tim Robertson edited comment on BEAM-4861 at 8/27/18 9:44 AM:
--

The {{HadoopFileSystem}} has the following methods:
{code:java}
  @Override
  protected void copy(List srcResourceIds, 
List destResourceIds)
  throws IOException {
for (int i = 0; i < srcResourceIds.size(); ++i) {
  // Unfortunately HDFS FileSystems don't support a native copy operation 
so we are forced
  // to use the inefficient implementation found in FileUtil which copies 
all the bytes through
  // the local machine.
  //
  // HDFS FileSystem does define a concat method but could only find the 
DFSFileSystem
  // implementing it. The DFSFileSystem implemented concat by deleting the 
srcs after which
  // is not what we want. Also, all the other FileSystem implementations I 
saw threw
  // UnsupportedOperationException within concat.
  FileUtil.copy(
  fileSystem,
  srcResourceIds.get(i).toPath(),
  fileSystem,
  destResourceIds.get(i).toPath(),
  false,
  true,
  fileSystem.getConf());
}
  }

  @Override
  protected void rename(
  List srcResourceIds, List 
destResourceIds)
  throws IOException {
for (int i = 0; i < srcResourceIds.size(); ++i) {
  fileSystem.rename(srcResourceIds.get(i).toPath(), 
destResourceIds.get(i).toPath());
}
  }

  @Override
  protected void delete(Collection resourceIds) throws 
IOException {
for (HadoopResourceId resourceId : resourceIds) {
  fileSystem.delete(resourceId.toPath(), false);
}
  }
{code}
{{FileUtil.copy}}, {{fileSystem.rename}} and {{fileSystem.delete}} can all 
return false indicating that the operation was not performed.

 

*1. Informing the user of the unsuccessful operation*

We could either:
 # Change the Beam {{FileSystem}} API to propagate this, although the [rules 
for HDFS 
rename()|https://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-common/filesystem/filesystem.html#boolean_renamePath_src_Path_d]
 are not trivial to document and this might prove to be invasive in many places.
 # Throw an {{IOException}} to signal that the operation was not successful if 
the response is false?

I tend towards suggesting leaving the API to return void but throw an exception 
on the first case of error within the loops - thoughts?

 

*2. rename() in HDFS*

What do we believe are the expectations for {{rename()}} on HDFS?

Currently the user is not informed if an attempt to rename a file into a non 
existent directory is made. This is obviously bad.

We could change behaviour to one of:
 # Throw exception if the directory does not exist
 # Create the directory where necessary, letting files be overridden if it does 
exist (equivalent of e.g. {{S3Filesystem}})
 # Verify that the directory does not exist, and only then create it and 
proceed, otherwise alerting with Exception (the usual behaviour of a 
{{MapReduce FileOutputFormat}} at job startup where it quickly fails with 
"directory already exists").

Note that {{S3FileSystem}} and {{GcsFileSystem}} treat a rename as a {{copy()}} 
and {{delete()}} operation internally.

I tend towards creating the directory where necessary allowing for overwriting 
- thoughts?

CC [~reuvenlax] as relates to BEAM-5036 as well.


was (Author: timrobertson100):
The {{HadoopFileSystem}} has the following methods:
{code:java}
  @Override
  protected void copy(List srcResourceIds, 
List destResourceIds)
  throws IOException {
for (int i = 0; i < srcResourceIds.size(); ++i) {
  // Unfortunately HDFS FileSystems don't support a native copy operation 
so we are forced
  // to use the inefficient implementation found in FileUtil which copies 
all the bytes through
  // the local machine.
  //
  // HDFS FileSystem does define a concat method but could only find the 
DFSFileSystem
  // implementing it. The DFSFileSystem implemented concat by deleting the 
srcs after which
  // is not what we want. Also, all the other FileSystem implementations I 
saw threw
  // UnsupportedOperationException within concat.
  FileUtil.copy(
  fileSystem,
  srcResourceIds.get(i).toPath(),
  fileSystem,
  destResourceIds.get(i).toPath(),
  false,
  true,
  fileSystem.getConf());
}
  }

  @Override
  protected void rename(
  List srcResourceIds, List 
destResourceIds)
  throws IOException {
for (int i = 0; i < srcResourceIds.size(); ++i) {
  fileSystem.rename(srcResourceIds.get(i).toPath(), 
destResourceIds.get(i).toPath());
}
  }

  @Override
  protected void delete(Collection resourceIds) throws 
IOException {
for (HadoopResourceId resourceId : resourceIds) {
  fileSystem.delete(resourceId.t

[jira] [Commented] (BEAM-4861) Hadoop Filesystem silently fails

[Tim Robertson (JIRA)]

[ 
https://issues.apache.org/jira/browse/BEAM-4861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16593406#comment-16593406
 ] 

Tim Robertson commented on BEAM-4861:
-

The {{HadoopFileSystem}} has the following methods:
{code:java}
  @Override
  protected void copy(List srcResourceIds, 
List destResourceIds)
  throws IOException {
for (int i = 0; i < srcResourceIds.size(); ++i) {
  // Unfortunately HDFS FileSystems don't support a native copy operation 
so we are forced
  // to use the inefficient implementation found in FileUtil which copies 
all the bytes through
  // the local machine.
  //
  // HDFS FileSystem does define a concat method but could only find the 
DFSFileSystem
  // implementing it. The DFSFileSystem implemented concat by deleting the 
srcs after which
  // is not what we want. Also, all the other FileSystem implementations I 
saw threw
  // UnsupportedOperationException within concat.
  FileUtil.copy(
  fileSystem,
  srcResourceIds.get(i).toPath(),
  fileSystem,
  destResourceIds.get(i).toPath(),
  false,
  true,
  fileSystem.getConf());
}
  }

  @Override
  protected void rename(
  List srcResourceIds, List 
destResourceIds)
  throws IOException {
for (int i = 0; i < srcResourceIds.size(); ++i) {
  fileSystem.rename(srcResourceIds.get(i).toPath(), 
destResourceIds.get(i).toPath());
}
  }

  @Override
  protected void delete(Collection resourceIds) throws 
IOException {
for (HadoopResourceId resourceId : resourceIds) {
  fileSystem.delete(resourceId.toPath(), false);
}
  }
{code}
{{FileUtil.copy}}, {{fileSystem.rename}} and {{fileSystem.delete}} can all 
return false indicating that the operation was not performed.

 

*1. Informing the user of the unsuccessful operation*

We could either:
 # Change the Beam {{FileSystem}} API to propagate this, although the [rules 
for HDFS 
rename()|https://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-common/filesystem/filesystem.html#boolean_renamePath_src_Path_d]
 are not trivial to document and this might prove to be invasive in many places.
 # Throw an {{IOException}} to signal that the operation was not successful if 
the response is false?

I tend towards suggesting leaving the API to return void but throw an exception 
on the first case of error within the loops - thoughts?

 

***2. rename() in HDFS*

What do we believe are the expectations for {{rename()}} on HDFS?

Currently the user is not informed if an attempt to rename a file into a non 
existent directory is made. This is obviously bad.

We could change behaviour to one of:
 # Throw exception if the directory does not exist
 # Create the directory where necessary, letting files be overridden if it does 
exist (equivalent of e.g. {{S3Filesystem}})
 # Verify that the directory does not exist, and only then create it and 
proceed, otherwise alerting with Exception (the usual behaviour of a 
{{MapReduce FileOutputFormat}} at job startup where it quickly fails with 
"directory already exists").

Note that {{S3FileSystem}} and {{GcsFileSystem}} treat a rename as a {{copy()}} 
and {{delete()}} operation internally.

I tend towards creating the directory where necessary allowing for overwriting 
- thoughts?

CC [~reuvenlax] as relates to BEAM-5036 as well.

> Hadoop Filesystem silently fails
> 
>
> Key: BEAM-4861
> URL: https://issues.apache.org/jira/browse/BEAM-4861
> Project: Beam
>  Issue Type: Bug
>  Components: io-java-hadoop
>Reporter: Jozef Vilcek
>Assignee: Chamikara Jayalath
>Priority: Major
>
> Hi,
> beam Filesystem operations copy, rename and delete are void in SDK. Hadoop 
> native filesystem operations are not and returns void. Current implementation 
> in Beam ignores the result and pass as long as exception is not thrown.
> I got burned by this when using 'rename' to do a 'move' operation on HDFS. If 
> target directory does not exists, operations returns false and do not touch 
> the file.
> [https://github.com/apache/beam/blob/master/sdks/java/io/hadoop-file-system/src/main/java/org/apache/beam/sdk/io/hdfs/HadoopFileSystem.java#L148]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (BEAM-4861) Hadoop Filesystem silently fails

[Tim Robertson (JIRA)]

[ 
https://issues.apache.org/jira/browse/BEAM-4861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16593406#comment-16593406
 ] 

Tim Robertson edited comment on BEAM-4861 at 8/27/18 10:03 AM:
---

The {{HadoopFileSystem}} has the following methods:
{code:java}
  @Override
  protected void copy(List srcResourceIds, 
List destResourceIds)
  throws IOException {
for (int i = 0; i < srcResourceIds.size(); ++i) {
  // Unfortunately HDFS FileSystems don't support a native copy operation 
so we are forced
  // to use the inefficient implementation found in FileUtil which copies 
all the bytes through
  // the local machine.
  //
  // HDFS FileSystem does define a concat method but could only find the 
DFSFileSystem
  // implementing it. The DFSFileSystem implemented concat by deleting the 
srcs after which
  // is not what we want. Also, all the other FileSystem implementations I 
saw threw
  // UnsupportedOperationException within concat.
  FileUtil.copy(
  fileSystem,
  srcResourceIds.get(i).toPath(),
  fileSystem,
  destResourceIds.get(i).toPath(),
  false,
  true,
  fileSystem.getConf());
}
  }

  @Override
  protected void rename(
  List srcResourceIds, List 
destResourceIds)
  throws IOException {
for (int i = 0; i < srcResourceIds.size(); ++i) {
  fileSystem.rename(srcResourceIds.get(i).toPath(), 
destResourceIds.get(i).toPath());
}
  }

  @Override
  protected void delete(Collection resourceIds) throws 
IOException {
for (HadoopResourceId resourceId : resourceIds) {
  fileSystem.delete(resourceId.toPath(), false);
}
  }
{code}
{{FileUtil.copy}}, {{fileSystem.rename}} and {{fileSystem.delete}} can all 
return false indicating that the operation was not performed.

 

*1. Informing the user of the unsuccessful operation*

We could either:
 # Change the Beam {{FileSystem}} API to propagate this, although the [rules 
for HDFS 
rename()|https://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-common/filesystem/filesystem.html#boolean_renamePath_src_Path_d]
 are not trivial to document and this might prove to be invasive in many places.
 # Throw an {{IOException}} to signal that the operation was not successful if 
the response is false?

I tend towards suggesting leaving the API to return void but throw an exception 
on the first case of error within the loops - thoughts?

 

*2. rename() in HDFS*

What do we believe are the expectations for {{rename()}} on HDFS?

Currently the user is not informed that nothing happens if an attempt to rename 
a file into a non existent directory is made. This is obviously bad.

We could change behaviour to one of:
 # Throw exception if the directory does not exist
 # Create the directory where necessary, letting files be overridden if it does 
exist (equivalent of e.g. {{S3Filesystem}})
 # Verify that the directory does not exist, and only then create it and 
proceed, otherwise alerting with Exception (the usual behaviour of a 
{{MapReduce FileOutputFormat}} at job startup where it quickly fails with 
"directory already exists").

Note that {{S3FileSystem}} and {{GcsFileSystem}} treat a rename as a {{copy()}} 
and {{delete()}} operation internally.

I tend towards creating the directory where necessary allowing for overwriting 
- thoughts?

CC [~reuvenlax] as relates to BEAM-5036 as well.


was (Author: timrobertson100):
The {{HadoopFileSystem}} has the following methods:
{code:java}
  @Override
  protected void copy(List srcResourceIds, 
List destResourceIds)
  throws IOException {
for (int i = 0; i < srcResourceIds.size(); ++i) {
  // Unfortunately HDFS FileSystems don't support a native copy operation 
so we are forced
  // to use the inefficient implementation found in FileUtil which copies 
all the bytes through
  // the local machine.
  //
  // HDFS FileSystem does define a concat method but could only find the 
DFSFileSystem
  // implementing it. The DFSFileSystem implemented concat by deleting the 
srcs after which
  // is not what we want. Also, all the other FileSystem implementations I 
saw threw
  // UnsupportedOperationException within concat.
  FileUtil.copy(
  fileSystem,
  srcResourceIds.get(i).toPath(),
  fileSystem,
  destResourceIds.get(i).toPath(),
  false,
  true,
  fileSystem.getConf());
}
  }

  @Override
  protected void rename(
  List srcResourceIds, List 
destResourceIds)
  throws IOException {
for (int i = 0; i < srcResourceIds.size(); ++i) {
  fileSystem.rename(srcResourceIds.get(i).toPath(), 
destResourceIds.get(i).toPath());
}
  }

  @Override
  protected void delete(Collection resourceIds) throws 
IOException {
for (HadoopResourceId resourceId : resourceIds) {
  fileSys

[jira] [Comment Edited] (BEAM-4861) Hadoop Filesystem silently fails

[Tim Robertson (JIRA)]

[ 
https://issues.apache.org/jira/browse/BEAM-4861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16593406#comment-16593406
 ] 

Tim Robertson edited comment on BEAM-4861 at 8/27/18 10:04 AM:
---

The {{HadoopFileSystem}} has the following methods:
{code:java}
  @Override
  protected void copy(List srcResourceIds, 
List destResourceIds)
  throws IOException {
for (int i = 0; i < srcResourceIds.size(); ++i) {
  // Unfortunately HDFS FileSystems don't support a native copy operation 
so we are forced
  // to use the inefficient implementation found in FileUtil which copies 
all the bytes through
  // the local machine.
  //
  // HDFS FileSystem does define a concat method but could only find the 
DFSFileSystem
  // implementing it. The DFSFileSystem implemented concat by deleting the 
srcs after which
  // is not what we want. Also, all the other FileSystem implementations I 
saw threw
  // UnsupportedOperationException within concat.
  FileUtil.copy(
  fileSystem,
  srcResourceIds.get(i).toPath(),
  fileSystem,
  destResourceIds.get(i).toPath(),
  false,
  true,
  fileSystem.getConf());
}
  }

  @Override
  protected void rename(
  List srcResourceIds, List 
destResourceIds)
  throws IOException {
for (int i = 0; i < srcResourceIds.size(); ++i) {
  fileSystem.rename(srcResourceIds.get(i).toPath(), 
destResourceIds.get(i).toPath());
}
  }

  @Override
  protected void delete(Collection resourceIds) throws 
IOException {
for (HadoopResourceId resourceId : resourceIds) {
  fileSystem.delete(resourceId.toPath(), false);
}
  }
{code}
{{FileUtil.copy}}, {{fileSystem.rename}} and {{fileSystem.delete}} can all 
return false indicating that the operation was not performed.

 

*1. Informing the user of the unsuccessful operation*

We could either:
 # Change the Beam {{FileSystem}} API to propagate this, although the [rules 
for HDFS 
rename()|https://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-common/filesystem/filesystem.html#boolean_renamePath_src_Path_d]
 are not trivial to document and this might prove to be invasive in many places.
 # Throw an {{IOException}} to signal that the operation was not successful if 
the response is false?

I tend towards suggesting leaving the API to return void but throw an exception 
on the first case of error within the loops - thoughts?

 

*2. rename() in HDFS*

What do we believe are the expectations for {{rename()}} on HDFS?

Currently the user is not informed that nothing happens if an attempt to rename 
a file into a non existent directory is made. This is obviously bad.

We could change behaviour to one of:
 # Throw exception if the directory does not exist
 # Create the directory where necessary, letting existing files be overridden 
(equivalent of e.g. {{S3Filesystem}})
 # Verify that the directory does not exist, and only then create it and 
proceed, otherwise alerting with Exception (the usual behaviour of a 
{{MapReduce FileOutputFormat}} at job startup where it quickly fails with 
"directory already exists").

Note that {{S3FileSystem}} and {{GcsFileSystem}} treat a rename as a {{copy()}} 
and {{delete()}} operation internally.

I tend towards creating the directory where necessary allowing for overwriting 
- thoughts?

CC [~reuvenlax] as relates to BEAM-5036 as well.


was (Author: timrobertson100):
The {{HadoopFileSystem}} has the following methods:
{code:java}
  @Override
  protected void copy(List srcResourceIds, 
List destResourceIds)
  throws IOException {
for (int i = 0; i < srcResourceIds.size(); ++i) {
  // Unfortunately HDFS FileSystems don't support a native copy operation 
so we are forced
  // to use the inefficient implementation found in FileUtil which copies 
all the bytes through
  // the local machine.
  //
  // HDFS FileSystem does define a concat method but could only find the 
DFSFileSystem
  // implementing it. The DFSFileSystem implemented concat by deleting the 
srcs after which
  // is not what we want. Also, all the other FileSystem implementations I 
saw threw
  // UnsupportedOperationException within concat.
  FileUtil.copy(
  fileSystem,
  srcResourceIds.get(i).toPath(),
  fileSystem,
  destResourceIds.get(i).toPath(),
  false,
  true,
  fileSystem.getConf());
}
  }

  @Override
  protected void rename(
  List srcResourceIds, List 
destResourceIds)
  throws IOException {
for (int i = 0; i < srcResourceIds.size(); ++i) {
  fileSystem.rename(srcResourceIds.get(i).toPath(), 
destResourceIds.get(i).toPath());
}
  }

  @Override
  protected void delete(Collection resourceIds) throws 
IOException {
for (HadoopResourceId resourceId : resourceIds) {
  fileSystem.dele

[jira] [Comment Edited] (BEAM-5036) Optimize FileBasedSink's WriteOperation.moveToOutput()

[Tim Robertson (JIRA)]

[ 
https://issues.apache.org/jira/browse/BEAM-5036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16593439#comment-16593439
 ] 

Tim Robertson edited comment on BEAM-5036 at 8/27/18 10:09 AM:
---

Thanks [~reuvenlax]

1. Adding a cross FS check seems reasonable as a precaution.

2. Please see [this 
comment|https://issues.apache.org/jira/browse/BEAM-4861?focusedCommentId=16593406&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16593406]
 on BEAM-4861 where we have a decision to make on the HDFS parent directory not 
existing. Appreciate your and [~JozoVilcek] thoughts on that (and others).


was (Author: timrobertson100):
Thanks [~reuvenlax]

1. Adding a cross FS check seems reasonable as a precaution.

2. Please see this comment on BEAM-4861 where we have a decision to make on the 
HDFS parent directory not existing. Appreciate your and [~JozoVilcek] thoughts 
on that (and others).

> Optimize FileBasedSink's WriteOperation.moveToOutput()
> --
>
> Key: BEAM-5036
> URL: https://issues.apache.org/jira/browse/BEAM-5036
> Project: Beam
>  Issue Type: Improvement
>  Components: io-java-files
>Affects Versions: 2.5.0
>Reporter: Jozef Vilcek
>Assignee: Tim Robertson
>Priority: Major
>
> moveToOutput() methods in FileBasedSink.WriteOperation implements move by 
> copy+delete. It would be better to use a rename() which can be much more 
> effective for some filesystems.
> Filesystem must support cross-directory rename. BEAM-4861 is related to this 
> for the case of HDFS filesystem.
> Feature was discussed here:
> http://mail-archives.apache.org/mod_mbox/beam-dev/201807.mbox/%3CCAF9t7_4Mp54pQ+vRrJrBh9Vx0=uaknupzd_qdh_qdm9vxll...@mail.gmail.com%3E



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (BEAM-5036) Optimize FileBasedSink's WriteOperation.moveToOutput()

[Tim Robertson (JIRA)]

[ 
https://issues.apache.org/jira/browse/BEAM-5036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16593439#comment-16593439
 ] 

Tim Robertson commented on BEAM-5036:
-

Thanks [~reuvenlax]

1. Adding a cross FS check seems reasonable as a precaution.

2. Please see this comment on BEAM-4861 where we have a decision to make on the 
HDFS parent directory not existing. Appreciate your and [~JozoVilcek] thoughts 
on that (and others).

> Optimize FileBasedSink's WriteOperation.moveToOutput()
> --
>
> Key: BEAM-5036
> URL: https://issues.apache.org/jira/browse/BEAM-5036
> Project: Beam
>  Issue Type: Improvement
>  Components: io-java-files
>Affects Versions: 2.5.0
>Reporter: Jozef Vilcek
>Assignee: Tim Robertson
>Priority: Major
>
> moveToOutput() methods in FileBasedSink.WriteOperation implements move by 
> copy+delete. It would be better to use a rename() which can be much more 
> effective for some filesystems.
> Filesystem must support cross-directory rename. BEAM-4861 is related to this 
> for the case of HDFS filesystem.
> Feature was discussed here:
> http://mail-archives.apache.org/mod_mbox/beam-dev/201807.mbox/%3CCAF9t7_4Mp54pQ+vRrJrBh9Vx0=uaknupzd_qdh_qdm9vxll...@mail.gmail.com%3E



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (BEAM-4861) Hadoop Filesystem silently fails

[Jozef Vilcek (JIRA)]

[ 
https://issues.apache.org/jira/browse/BEAM-4861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16593447#comment-16593447
 ] 

Jozef Vilcek commented on BEAM-4861:


For unsuccessful operation, I would throw exception as well. In practice, this 
is what is mostly done around the native HDFS boolean methods by helpers. Fail 
and investigate later what was wrong.

For rename, create directories where necessary sounds good. Plus with allowing 
overwrites, behaviour would be consistent with what I observe on "normal file 
create" operations. Allow overwrite is maybe allowed for cases or restarting 
jobs form snapshots which can lead to reprocessing and recreating same outputs 
again? Not sure.

> Hadoop Filesystem silently fails
> 
>
> Key: BEAM-4861
> URL: https://issues.apache.org/jira/browse/BEAM-4861
> Project: Beam
>  Issue Type: Bug
>  Components: io-java-hadoop
>Reporter: Jozef Vilcek
>Assignee: Chamikara Jayalath
>Priority: Major
>
> Hi,
> beam Filesystem operations copy, rename and delete are void in SDK. Hadoop 
> native filesystem operations are not and returns void. Current implementation 
> in Beam ignores the result and pass as long as exception is not thrown.
> I got burned by this when using 'rename' to do a 'move' operation on HDFS. If 
> target directory does not exists, operations returns false and do not touch 
> the file.
> [https://github.com/apache/beam/blob/master/sdks/java/io/hadoop-file-system/src/main/java/org/apache/beam/sdk/io/hdfs/HadoopFileSystem.java#L148]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (BEAM-4861) Hadoop Filesystem silently fails

[Tim Robertson (JIRA)]

[ 
https://issues.apache.org/jira/browse/BEAM-4861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16593406#comment-16593406
 ] 

Tim Robertson edited comment on BEAM-4861 at 8/27/18 10:22 AM:
---

The {{HadoopFileSystem}} has the following methods:
{code:java}
  @Override
  protected void copy(List srcResourceIds, 
List destResourceIds)
  throws IOException {
for (int i = 0; i < srcResourceIds.size(); ++i) {
  // Unfortunately HDFS FileSystems don't support a native copy operation 
so we are forced
  // to use the inefficient implementation found in FileUtil which copies 
all the bytes through
  // the local machine.
  //
  // HDFS FileSystem does define a concat method but could only find the 
DFSFileSystem
  // implementing it. The DFSFileSystem implemented concat by deleting the 
srcs after which
  // is not what we want. Also, all the other FileSystem implementations I 
saw threw
  // UnsupportedOperationException within concat.
  FileUtil.copy(
  fileSystem,
  srcResourceIds.get(i).toPath(),
  fileSystem,
  destResourceIds.get(i).toPath(),
  false,
  true,
  fileSystem.getConf());
}
  }

  @Override
  protected void rename(
  List srcResourceIds, List 
destResourceIds)
  throws IOException {
for (int i = 0; i < srcResourceIds.size(); ++i) {
  fileSystem.rename(srcResourceIds.get(i).toPath(), 
destResourceIds.get(i).toPath());
}
  }

  @Override
  protected void delete(Collection resourceIds) throws 
IOException {
for (HadoopResourceId resourceId : resourceIds) {
  fileSystem.delete(resourceId.toPath(), false);
}
  }
{code}
{{FileUtil.copy}}, {{fileSystem.rename}} and {{fileSystem.delete}} can all 
return false indicating that the operation was not performed.

 

*1. Informing the user of the unsuccessful operation*

We could either:
 # Change the Beam {{FileSystem}} API to propagate this, although the [rules 
for HDFS 
rename()|https://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-common/filesystem/filesystem.html#boolean_renamePath_src_Path_d]
 are not trivial to document and this might prove to be invasive in many places.
 # Throw an {{IOException}} to signal that the operation was not successful if 
the response is false?

I tend towards suggesting leaving the API to return void but throw an exception 
on the first case of error within the loops - thoughts?

 

*2. rename() in HDFS*

What do we believe are the expectations for {{rename()}} on HDFS?

Currently the user is not informed that nothing happens if an attempt to rename 
a file into a non existent directory is made. This is obviously bad.

We could change behaviour to one of:
 # Throw exception if the directory does not exist
 # Create the directory where necessary, letting existing files be overridden 
(equivalent of e.g. {{S3Filesystem}})
 # Verify that the directory does not exist, and only then create it and 
proceed, otherwise alerting with Exception (the usual behaviour of a 
{{MapReduce / Spark FileOutputFormat}} at job startup where it quickly fails 
with "directory already exists").

Note that {{S3FileSystem}} and {{GcsFileSystem}} treat a rename as a {{copy()}} 
and {{delete()}} operation internally.

I tend towards creating the directory where necessary allowing for overwriting 
- thoughts?

CC [~reuvenlax] as relates to BEAM-5036 as well.


was (Author: timrobertson100):
The {{HadoopFileSystem}} has the following methods:
{code:java}
  @Override
  protected void copy(List srcResourceIds, 
List destResourceIds)
  throws IOException {
for (int i = 0; i < srcResourceIds.size(); ++i) {
  // Unfortunately HDFS FileSystems don't support a native copy operation 
so we are forced
  // to use the inefficient implementation found in FileUtil which copies 
all the bytes through
  // the local machine.
  //
  // HDFS FileSystem does define a concat method but could only find the 
DFSFileSystem
  // implementing it. The DFSFileSystem implemented concat by deleting the 
srcs after which
  // is not what we want. Also, all the other FileSystem implementations I 
saw threw
  // UnsupportedOperationException within concat.
  FileUtil.copy(
  fileSystem,
  srcResourceIds.get(i).toPath(),
  fileSystem,
  destResourceIds.get(i).toPath(),
  false,
  true,
  fileSystem.getConf());
}
  }

  @Override
  protected void rename(
  List srcResourceIds, List 
destResourceIds)
  throws IOException {
for (int i = 0; i < srcResourceIds.size(); ++i) {
  fileSystem.rename(srcResourceIds.get(i).toPath(), 
destResourceIds.get(i).toPath());
}
  }

  @Override
  protected void delete(Collection resourceIds) throws 
IOException {
for (HadoopResourceId resourceId : resourceIds) {
  fileSys

[jira] [Work logged] (BEAM-3310) Push metrics to a backend in an runner agnostic way

[ASF GitHub Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-3310?focusedWorklogId=138339&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-138339
 ]

ASF GitHub Bot logged work on BEAM-3310:


Author: ASF GitHub Bot
Created on: 27/Aug/18 10:49
Start Date: 27/Aug/18 10:49
Worklog Time Spent: 10m 
  Work Description: JozoVilcek commented on issue #4548: [BEAM-3310] 
Metrics pusher
URL: https://github.com/apache/beam/pull/4548#issuecomment-416188576
 
 
   So, I am playing with flink `MetricReporter` (and also with UI) and observe 
a bit strange thing. Job reading from kafka should report `elements_read` beam 
counter. I can see it in UI if I select source task. But, there are many many 
instances. I would expect to see the counter only for one `operator` and its 
`subtasks` (I am guessing it relates to parallelism). But, what I observe is 
like `elements_read` counter being defined for each operator within that task. 
   Can this be some sort of double counting or mirror or what is going on? I am 
not sure how to deal with this in `MetricReporter` so I do not double count in 
time-series database.
   
   P.S.: I should probably be asking this somewhere else, right? :)


This is an automated message from the Apache Git Service.
To respond to the message, please log on 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: 138339)
Time Spent: 18h 20m  (was: 18h 10m)

> Push metrics to a backend in an runner agnostic way
> ---
>
> Key: BEAM-3310
> URL: https://issues.apache.org/jira/browse/BEAM-3310
> Project: Beam
>  Issue Type: New Feature
>  Components: runner-extensions-metrics, sdk-java-core
>Reporter: Etienne Chauchot
>Assignee: Etienne Chauchot
>Priority: Major
>  Time Spent: 18h 20m
>  Remaining Estimate: 0h
>
> The idea is to avoid relying on the runners to provide access to the metrics 
> (either at the end of the pipeline or while it runs) because they don't have 
> all the same capabilities towards metrics (e.g. spark runner configures sinks 
>  like csv, graphite or in memory sinks using the spark engine conf). The 
> target is to push the metrics in the common runner code so that no matter the 
> chosen runner, a user can get his metrics out of beam.
> Here is the link to the discussion thread on the dev ML: 
> https://lists.apache.org/thread.html/01a80d62f2df6b84bfa41f05e15fda900178f882877c294fed8be91e@%3Cdev.beam.apache.org%3E
> And the design doc:
> https://s.apache.org/runner_independent_metrics_extraction



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Work logged] (BEAM-313) Enable the use of an existing spark context with the SparkPipelineRunner

[ASF GitHub Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-313?focusedWorklogId=138351&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-138351
 ]

ASF GitHub Bot logged work on BEAM-313:
---

Author: ASF GitHub Bot
Created on: 27/Aug/18 11:39
Start Date: 27/Aug/18 11:39
Worklog Time Spent: 10m 
  Work Description: amarouni commented on issue #401: [BEAM-313] Enable the 
use of an existing spark context with the SparkPipelineRunner
URL: https://github.com/apache/beam/pull/401#issuecomment-416199029
 
 
   @kohlerm 
   
   Here's an old Scala snippet that shows how to use Beam & SJS, it's based on 
old versions of SJS & Beam so it probably won't compile with new SJS/Beam 
versions but you'll get the idea : 
   
   ```scala
   import com.typesafe.config.Config
   import org.apache.beam.runners.spark.{ SparkContextOptions, SparkRunner }
   import org.apache.beam.sdk.Pipeline
   import org.apache.beam.sdk.coders.StringUtf8Coder
   import org.apache.beam.sdk.options.PipelineOptionsFactory
   import org.apache.beam.sdk.transforms.Create
   import org.apache.spark.SparkContext
   import org.apache.spark.api.java.JavaSparkContext
   import spark.jobserver.{ SparkJob, SparkJobInvalid, SparkJobValid, 
SparkJobValidation }
   
   import scala.collection.JavaConversions
   import scala.util.Try
   
   /**
* Beam wordcount test. Returns the word count of a fixed String seq.
*/
   object BeamWordCount extends SparkJob {
 override def validate(sc: SparkContext, config: Config): 
SparkJobValidation = {
   
   Try(config.getStringList("wordList"))
 .map(x => SparkJobValid)
 .getOrElse(SparkJobInvalid("No wordList in context config"))
 }
   
 override def runJob(sc: SparkContext, jobConfig: Config): Any = {
   
   // Input test list
   val inputBuffer = 
scala.collection.JavaConversions.asScalaBuffer(jobConfig.getStringList("wordList"))
   val WORDS = inputBuffer.toList
   
   // Pipeline options
   val sparkPipelineOptions = 
PipelineOptionsFactory.as(classOf[SparkContextOptions])
   sparkPipelineOptions.setAppName("Beam WordCount test")
   sparkPipelineOptions.setRunner(classOf[SparkRunner])
   sparkPipelineOptions.setUsesProvidedSparkContext(true)
   sparkPipelineOptions.setProvidedSparkContext(new JavaSparkContext(sc))
   
   // Pipeline
   val pipeline = Pipeline.create(sparkPipelineOptions)
   
   // Input + processing + Output
   val output = pipeline
 
.apply(Create.of(JavaConversions.seqAsJavaList(WORDS)).withCoder(StringUtf8Coder.of()))
 .apply(new CountWords())
   
   // Result
   // val result: EvaluationResult = 
pipeline.run().asInstanceOf[EvaluationResult]
   
   // Run job & wait until finish
   pipeline.run().waitUntilFinish()
 }
   }
   ```
   
   It'd be nice to contribute this as new documentation if you manage to get it 
to work. 


This is an automated message from the Apache Git Service.
To respond to the message, please log on 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: 138351)
Time Spent: 1h 10m  (was: 1h)

> Enable the use of an existing spark context with the SparkPipelineRunner
> 
>
> Key: BEAM-313
> URL: https://issues.apache.org/jira/browse/BEAM-313
> Project: Beam
>  Issue Type: New Feature
>  Components: runner-spark
>Reporter: Abbass Marouni
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 0.3.0-incubating
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> The general use case is that the SparkPipelineRunner creates its own Spark 
> context and uses it for the pipeline execution.
> Another alternative is to provide the SparkPipelineRunner with an existing 
> spark context. This can be interesting for a lot of use cases where the Spark 
> context is managed outside of beam (context reuse, advanced context 
> management, spark job server, ...).
> code sample : 
> https://github.com/amarouni/incubator-beam/commit/fe0bb517bf0ccde07ef5a61f3e44df695b75f076



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Work logged] (BEAM-4824) Get BigQueryIO batch loads to return something actionable

[ASF GitHub Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-4824?focusedWorklogId=138352&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-138352
 ]

ASF GitHub Bot logged work on BEAM-4824:


Author: ASF GitHub Bot
Created on: 27/Aug/18 11:42
Start Date: 27/Aug/18 11:42
Worklog Time Spent: 10m 
  Work Description: calonso commented on issue #6055: [BEAM-4824] Batch 
BigQueryIO returns job results
URL: https://github.com/apache/beam/pull/6055#issuecomment-416199545
 
 
   Sorry for the delay, been on holidays.
   
   I think I can make the new behaviour opt-in by adding a new method to the 
builder, similar to what I did in #5341.
   
   I'm not sure though on what to do about your second comment. Maybe just 
limiting to batch jobs? (using `expandUntriggered`?) although I think having 
the job result information is really valuable in all cases, even if it changes 
the record granularity.


This is an automated message from the Apache Git Service.
To respond to the message, please log on 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: 138352)
Time Spent: 0.5h  (was: 20m)

> Get BigQueryIO batch loads to return something actionable
> -
>
> Key: BEAM-4824
> URL: https://issues.apache.org/jira/browse/BEAM-4824
> Project: Beam
>  Issue Type: Improvement
>  Components: io-java-gcp
>Reporter: Carlos Alonso
>Assignee: Carlos Alonso
>Priority: Minor
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> ATM BigQueryIO batchloads returns an empty collection that has no information 
> related to how the load job finished. It is even returned before the job 
> finishes.
>  
> Change it so that:
>  # The returning PCollection only appers when the job has actually finished
>  # The returning PCollection contains information about the job result



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Work logged] (BEAM-313) Enable the use of an existing spark context with the SparkPipelineRunner

[ASF GitHub Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-313?focusedWorklogId=138355&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-138355
 ]

ASF GitHub Bot logged work on BEAM-313:
---

Author: ASF GitHub Bot
Created on: 27/Aug/18 12:00
Start Date: 27/Aug/18 12:00
Worklog Time Spent: 10m 
  Work Description: kohlerm commented on issue #401: [BEAM-313] Enable the 
use of an existing spark context with the SparkPipelineRunner
URL: https://github.com/apache/beam/pull/401#issuecomment-416203659
 
 
   Thanks a lot! Of course in case we get it work I would try to document it. I 
think this is a pretty common use case.


This is an automated message from the Apache Git Service.
To respond to the message, please log on 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: 138355)
Time Spent: 1h 20m  (was: 1h 10m)

> Enable the use of an existing spark context with the SparkPipelineRunner
> 
>
> Key: BEAM-313
> URL: https://issues.apache.org/jira/browse/BEAM-313
> Project: Beam
>  Issue Type: New Feature
>  Components: runner-spark
>Reporter: Abbass Marouni
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 0.3.0-incubating
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> The general use case is that the SparkPipelineRunner creates its own Spark 
> context and uses it for the pipeline execution.
> Another alternative is to provide the SparkPipelineRunner with an existing 
> spark context. This can be interesting for a lot of use cases where the Spark 
> context is managed outside of beam (context reuse, advanced context 
> management, spark job server, ...).
> code sample : 
> https://github.com/amarouni/incubator-beam/commit/fe0bb517bf0ccde07ef5a61f3e44df695b75f076



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (BEAM-5222) Parquet IO position invalid when writing integers

[George Hilios (JIRA)]

George Hilios created BEAM-5222:
---

 Summary: Parquet IO position invalid when writing integers
 Key: BEAM-5222
 URL: https://issues.apache.org/jira/browse/BEAM-5222
 Project: Beam
  Issue Type: Bug
  Components: io-java-parquet
Reporter: George Hilios
Assignee: Lukasz Gajowy


Please see 
[https://github.com/apache/beam/blob/master/sdks/java/io/parquet/src/main/java/org/apache/beam/sdk/io/parquet/ParquetIO.java#L345]

On write(int b), position is incremented by 1. On write(byte[] b, int off, int 
len) position is incremented by the length of the byte array.

write(int b) should increment by 4 bytes, if I'm understanding correctly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (BEAM-5069) Incorrect string type check in _OutputProcessor.process_outputs.

[Juan Carlos Cardenas (JIRA)]

[ 
https://issues.apache.org/jira/browse/BEAM-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16593564#comment-16593564
 ] 

Juan Carlos Cardenas commented on BEAM-5069:


I'm interested, but sorry Valentyn but I'm new to beam and I have no idea of 
how to start with this "unit test" :)
if you can guide me, I will more than happy to help...

> Incorrect string type check in _OutputProcessor.process_outputs.
> 
>
> Key: BEAM-5069
> URL: https://issues.apache.org/jira/browse/BEAM-5069
> Project: Beam
>  Issue Type: Bug
>  Components: sdk-py-core
>Reporter: Valentyn Tymofieiev
>Assignee: Valentyn Tymofieiev
>Priority: Major
>
> Due to _# cython: language_level=3_ directive in 
> [common.py|https://github.com/apache/beam/blob/8f1d86ea7bd5b118bc7e638d4d484445101526a1/sdks/python/apache_beam/runners/common.py#L18],
>  the type check in 
> [common.py|https://github.com/apache/beam/blob/8f1d86ea7bd5b118bc7e638d4d484445101526a1/sdks/python/apache_beam/runners/common.py#L729]
>  does not recognize Python 2 strings, which have type 'bytes'.
> This causes pipelines to crash when this codepath is executed in Cythonized 
> version of the SDK.
> The regression happened during ongoing efforts to make Beam codebase Python 3 
> compatible.
> The fix will need to be cherry-picked into the 2.6.0 release.
> Working on the fix.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-5079) Beam Dependency Update Request: google-cloud-bigquery 1.5.0

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-5079:

Description: 


2018-08-06 12:07:33.923923

Please review and upgrade the google-cloud-bigquery to the latest 
version 1.5.0 
 
cc: 

2018-08-13 12:07:49.652119

Please review and upgrade the google-cloud-bigquery to the latest 
version 1.5.0 
 
cc: 

2018-08-20 12:10:19.579639

Please review and upgrade the google-cloud-bigquery to the latest 
version 1.5.0 
 
cc: 

2018-08-27 12:09:26.119958

Please review and upgrade the google-cloud-bigquery to the latest 
version 1.5.0 
 
cc: 

  was:


2018-08-06 12:07:33.923923

Please review and upgrade the google-cloud-bigquery to the latest 
version 1.5.0 
 
cc: 

2018-08-13 12:07:49.652119

Please review and upgrade the google-cloud-bigquery to the latest 
version 1.5.0 
 
cc: 

2018-08-20 12:10:19.579639

Please review and upgrade the google-cloud-bigquery to the latest 
version 1.5.0 
 
cc: 


> Beam Dependency Update Request: google-cloud-bigquery 1.5.0
> ---
>
> Key: BEAM-5079
> URL: https://issues.apache.org/jira/browse/BEAM-5079
> Project: Beam
>  Issue Type: Bug
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Assignee: Charles Chen
>Priority: Major
>  Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> 2018-08-06 12:07:33.923923
> Please review and upgrade the google-cloud-bigquery to the latest 
> version 1.5.0 
>  
> cc: 
> 2018-08-13 12:07:49.652119
> Please review and upgrade the google-cloud-bigquery to the latest 
> version 1.5.0 
>  
> cc: 
> 2018-08-20 12:10:19.579639
> Please review and upgrade the google-cloud-bigquery to the latest 
> version 1.5.0 
>  
> cc: 
> 2018-08-27 12:09:26.119958
> Please review and upgrade the google-cloud-bigquery to the latest 
> version 1.5.0 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (BEAM-5223) Beam Dependency Update Request: google-cloud-pubsub 0.37.2

[Beam JIRA Bot (JIRA)]

Beam JIRA Bot created BEAM-5223:
---

 Summary: Beam Dependency Update Request: google-cloud-pubsub 0.37.2
 Key: BEAM-5223
 URL: https://issues.apache.org/jira/browse/BEAM-5223
 Project: Beam
  Issue Type: Bug
  Components: dependencies
Reporter: Beam JIRA Bot
Assignee: Mark Liu




2018-08-27 12:10:14.029397

Please review and upgrade the google-cloud-pubsub to the latest version 
0.37.2 
 
cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-4900) Beam Dependency Update Request: org.apache.commons:commons-dbcp2 2.5.0

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-4900:

Description: 


2018-07-25 20:23:31.265674

Please review and upgrade the org.apache.commons:commons-dbcp2 to the 
latest version 2.5.0 
 
cc: 

2018-08-06 12:09:19.186808

Please review and upgrade the org.apache.commons:commons-dbcp2 to the 
latest version 2.5.0 
 
cc: 

2018-08-13 12:09:37.170682

Please review and upgrade the org.apache.commons:commons-dbcp2 to the 
latest version 2.5.0 
 
cc: 

2018-08-20 12:12:21.262763

Please review and upgrade the org.apache.commons:commons-dbcp2 to the 
latest version 2.5.0 
 
cc: 

2018-08-27 12:13:50.267143

Please review and upgrade the org.apache.commons:commons-dbcp2 to the 
latest version 2.5.0 
 
cc: 

  was:


2018-07-25 20:23:31.265674

Please review and upgrade the org.apache.commons:commons-dbcp2 to the 
latest version 2.5.0 
 
cc: 

2018-08-06 12:09:19.186808

Please review and upgrade the org.apache.commons:commons-dbcp2 to the 
latest version 2.5.0 
 
cc: 

2018-08-13 12:09:37.170682

Please review and upgrade the org.apache.commons:commons-dbcp2 to the 
latest version 2.5.0 
 
cc: 

2018-08-20 12:12:21.262763

Please review and upgrade the org.apache.commons:commons-dbcp2 to the 
latest version 2.5.0 
 
cc: 


> Beam Dependency Update Request: org.apache.commons:commons-dbcp2 2.5.0
> --
>
> Key: BEAM-4900
> URL: https://issues.apache.org/jira/browse/BEAM-4900
> Project: Beam
>  Issue Type: Sub-task
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Assignee: Batkhuyag Batsaikhan
>Priority: Major
>
> 2018-07-25 20:23:31.265674
> Please review and upgrade the org.apache.commons:commons-dbcp2 to the 
> latest version 2.5.0 
>  
> cc: 
> 2018-08-06 12:09:19.186808
> Please review and upgrade the org.apache.commons:commons-dbcp2 to the 
> latest version 2.5.0 
>  
> cc: 
> 2018-08-13 12:09:37.170682
> Please review and upgrade the org.apache.commons:commons-dbcp2 to the 
> latest version 2.5.0 
>  
> cc: 
> 2018-08-20 12:12:21.262763
> Please review and upgrade the org.apache.commons:commons-dbcp2 to the 
> latest version 2.5.0 
>  
> cc: 
> 2018-08-27 12:13:50.267143
> Please review and upgrade the org.apache.commons:commons-dbcp2 to the 
> latest version 2.5.0 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-5182) Beam Dependency Update Request: org.assertj:assertj-core 3.11.0

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-5182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-5182:

Description: 


2018-08-20 12:11:47.500445

Please review and upgrade the org.assertj:assertj-core to the latest 
version 3.11.0 
 
cc: 

2018-08-27 12:13:06.123086

Please review and upgrade the org.assertj:assertj-core to the latest 
version 3.11.0 
 
cc: 

  was:


2018-08-20 12:11:47.500445

Please review and upgrade the org.assertj:assertj-core to the latest 
version 3.11.0 
 
cc: 


> Beam Dependency Update Request: org.assertj:assertj-core 3.11.0
> ---
>
> Key: BEAM-5182
> URL: https://issues.apache.org/jira/browse/BEAM-5182
> Project: Beam
>  Issue Type: Sub-task
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Assignee: Scott Wegner
>Priority: Major
>
> 2018-08-20 12:11:47.500445
> Please review and upgrade the org.assertj:assertj-core to the latest 
> version 3.11.0 
>  
> cc: 
> 2018-08-27 12:13:06.123086
> Please review and upgrade the org.assertj:assertj-core to the latest 
> version 3.11.0 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-4884) Beam Dependency Update Request: biz.aQute:bndlib 2.0.0.20130123-133441

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-4884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-4884:

Description: 


2018-07-25 20:22:10.667692

Please review and upgrade the biz.aQute:bndlib to the latest version 
2.0.0.20130123-133441 
 
cc: 

2018-08-02 11:42:45.184687

Please review and upgrade the biz.aQute:bndlib to the latest version 
2.0.0.20130123-133441 

cc: 

2018-08-06 12:08:44.804597

Please review and upgrade the biz.aQute:bndlib to the latest version 
2.0.0.20130123-133441 
 
cc: 

2018-08-13 12:09:05.718866

Please review and upgrade the biz.aQute:bndlib to the latest version 
2.0.0.20130123-133441 
 
cc: 

2018-08-20 12:11:56.128242

Please review and upgrade the biz.aQute:bndlib to the latest version 
2.0.0.20130123-133441 
 
cc: 

2018-08-27 12:13:22.621235

Please review and upgrade the biz.aQute:bndlib to the latest version 
2.0.0.20130123-133441 
 
cc: 

  was:


2018-07-25 20:22:10.667692

Please review and upgrade the biz.aQute:bndlib to the latest version 
2.0.0.20130123-133441 
 
cc: 

2018-08-02 11:42:45.184687

Please review and upgrade the biz.aQute:bndlib to the latest version 
2.0.0.20130123-133441 

cc: 

2018-08-06 12:08:44.804597

Please review and upgrade the biz.aQute:bndlib to the latest version 
2.0.0.20130123-133441 
 
cc: 

2018-08-13 12:09:05.718866

Please review and upgrade the biz.aQute:bndlib to the latest version 
2.0.0.20130123-133441 
 
cc: 

2018-08-20 12:11:56.128242

Please review and upgrade the biz.aQute:bndlib to the latest version 
2.0.0.20130123-133441 
 
cc: 


> Beam Dependency Update Request: biz.aQute:bndlib 2.0.0.20130123-133441
> --
>
> Key: BEAM-4884
> URL: https://issues.apache.org/jira/browse/BEAM-4884
> Project: Beam
>  Issue Type: Sub-task
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Assignee: Sergey Beryozkin
>Priority: Major
>
> 2018-07-25 20:22:10.667692
> Please review and upgrade the biz.aQute:bndlib to the latest version 
> 2.0.0.20130123-133441 
>  
> cc: 
> 2018-08-02 11:42:45.184687
> Please review and upgrade the biz.aQute:bndlib to the latest version 
> 2.0.0.20130123-133441 
> cc: 
> 2018-08-06 12:08:44.804597
> Please review and upgrade the biz.aQute:bndlib to the latest version 
> 2.0.0.20130123-133441 
>  
> cc: 
> 2018-08-13 12:09:05.718866
> Please review and upgrade the biz.aQute:bndlib to the latest version 
> 2.0.0.20130123-133441 
>  
> cc: 
> 2018-08-20 12:11:56.128242
> Please review and upgrade the biz.aQute:bndlib to the latest version 
> 2.0.0.20130123-133441 
>  
> cc: 
> 2018-08-27 12:13:22.621235
> Please review and upgrade the biz.aQute:bndlib to the latest version 
> 2.0.0.20130123-133441 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-4896) Beam Dependency Update Request: commons-cli:commons-cli 1.4

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-4896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-4896:

Description: 


2018-07-25 20:23:12.608853

Please review and upgrade the commons-cli:commons-cli to the latest 
version 1.4 
 
cc: 

2018-08-20 12:12:10.482763

Please review and upgrade the commons-cli:commons-cli to the latest 
version 1.4 
 
cc: 

2018-08-27 12:13:39.622839

Please review and upgrade the commons-cli:commons-cli to the latest 
version 1.4 
 
cc: 

  was:


2018-07-25 20:23:12.608853

Please review and upgrade the commons-cli:commons-cli to the latest 
version 1.4 
 
cc: 

2018-08-20 12:12:10.482763

Please review and upgrade the commons-cli:commons-cli to the latest 
version 1.4 
 
cc: 


> Beam Dependency Update Request: commons-cli:commons-cli 1.4
> ---
>
> Key: BEAM-4896
> URL: https://issues.apache.org/jira/browse/BEAM-4896
> Project: Beam
>  Issue Type: Sub-task
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Priority: Major
>
> 2018-07-25 20:23:12.608853
> Please review and upgrade the commons-cli:commons-cli to the latest 
> version 1.4 
>  
> cc: 
> 2018-08-20 12:12:10.482763
> Please review and upgrade the commons-cli:commons-cli to the latest 
> version 1.4 
>  
> cc: 
> 2018-08-27 12:13:39.622839
> Please review and upgrade the commons-cli:commons-cli to the latest 
> version 1.4 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (BEAM-5224) Beam Dependency Update Request: com.gradle:build-scan-plugin 1.16

[Beam JIRA Bot (JIRA)]

Beam JIRA Bot created BEAM-5224:
---

 Summary: Beam Dependency Update Request: 
com.gradle:build-scan-plugin 1.16
 Key: BEAM-5224
 URL: https://issues.apache.org/jira/browse/BEAM-5224
 Project: Beam
  Issue Type: Sub-task
  Components: dependencies
Reporter: Beam JIRA Bot
Assignee: Scott Wegner




2018-08-27 12:13:32.215540

Please review and upgrade the com.gradle:build-scan-plugin to the 
latest version 1.16 
 
cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-4874) Beam Dependency Update Request: com.google.auto.service:auto-service 1.0-rc4

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-4874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-4874:

Description: 


2018-07-25 20:21:08.597317

Please review and upgrade the com.google.auto.service:auto-service to 
the latest version 1.0-rc4 
 
cc: 

2018-08-06 12:08:14.189802

Please review and upgrade the com.google.auto.service:auto-service to 
the latest version 1.0-rc4 
 
cc: 

2018-08-13 12:08:37.495569

Please review and upgrade the com.google.auto.service:auto-service to 
the latest version 1.0-rc4 
 
cc: 

2018-08-20 12:11:49.688170

Please review and upgrade the com.google.auto.service:auto-service to 
the latest version 1.0-rc4 
 
cc: 

2018-08-27 12:13:11.448132

Please review and upgrade the com.google.auto.service:auto-service to 
the latest version 1.0-rc4 
 
cc: 

  was:


2018-07-25 20:21:08.597317

Please review and upgrade the com.google.auto.service:auto-service to 
the latest version 1.0-rc4 
 
cc: 

2018-08-06 12:08:14.189802

Please review and upgrade the com.google.auto.service:auto-service to 
the latest version 1.0-rc4 
 
cc: 

2018-08-13 12:08:37.495569

Please review and upgrade the com.google.auto.service:auto-service to 
the latest version 1.0-rc4 
 
cc: 

2018-08-20 12:11:49.688170

Please review and upgrade the com.google.auto.service:auto-service to 
the latest version 1.0-rc4 
 
cc: 


> Beam Dependency Update Request: com.google.auto.service:auto-service 1.0-rc4
> 
>
> Key: BEAM-4874
> URL: https://issues.apache.org/jira/browse/BEAM-4874
> Project: Beam
>  Issue Type: Sub-task
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Assignee: Scott Wegner
>Priority: Major
>
> 2018-07-25 20:21:08.597317
> Please review and upgrade the com.google.auto.service:auto-service to 
> the latest version 1.0-rc4 
>  
> cc: 
> 2018-08-06 12:08:14.189802
> Please review and upgrade the com.google.auto.service:auto-service to 
> the latest version 1.0-rc4 
>  
> cc: 
> 2018-08-13 12:08:37.495569
> Please review and upgrade the com.google.auto.service:auto-service to 
> the latest version 1.0-rc4 
>  
> cc: 
> 2018-08-20 12:11:49.688170
> Please review and upgrade the com.google.auto.service:auto-service to 
> the latest version 1.0-rc4 
>  
> cc: 
> 2018-08-27 12:13:11.448132
> Please review and upgrade the com.google.auto.service:auto-service to 
> the latest version 1.0-rc4 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-4902) Beam Dependency Update Request: com.typesafe:config 1.3.3

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-4902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-4902:

Description: 


2018-07-25 20:23:40.219872

Please review and upgrade the com.typesafe:config to the latest version 
1.3.3 
 
cc: 

2018-08-20 12:12:26.722997

Please review and upgrade the com.typesafe:config to the latest version 
1.3.3 
 
cc: 

2018-08-27 12:13:55.567873

Please review and upgrade the com.typesafe:config to the latest version 
1.3.3 
 
cc: 

  was:


2018-07-25 20:23:40.219872

Please review and upgrade the com.typesafe:config to the latest version 
1.3.3 
 
cc: 

2018-08-20 12:12:26.722997

Please review and upgrade the com.typesafe:config to the latest version 
1.3.3 
 
cc: 


> Beam Dependency Update Request: com.typesafe:config 1.3.3
> -
>
> Key: BEAM-4902
> URL: https://issues.apache.org/jira/browse/BEAM-4902
> Project: Beam
>  Issue Type: Sub-task
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Priority: Major
>
> 2018-07-25 20:23:40.219872
> Please review and upgrade the com.typesafe:config to the latest 
> version 1.3.3 
>  
> cc: 
> 2018-08-20 12:12:26.722997
> Please review and upgrade the com.typesafe:config to the latest 
> version 1.3.3 
>  
> cc: 
> 2018-08-27 12:13:55.567873
> Please review and upgrade the com.typesafe:config to the latest 
> version 1.3.3 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-4898) Beam Dependency Update Request: commons-codec:commons-codec 1.11

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-4898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-4898:

Description: 


2018-07-25 20:23:22.049227

Please review and upgrade the commons-codec:commons-codec to the latest 
version 1.11 
 
cc: 

2018-08-20 12:12:15.872932

Please review and upgrade the commons-codec:commons-codec to the latest 
version 1.11 
 
cc: 

2018-08-27 12:13:44.991242

Please review and upgrade the commons-codec:commons-codec to the latest 
version 1.11 
 
cc: 

  was:


2018-07-25 20:23:22.049227

Please review and upgrade the commons-codec:commons-codec to the latest 
version 1.11 
 
cc: 

2018-08-20 12:12:15.872932

Please review and upgrade the commons-codec:commons-codec to the latest 
version 1.11 
 
cc: 


> Beam Dependency Update Request: commons-codec:commons-codec 1.11
> 
>
> Key: BEAM-4898
> URL: https://issues.apache.org/jira/browse/BEAM-4898
> Project: Beam
>  Issue Type: Sub-task
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Priority: Major
>
> 2018-07-25 20:23:22.049227
> Please review and upgrade the commons-codec:commons-codec to the 
> latest version 1.11 
>  
> cc: 
> 2018-08-20 12:12:15.872932
> Please review and upgrade the commons-codec:commons-codec to the 
> latest version 1.11 
>  
> cc: 
> 2018-08-27 12:13:44.991242
> Please review and upgrade the commons-codec:commons-codec to the 
> latest version 1.11 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-5083) Beam Dependency Update Request: org.apache.cassandra:cassandra-all 3.11.3

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-5083:

Description: 


2018-08-06 12:09:03.144998

Please review and upgrade the org.apache.cassandra:cassandra-all to the 
latest version 3.11.3 
 
cc: 

2018-08-13 12:09:18.120427

Please review and upgrade the org.apache.cassandra:cassandra-all to the 
latest version 3.11.3 
 
cc: 

2018-08-20 12:12:04.749671

Please review and upgrade the org.apache.cassandra:cassandra-all to the 
latest version 3.11.3 
 
cc: 

2018-08-27 12:13:34.037181

Please review and upgrade the org.apache.cassandra:cassandra-all to the 
latest version 3.11.3 
 
cc: 

  was:


2018-08-06 12:09:03.144998

Please review and upgrade the org.apache.cassandra:cassandra-all to the 
latest version 3.11.3 
 
cc: 

2018-08-13 12:09:18.120427

Please review and upgrade the org.apache.cassandra:cassandra-all to the 
latest version 3.11.3 
 
cc: 

2018-08-20 12:12:04.749671

Please review and upgrade the org.apache.cassandra:cassandra-all to the 
latest version 3.11.3 
 
cc: 


> Beam Dependency Update Request: org.apache.cassandra:cassandra-all 3.11.3
> -
>
> Key: BEAM-5083
> URL: https://issues.apache.org/jira/browse/BEAM-5083
> Project: Beam
>  Issue Type: Sub-task
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Assignee: Batkhuyag Batsaikhan
>Priority: Major
>
> 2018-08-06 12:09:03.144998
> Please review and upgrade the org.apache.cassandra:cassandra-all to 
> the latest version 3.11.3 
>  
> cc: 
> 2018-08-13 12:09:18.120427
> Please review and upgrade the org.apache.cassandra:cassandra-all to 
> the latest version 3.11.3 
>  
> cc: 
> 2018-08-20 12:12:04.749671
> Please review and upgrade the org.apache.cassandra:cassandra-all to 
> the latest version 3.11.3 
>  
> cc: 
> 2018-08-27 12:13:34.037181
> Please review and upgrade the org.apache.cassandra:cassandra-all to 
> the latest version 3.11.3 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (BEAM-5229) Beam Dependency Update Request: com.commercehub.gradle.plugin:gradle-avro-plugin 0.15.0

[Beam JIRA Bot (JIRA)]

Beam JIRA Bot created BEAM-5229:
---

 Summary: Beam Dependency Update Request: 
com.commercehub.gradle.plugin:gradle-avro-plugin 0.15.0
 Key: BEAM-5229
 URL: https://issues.apache.org/jira/browse/BEAM-5229
 Project: Beam
  Issue Type: Sub-task
  Components: dependencies
Reporter: Beam JIRA Bot
Assignee: Scott Wegner




2018-08-27 12:14:32.746008

Please review and upgrade the 
com.commercehub.gradle.plugin:gradle-avro-plugin to the latest version 0.15.0 
 
cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (BEAM-5228) Beam Dependency Update Request: org.elasticsearch.test:framework 6.4.0

[Beam JIRA Bot (JIRA)]

Beam JIRA Bot created BEAM-5228:
---

 Summary: Beam Dependency Update Request: 
org.elasticsearch.test:framework 6.4.0
 Key: BEAM-5228
 URL: https://issues.apache.org/jira/browse/BEAM-5228
 Project: Beam
  Issue Type: Sub-task
  Components: dependencies
Reporter: Beam JIRA Bot
Assignee: Etienne Chauchot




2018-08-27 12:14:18.479647

Please review and upgrade the org.elasticsearch.test:framework to the 
latest version 6.4.0 
 
cc: [~timrobertson100], 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (BEAM-5225) Beam Dependency Update Request: org.elasticsearch:elasticsearch 6.4.0

[Beam JIRA Bot (JIRA)]

Beam JIRA Bot created BEAM-5225:
---

 Summary: Beam Dependency Update Request: 
org.elasticsearch:elasticsearch 6.4.0
 Key: BEAM-5225
 URL: https://issues.apache.org/jira/browse/BEAM-5225
 Project: Beam
  Issue Type: Sub-task
  Components: dependencies
Reporter: Beam JIRA Bot
Assignee: Etienne Chauchot




2018-08-27 12:14:11.978974

Please review and upgrade the org.elasticsearch:elasticsearch to the 
latest version 6.4.0 
 
cc: [~timrobertson100], 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (BEAM-5226) Beam Dependency Update Request: org.elasticsearch:elasticsearch-hadoop 6.4.0

[Beam JIRA Bot (JIRA)]

Beam JIRA Bot created BEAM-5226:
---

 Summary: Beam Dependency Update Request: 
org.elasticsearch:elasticsearch-hadoop 6.4.0
 Key: BEAM-5226
 URL: https://issues.apache.org/jira/browse/BEAM-5226
 Project: Beam
  Issue Type: Sub-task
  Components: dependencies
Reporter: Beam JIRA Bot
Assignee: Tim Robertson




2018-08-27 12:14:13.752280

Please review and upgrade the org.elasticsearch:elasticsearch-hadoop to 
the latest version 6.4.0 
 
cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-4924) Beam Dependency Update Request: net.ltgt.gradle:gradle-apt-plugin 0.18

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-4924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-4924:

Description: 


2018-07-25 20:25:41.106147

Please review and upgrade the net.ltgt.gradle:gradle-apt-plugin to the 
latest version 0.18 
 
cc: 

2018-08-06 12:10:36.889118

Please review and upgrade the net.ltgt.gradle:gradle-apt-plugin to the 
latest version 0.18 
 
cc: 

2018-08-13 12:12:03.418854

Please review and upgrade the net.ltgt.gradle:gradle-apt-plugin to the 
latest version 0.18 
 
cc: 

2018-08-20 12:13:09.469810

Please review and upgrade the net.ltgt.gradle:gradle-apt-plugin to the 
latest version 0.18 
 
cc: 

2018-08-27 12:14:23.504740

Please review and upgrade the net.ltgt.gradle:gradle-apt-plugin to the 
latest version 0.18 
 
cc: 

  was:


2018-07-25 20:25:41.106147

Please review and upgrade the net.ltgt.gradle:gradle-apt-plugin to the 
latest version 0.18 
 
cc: 

2018-08-06 12:10:36.889118

Please review and upgrade the net.ltgt.gradle:gradle-apt-plugin to the 
latest version 0.18 
 
cc: 

2018-08-13 12:12:03.418854

Please review and upgrade the net.ltgt.gradle:gradle-apt-plugin to the 
latest version 0.18 
 
cc: 

2018-08-20 12:13:09.469810

Please review and upgrade the net.ltgt.gradle:gradle-apt-plugin to the 
latest version 0.18 
 
cc: 


> Beam Dependency Update Request: net.ltgt.gradle:gradle-apt-plugin 0.18
> --
>
> Key: BEAM-4924
> URL: https://issues.apache.org/jira/browse/BEAM-4924
> Project: Beam
>  Issue Type: Sub-task
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Priority: Major
>
> 2018-07-25 20:25:41.106147
> Please review and upgrade the net.ltgt.gradle:gradle-apt-plugin to 
> the latest version 0.18 
>  
> cc: 
> 2018-08-06 12:10:36.889118
> Please review and upgrade the net.ltgt.gradle:gradle-apt-plugin to 
> the latest version 0.18 
>  
> cc: 
> 2018-08-13 12:12:03.418854
> Please review and upgrade the net.ltgt.gradle:gradle-apt-plugin to 
> the latest version 0.18 
>  
> cc: 
> 2018-08-20 12:13:09.469810
> Please review and upgrade the net.ltgt.gradle:gradle-apt-plugin to 
> the latest version 0.18 
>  
> cc: 
> 2018-08-27 12:14:23.504740
> Please review and upgrade the net.ltgt.gradle:gradle-apt-plugin to 
> the latest version 0.18 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (BEAM-5227) Beam Dependency Update Request: org.elasticsearch.client:elasticsearch-rest-client 6.4.0

[Beam JIRA Bot (JIRA)]

Beam JIRA Bot created BEAM-5227:
---

 Summary: Beam Dependency Update Request: 
org.elasticsearch.client:elasticsearch-rest-client 6.4.0
 Key: BEAM-5227
 URL: https://issues.apache.org/jira/browse/BEAM-5227
 Project: Beam
  Issue Type: Sub-task
  Components: dependencies
Reporter: Beam JIRA Bot
Assignee: Etienne Chauchot




2018-08-27 12:14:15.615310

Please review and upgrade the 
org.elasticsearch.client:elasticsearch-rest-client to the latest version 6.4.0 
 
cc: [~timrobertson100], 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-5085) Beam Dependency Update Request: com.google.guava:guava 26.0-jre

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-5085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-5085:

Description: 


2018-08-06 12:11:45.524503

Please review and upgrade the com.google.guava:guava to the latest 
version 26.0-jre 
 
cc: 

2018-08-13 12:13:13.070372

Please review and upgrade the com.google.guava:guava to the latest 
version 26.0-jre 
 
cc: 

2018-08-20 12:13:53.326708

Please review and upgrade the com.google.guava:guava to the latest 
version 26.0-jre 
 
cc: 

2018-08-27 12:14:56.293907

Please review and upgrade the com.google.guava:guava to the latest 
version 26.0-jre 
 
cc: 

  was:


2018-08-06 12:11:45.524503

Please review and upgrade the com.google.guava:guava to the latest 
version 26.0-jre 
 
cc: 

2018-08-13 12:13:13.070372

Please review and upgrade the com.google.guava:guava to the latest 
version 26.0-jre 
 
cc: 

2018-08-20 12:13:53.326708

Please review and upgrade the com.google.guava:guava to the latest 
version 26.0-jre 
 
cc: 


> Beam Dependency Update Request: com.google.guava:guava 26.0-jre
> ---
>
> Key: BEAM-5085
> URL: https://issues.apache.org/jira/browse/BEAM-5085
> Project: Beam
>  Issue Type: Sub-task
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Priority: Major
>
> 2018-08-06 12:11:45.524503
> Please review and upgrade the com.google.guava:guava to the latest 
> version 26.0-jre 
>  
> cc: 
> 2018-08-13 12:13:13.070372
> Please review and upgrade the com.google.guava:guava to the latest 
> version 26.0-jre 
>  
> cc: 
> 2018-08-20 12:13:53.326708
> Please review and upgrade the com.google.guava:guava to the latest 
> version 26.0-jre 
>  
> cc: 
> 2018-08-27 12:14:56.293907
> Please review and upgrade the com.google.guava:guava to the latest 
> version 26.0-jre 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-4904) Beam Dependency Update Request: de.flapdoodle.embed:de.flapdoodle.embed.mongo 2.1.1

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-4904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-4904:

Description: 


2018-07-25 20:23:49.911490

Please review and upgrade the 
de.flapdoodle.embed:de.flapdoodle.embed.mongo to the latest version 2.1.1 
 
cc: 

2018-08-06 12:09:30.976479

Please review and upgrade the 
de.flapdoodle.embed:de.flapdoodle.embed.mongo to the latest version 2.1.1 
 
cc: 

2018-08-13 12:09:48.188897

Please review and upgrade the 
de.flapdoodle.embed:de.flapdoodle.embed.mongo to the latest version 2.1.1 
 
cc: 

2018-08-20 12:12:32.344889

Please review and upgrade the 
de.flapdoodle.embed:de.flapdoodle.embed.mongo to the latest version 2.1.1 
 
cc: 

2018-08-27 12:14:00.846640

Please review and upgrade the 
de.flapdoodle.embed:de.flapdoodle.embed.mongo to the latest version 2.1.1 
 
cc: 

  was:


2018-07-25 20:23:49.911490

Please review and upgrade the 
de.flapdoodle.embed:de.flapdoodle.embed.mongo to the latest version 2.1.1 
 
cc: 

2018-08-06 12:09:30.976479

Please review and upgrade the 
de.flapdoodle.embed:de.flapdoodle.embed.mongo to the latest version 2.1.1 
 
cc: 

2018-08-13 12:09:48.188897

Please review and upgrade the 
de.flapdoodle.embed:de.flapdoodle.embed.mongo to the latest version 2.1.1 
 
cc: 

2018-08-20 12:12:32.344889

Please review and upgrade the 
de.flapdoodle.embed:de.flapdoodle.embed.mongo to the latest version 2.1.1 
 
cc: 


> Beam Dependency Update Request: de.flapdoodle.embed:de.flapdoodle.embed.mongo 
> 2.1.1
> ---
>
> Key: BEAM-4904
> URL: https://issues.apache.org/jira/browse/BEAM-4904
> Project: Beam
>  Issue Type: Sub-task
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Assignee: Chamikara Jayalath
>Priority: Major
>
> 2018-07-25 20:23:49.911490
> Please review and upgrade the 
> de.flapdoodle.embed:de.flapdoodle.embed.mongo to the latest version 2.1.1 
>  
> cc: 
> 2018-08-06 12:09:30.976479
> Please review and upgrade the 
> de.flapdoodle.embed:de.flapdoodle.embed.mongo to the latest version 2.1.1 
>  
> cc: 
> 2018-08-13 12:09:48.188897
> Please review and upgrade the 
> de.flapdoodle.embed:de.flapdoodle.embed.mongo to the latest version 2.1.1 
>  
> cc: 
> 2018-08-20 12:12:32.344889
> Please review and upgrade the 
> de.flapdoodle.embed:de.flapdoodle.embed.mongo to the latest version 2.1.1 
>  
> cc: 
> 2018-08-27 12:14:00.846640
> Please review and upgrade the 
> de.flapdoodle.embed:de.flapdoodle.embed.mongo to the latest version 2.1.1 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-4905) Beam Dependency Update Request: de.flapdoodle.embed:de.flapdoodle.embed.process 2.0.5

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-4905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-4905:

Description: 


2018-07-25 20:23:58.022170

Please review and upgrade the 
de.flapdoodle.embed:de.flapdoodle.embed.process to the latest version 2.0.5 
 
cc: 

2018-08-06 12:09:39.047955

Please review and upgrade the 
de.flapdoodle.embed:de.flapdoodle.embed.process to the latest version 2.0.5 
 
cc: 

2018-08-13 12:09:56.445368

Please review and upgrade the 
de.flapdoodle.embed:de.flapdoodle.embed.process to the latest version 2.0.5 
 
cc: 

2018-08-20 12:12:37.728222

Please review and upgrade the 
de.flapdoodle.embed:de.flapdoodle.embed.process to the latest version 2.0.5 
 
cc: 

2018-08-27 12:14:06.408790

Please review and upgrade the 
de.flapdoodle.embed:de.flapdoodle.embed.process to the latest version 2.0.5 
 
cc: 

  was:


2018-07-25 20:23:58.022170

Please review and upgrade the 
de.flapdoodle.embed:de.flapdoodle.embed.process to the latest version 2.0.5 
 
cc: 

2018-08-06 12:09:39.047955

Please review and upgrade the 
de.flapdoodle.embed:de.flapdoodle.embed.process to the latest version 2.0.5 
 
cc: 

2018-08-13 12:09:56.445368

Please review and upgrade the 
de.flapdoodle.embed:de.flapdoodle.embed.process to the latest version 2.0.5 
 
cc: 

2018-08-20 12:12:37.728222

Please review and upgrade the 
de.flapdoodle.embed:de.flapdoodle.embed.process to the latest version 2.0.5 
 
cc: 


> Beam Dependency Update Request: 
> de.flapdoodle.embed:de.flapdoodle.embed.process 2.0.5
> -
>
> Key: BEAM-4905
> URL: https://issues.apache.org/jira/browse/BEAM-4905
> Project: Beam
>  Issue Type: Sub-task
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Assignee: Chamikara Jayalath
>Priority: Major
>
> 2018-07-25 20:23:58.022170
> Please review and upgrade the 
> de.flapdoodle.embed:de.flapdoodle.embed.process to the latest version 2.0.5 
>  
> cc: 
> 2018-08-06 12:09:39.047955
> Please review and upgrade the 
> de.flapdoodle.embed:de.flapdoodle.embed.process to the latest version 2.0.5 
>  
> cc: 
> 2018-08-13 12:09:56.445368
> Please review and upgrade the 
> de.flapdoodle.embed:de.flapdoodle.embed.process to the latest version 2.0.5 
>  
> cc: 
> 2018-08-20 12:12:37.728222
> Please review and upgrade the 
> de.flapdoodle.embed:de.flapdoodle.embed.process to the latest version 2.0.5 
>  
> cc: 
> 2018-08-27 12:14:06.408790
> Please review and upgrade the 
> de.flapdoodle.embed:de.flapdoodle.embed.process to the latest version 2.0.5 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-4947) Beam Dependency Update Request: com.google.code.gson:gson 2.8.5

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-4947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-4947:

Description: 


2018-07-25 20:27:55.719554

Please review and upgrade the com.google.code.gson:gson to the latest 
version 2.8.5 
 
cc: 

2018-08-20 12:13:47.846594

Please review and upgrade the com.google.code.gson:gson to the latest 
version 2.8.5 
 
cc: 

2018-08-27 12:14:50.921633

Please review and upgrade the com.google.code.gson:gson to the latest 
version 2.8.5 
 
cc: 

  was:


2018-07-25 20:27:55.719554

Please review and upgrade the com.google.code.gson:gson to the latest 
version 2.8.5 
 
cc: 

2018-08-20 12:13:47.846594

Please review and upgrade the com.google.code.gson:gson to the latest 
version 2.8.5 
 
cc: 


> Beam Dependency Update Request: com.google.code.gson:gson 2.8.5
> ---
>
> Key: BEAM-4947
> URL: https://issues.apache.org/jira/browse/BEAM-4947
> Project: Beam
>  Issue Type: Sub-task
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Priority: Major
>
> 2018-07-25 20:27:55.719554
> Please review and upgrade the com.google.code.gson:gson to the latest 
> version 2.8.5 
>  
> cc: 
> 2018-08-20 12:13:47.846594
> Please review and upgrade the com.google.code.gson:gson to the latest 
> version 2.8.5 
>  
> cc: 
> 2018-08-27 12:14:50.921633
> Please review and upgrade the com.google.code.gson:gson to the latest 
> version 2.8.5 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (BEAM-5230) Beam Dependency Update Request: org.apache.hive:hive-cli 3.1.0

[Beam JIRA Bot (JIRA)]

Beam JIRA Bot created BEAM-5230:
---

 Summary: Beam Dependency Update Request: org.apache.hive:hive-cli 
3.1.0
 Key: BEAM-5230
 URL: https://issues.apache.org/jira/browse/BEAM-5230
 Project: Beam
  Issue Type: Sub-task
  Components: dependencies
Reporter: Beam JIRA Bot
Assignee: Tim Robertson




2018-08-27 12:15:34.608436

Please review and upgrade the org.apache.hive:hive-cli to the latest 
version 3.1.0 
 
cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (BEAM-5234) Beam Dependency Update Request: org.slf4j:jcl-over-slf4j 1.8.0-beta2

[Beam JIRA Bot (JIRA)]

Beam JIRA Bot created BEAM-5234:
---

 Summary: Beam Dependency Update Request: org.slf4j:jcl-over-slf4j 
1.8.0-beta2
 Key: BEAM-5234
 URL: https://issues.apache.org/jira/browse/BEAM-5234
 Project: Beam
  Issue Type: Sub-task
  Components: dependencies
Reporter: Beam JIRA Bot




2018-08-27 12:15:47.239668

Please review and upgrade the org.slf4j:jcl-over-slf4j to the latest 
version 1.8.0-beta2 
 
cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-4973) Beam Dependency Update Request: net.java.dev.jna:jna 4.5.2

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-4973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-4973:

Description: 


2018-07-25 20:30:49.608065

Please review and upgrade the net.java.dev.jna:jna to the latest 
version 4.5.2 
 
cc: 

2018-08-06 12:13:27.668457

Please review and upgrade the net.java.dev.jna:jna to the latest 
version 4.5.2 
 
cc: 

2018-08-13 12:14:52.224671

Please review and upgrade the net.java.dev.jna:jna to the latest 
version 4.5.2 
 
cc: 

2018-08-20 12:15:12.578899

Please review and upgrade the net.java.dev.jna:jna to the latest 
version 4.5.2 
 
cc: 

2018-08-27 12:15:49.579735

Please review and upgrade the net.java.dev.jna:jna to the latest 
version 4.5.2 
 
cc: 

  was:


2018-07-25 20:30:49.608065

Please review and upgrade the net.java.dev.jna:jna to the latest 
version 4.5.2 
 
cc: 

2018-08-06 12:13:27.668457

Please review and upgrade the net.java.dev.jna:jna to the latest 
version 4.5.2 
 
cc: 

2018-08-13 12:14:52.224671

Please review and upgrade the net.java.dev.jna:jna to the latest 
version 4.5.2 
 
cc: 

2018-08-20 12:15:12.578899

Please review and upgrade the net.java.dev.jna:jna to the latest 
version 4.5.2 
 
cc: 


> Beam Dependency Update Request: net.java.dev.jna:jna 4.5.2
> --
>
> Key: BEAM-4973
> URL: https://issues.apache.org/jira/browse/BEAM-4973
> Project: Beam
>  Issue Type: Sub-task
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Priority: Major
>
> 2018-07-25 20:30:49.608065
> Please review and upgrade the net.java.dev.jna:jna to the latest 
> version 4.5.2 
>  
> cc: 
> 2018-08-06 12:13:27.668457
> Please review and upgrade the net.java.dev.jna:jna to the latest 
> version 4.5.2 
>  
> cc: 
> 2018-08-13 12:14:52.224671
> Please review and upgrade the net.java.dev.jna:jna to the latest 
> version 4.5.2 
>  
> cc: 
> 2018-08-20 12:15:12.578899
> Please review and upgrade the net.java.dev.jna:jna to the latest 
> version 4.5.2 
>  
> cc: 
> 2018-08-27 12:15:49.579735
> Please review and upgrade the net.java.dev.jna:jna to the latest 
> version 4.5.2 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-4951) Beam Dependency Update Request: org.apache.hbase:hbase-common 2.1.0

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-4951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-4951:

Description: 


2018-07-25 20:28:15.136904

Please review and upgrade the org.apache.hbase:hbase-common to the 
latest version 2.1.0 
 
cc: 

2018-08-06 12:11:50.186985

Please review and upgrade the org.apache.hbase:hbase-common to the 
latest version 2.1.0 
 
cc: 

2018-08-13 12:13:21.936469

Please review and upgrade the org.apache.hbase:hbase-common to the 
latest version 2.1.0 
 
cc: 

2018-08-20 12:13:58.982374

Please review and upgrade the org.apache.hbase:hbase-common to the 
latest version 2.1.0 
 
cc: 

2018-08-27 12:15:01.760143

Please review and upgrade the org.apache.hbase:hbase-common to the 
latest version 2.1.0 
 
cc: 

  was:


2018-07-25 20:28:15.136904

Please review and upgrade the org.apache.hbase:hbase-common to the 
latest version 2.1.0 
 
cc: 

2018-08-06 12:11:50.186985

Please review and upgrade the org.apache.hbase:hbase-common to the 
latest version 2.1.0 
 
cc: 

2018-08-13 12:13:21.936469

Please review and upgrade the org.apache.hbase:hbase-common to the 
latest version 2.1.0 
 
cc: 

2018-08-20 12:13:58.982374

Please review and upgrade the org.apache.hbase:hbase-common to the 
latest version 2.1.0 
 
cc: 


> Beam Dependency Update Request: org.apache.hbase:hbase-common 2.1.0
> ---
>
> Key: BEAM-4951
> URL: https://issues.apache.org/jira/browse/BEAM-4951
> Project: Beam
>  Issue Type: Sub-task
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Assignee: Tim Robertson
>Priority: Major
>
> 2018-07-25 20:28:15.136904
> Please review and upgrade the org.apache.hbase:hbase-common to the 
> latest version 2.1.0 
>  
> cc: 
> 2018-08-06 12:11:50.186985
> Please review and upgrade the org.apache.hbase:hbase-common to the 
> latest version 2.1.0 
>  
> cc: 
> 2018-08-13 12:13:21.936469
> Please review and upgrade the org.apache.hbase:hbase-common to the 
> latest version 2.1.0 
>  
> cc: 
> 2018-08-20 12:13:58.982374
> Please review and upgrade the org.apache.hbase:hbase-common to the 
> latest version 2.1.0 
>  
> cc: 
> 2018-08-27 12:15:01.760143
> Please review and upgrade the org.apache.hbase:hbase-common to the 
> latest version 2.1.0 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (BEAM-5232) Beam Dependency Update Request: org.apache.hive:hive-exec 3.1.0

[Beam JIRA Bot (JIRA)]

Beam JIRA Bot created BEAM-5232:
---

 Summary: Beam Dependency Update Request: org.apache.hive:hive-exec 
3.1.0
 Key: BEAM-5232
 URL: https://issues.apache.org/jira/browse/BEAM-5232
 Project: Beam
  Issue Type: Sub-task
  Components: dependencies
Reporter: Beam JIRA Bot
Assignee: Tim Robertson




2018-08-27 12:15:38.398485

Please review and upgrade the org.apache.hive:hive-exec to the latest 
version 3.1.0 
 
cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-4969) Beam Dependency Update Request: net.java.dev.javacc:javacc 7.0.3

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-4969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-4969:

Description: 


2018-07-25 20:30:28.956455

Please review and upgrade the net.java.dev.javacc:javacc to the latest 
version 7.0.3 
 
cc: 

2018-08-06 12:13:11.448519

Please review and upgrade the net.java.dev.javacc:javacc to the latest 
version 7.0.3 
 
cc: 

2018-08-13 12:14:40.280651

Please review and upgrade the net.java.dev.javacc:javacc to the latest 
version 7.0.3 
 
cc: 

2018-08-20 12:15:06.138843

Please review and upgrade the net.java.dev.javacc:javacc to the latest 
version 7.0.3 
 
cc: 

2018-08-27 12:15:41.995037

Please review and upgrade the net.java.dev.javacc:javacc to the latest 
version 7.0.3 
 
cc: 

  was:


2018-07-25 20:30:28.956455

Please review and upgrade the net.java.dev.javacc:javacc to the latest 
version 7.0.3 
 
cc: 

2018-08-06 12:13:11.448519

Please review and upgrade the net.java.dev.javacc:javacc to the latest 
version 7.0.3 
 
cc: 

2018-08-13 12:14:40.280651

Please review and upgrade the net.java.dev.javacc:javacc to the latest 
version 7.0.3 
 
cc: 

2018-08-20 12:15:06.138843

Please review and upgrade the net.java.dev.javacc:javacc to the latest 
version 7.0.3 
 
cc: 


> Beam Dependency Update Request: net.java.dev.javacc:javacc 7.0.3
> 
>
> Key: BEAM-4969
> URL: https://issues.apache.org/jira/browse/BEAM-4969
> Project: Beam
>  Issue Type: Sub-task
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Priority: Major
>
> 2018-07-25 20:30:28.956455
> Please review and upgrade the net.java.dev.javacc:javacc to the 
> latest version 7.0.3 
>  
> cc: 
> 2018-08-06 12:13:11.448519
> Please review and upgrade the net.java.dev.javacc:javacc to the 
> latest version 7.0.3 
>  
> cc: 
> 2018-08-13 12:14:40.280651
> Please review and upgrade the net.java.dev.javacc:javacc to the 
> latest version 7.0.3 
>  
> cc: 
> 2018-08-20 12:15:06.138843
> Please review and upgrade the net.java.dev.javacc:javacc to the 
> latest version 7.0.3 
>  
> cc: 
> 2018-08-27 12:15:41.995037
> Please review and upgrade the net.java.dev.javacc:javacc to the 
> latest version 7.0.3 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-4952) Beam Dependency Update Request: org.apache.hbase:hbase-hadoop-compat 2.1.0

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-4952:

Description: 


2018-07-25 20:28:24.987897

Please review and upgrade the org.apache.hbase:hbase-hadoop-compat to 
the latest version 2.1.0 
 
cc: 

2018-08-06 12:11:58.406173

Please review and upgrade the org.apache.hbase:hbase-hadoop-compat to 
the latest version 2.1.0 
 
cc: 

2018-08-13 12:13:31.045787

Please review and upgrade the org.apache.hbase:hbase-hadoop-compat to 
the latest version 2.1.0 
 
cc: 

2018-08-20 12:14:04.735400

Please review and upgrade the org.apache.hbase:hbase-hadoop-compat to 
the latest version 2.1.0 
 
cc: 

2018-08-27 12:15:07.483727

Please review and upgrade the org.apache.hbase:hbase-hadoop-compat to 
the latest version 2.1.0 
 
cc: 

  was:


2018-07-25 20:28:24.987897

Please review and upgrade the org.apache.hbase:hbase-hadoop-compat to 
the latest version 2.1.0 
 
cc: 

2018-08-06 12:11:58.406173

Please review and upgrade the org.apache.hbase:hbase-hadoop-compat to 
the latest version 2.1.0 
 
cc: 

2018-08-13 12:13:31.045787

Please review and upgrade the org.apache.hbase:hbase-hadoop-compat to 
the latest version 2.1.0 
 
cc: 

2018-08-20 12:14:04.735400

Please review and upgrade the org.apache.hbase:hbase-hadoop-compat to 
the latest version 2.1.0 
 
cc: 


> Beam Dependency Update Request: org.apache.hbase:hbase-hadoop-compat 2.1.0
> --
>
> Key: BEAM-4952
> URL: https://issues.apache.org/jira/browse/BEAM-4952
> Project: Beam
>  Issue Type: Sub-task
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Assignee: Tim Robertson
>Priority: Major
>
> 2018-07-25 20:28:24.987897
> Please review and upgrade the org.apache.hbase:hbase-hadoop-compat to 
> the latest version 2.1.0 
>  
> cc: 
> 2018-08-06 12:11:58.406173
> Please review and upgrade the org.apache.hbase:hbase-hadoop-compat to 
> the latest version 2.1.0 
>  
> cc: 
> 2018-08-13 12:13:31.045787
> Please review and upgrade the org.apache.hbase:hbase-hadoop-compat to 
> the latest version 2.1.0 
>  
> cc: 
> 2018-08-20 12:14:04.735400
> Please review and upgrade the org.apache.hbase:hbase-hadoop-compat to 
> the latest version 2.1.0 
>  
> cc: 
> 2018-08-27 12:15:07.483727
> Please review and upgrade the org.apache.hbase:hbase-hadoop-compat to 
> the latest version 2.1.0 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-4953) Beam Dependency Update Request: org.apache.hbase:hbase-hadoop2-compat 2.1.0

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-4953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-4953:

Description: 


2018-07-25 20:28:33.621577

Please review and upgrade the org.apache.hbase:hbase-hadoop2-compat to 
the latest version 2.1.0 
 
cc: 

2018-08-06 12:12:06.214820

Please review and upgrade the org.apache.hbase:hbase-hadoop2-compat to 
the latest version 2.1.0 
 
cc: 

2018-08-13 12:13:40.056300

Please review and upgrade the org.apache.hbase:hbase-hadoop2-compat to 
the latest version 2.1.0 
 
cc: 

2018-08-20 12:14:10.305463

Please review and upgrade the org.apache.hbase:hbase-hadoop2-compat to 
the latest version 2.1.0 
 
cc: 

2018-08-27 12:15:12.871124

Please review and upgrade the org.apache.hbase:hbase-hadoop2-compat to 
the latest version 2.1.0 
 
cc: 

  was:


2018-07-25 20:28:33.621577

Please review and upgrade the org.apache.hbase:hbase-hadoop2-compat to 
the latest version 2.1.0 
 
cc: 

2018-08-06 12:12:06.214820

Please review and upgrade the org.apache.hbase:hbase-hadoop2-compat to 
the latest version 2.1.0 
 
cc: 

2018-08-13 12:13:40.056300

Please review and upgrade the org.apache.hbase:hbase-hadoop2-compat to 
the latest version 2.1.0 
 
cc: 

2018-08-20 12:14:10.305463

Please review and upgrade the org.apache.hbase:hbase-hadoop2-compat to 
the latest version 2.1.0 
 
cc: 


> Beam Dependency Update Request: org.apache.hbase:hbase-hadoop2-compat 2.1.0
> ---
>
> Key: BEAM-4953
> URL: https://issues.apache.org/jira/browse/BEAM-4953
> Project: Beam
>  Issue Type: Sub-task
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Assignee: Tim Robertson
>Priority: Major
>
> 2018-07-25 20:28:33.621577
> Please review and upgrade the org.apache.hbase:hbase-hadoop2-compat 
> to the latest version 2.1.0 
>  
> cc: 
> 2018-08-06 12:12:06.214820
> Please review and upgrade the org.apache.hbase:hbase-hadoop2-compat 
> to the latest version 2.1.0 
>  
> cc: 
> 2018-08-13 12:13:40.056300
> Please review and upgrade the org.apache.hbase:hbase-hadoop2-compat 
> to the latest version 2.1.0 
>  
> cc: 
> 2018-08-20 12:14:10.305463
> Please review and upgrade the org.apache.hbase:hbase-hadoop2-compat 
> to the latest version 2.1.0 
>  
> cc: 
> 2018-08-27 12:15:12.871124
> Please review and upgrade the org.apache.hbase:hbase-hadoop2-compat 
> to the latest version 2.1.0 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-4975) Beam Dependency Update Request: com.esotericsoftware.kryo:kryo 2.24.0

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-4975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-4975:

Description: 


2018-07-25 20:30:59.832322

Please review and upgrade the com.esotericsoftware.kryo:kryo to the 
latest version 2.24.0 
 
cc: 

2018-08-06 12:13:35.657640

Please review and upgrade the com.esotericsoftware.kryo:kryo to the 
latest version 2.24.0 
 
cc: 

2018-08-13 12:15:00.360514

Please review and upgrade the com.esotericsoftware.kryo:kryo to the 
latest version 2.24.0 
 
cc: 

2018-08-20 12:15:17.992671

Please review and upgrade the com.esotericsoftware.kryo:kryo to the 
latest version 2.24.0 
 
cc: 

2018-08-27 12:15:54.996886

Please review and upgrade the com.esotericsoftware.kryo:kryo to the 
latest version 2.24.0 
 
cc: 

  was:


2018-07-25 20:30:59.832322

Please review and upgrade the com.esotericsoftware.kryo:kryo to the 
latest version 2.24.0 
 
cc: 

2018-08-06 12:13:35.657640

Please review and upgrade the com.esotericsoftware.kryo:kryo to the 
latest version 2.24.0 
 
cc: 

2018-08-13 12:15:00.360514

Please review and upgrade the com.esotericsoftware.kryo:kryo to the 
latest version 2.24.0 
 
cc: 

2018-08-20 12:15:17.992671

Please review and upgrade the com.esotericsoftware.kryo:kryo to the 
latest version 2.24.0 
 
cc: 


> Beam Dependency Update Request: com.esotericsoftware.kryo:kryo 2.24.0
> -
>
> Key: BEAM-4975
> URL: https://issues.apache.org/jira/browse/BEAM-4975
> Project: Beam
>  Issue Type: Sub-task
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Priority: Major
>
> 2018-07-25 20:30:59.832322
> Please review and upgrade the com.esotericsoftware.kryo:kryo to the 
> latest version 2.24.0 
>  
> cc: 
> 2018-08-06 12:13:35.657640
> Please review and upgrade the com.esotericsoftware.kryo:kryo to the 
> latest version 2.24.0 
>  
> cc: 
> 2018-08-13 12:15:00.360514
> Please review and upgrade the com.esotericsoftware.kryo:kryo to the 
> latest version 2.24.0 
>  
> cc: 
> 2018-08-20 12:15:17.992671
> Please review and upgrade the com.esotericsoftware.kryo:kryo to the 
> latest version 2.24.0 
>  
> cc: 
> 2018-08-27 12:15:54.996886
> Please review and upgrade the com.esotericsoftware.kryo:kryo to the 
> latest version 2.24.0 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (BEAM-5233) Beam Dependency Update Request: org.apache.hive.hcatalog:hive-hcatalog-core 3.1.0

[Beam JIRA Bot (JIRA)]

Beam JIRA Bot created BEAM-5233:
---

 Summary: Beam Dependency Update Request: 
org.apache.hive.hcatalog:hive-hcatalog-core 3.1.0
 Key: BEAM-5233
 URL: https://issues.apache.org/jira/browse/BEAM-5233
 Project: Beam
  Issue Type: Sub-task
  Components: dependencies
Reporter: Beam JIRA Bot
Assignee: Tim Robertson




2018-08-27 12:15:40.178082

Please review and upgrade the 
org.apache.hive.hcatalog:hive-hcatalog-core to the latest version 3.1.0 
 
cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-4954) Beam Dependency Update Request: org.apache.hbase:hbase-server 2.1.0

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-4954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-4954:

Description: 


2018-07-25 20:28:42.884230

Please review and upgrade the org.apache.hbase:hbase-server to the 
latest version 2.1.0 
 
cc: 

2018-08-06 12:12:14.491952

Please review and upgrade the org.apache.hbase:hbase-server to the 
latest version 2.1.0 
 
cc: 

2018-08-13 12:13:48.633595

Please review and upgrade the org.apache.hbase:hbase-server to the 
latest version 2.1.0 
 
cc: 

2018-08-20 12:14:15.918996

Please review and upgrade the org.apache.hbase:hbase-server to the 
latest version 2.1.0 
 
cc: 

2018-08-27 12:15:18.169745

Please review and upgrade the org.apache.hbase:hbase-server to the 
latest version 2.1.0 
 
cc: 

  was:


2018-07-25 20:28:42.884230

Please review and upgrade the org.apache.hbase:hbase-server to the 
latest version 2.1.0 
 
cc: 

2018-08-06 12:12:14.491952

Please review and upgrade the org.apache.hbase:hbase-server to the 
latest version 2.1.0 
 
cc: 

2018-08-13 12:13:48.633595

Please review and upgrade the org.apache.hbase:hbase-server to the 
latest version 2.1.0 
 
cc: 

2018-08-20 12:14:15.918996

Please review and upgrade the org.apache.hbase:hbase-server to the 
latest version 2.1.0 
 
cc: 


> Beam Dependency Update Request: org.apache.hbase:hbase-server 2.1.0
> ---
>
> Key: BEAM-4954
> URL: https://issues.apache.org/jira/browse/BEAM-4954
> Project: Beam
>  Issue Type: Sub-task
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Assignee: Tim Robertson
>Priority: Major
>
> 2018-07-25 20:28:42.884230
> Please review and upgrade the org.apache.hbase:hbase-server to the 
> latest version 2.1.0 
>  
> cc: 
> 2018-08-06 12:12:14.491952
> Please review and upgrade the org.apache.hbase:hbase-server to the 
> latest version 2.1.0 
>  
> cc: 
> 2018-08-13 12:13:48.633595
> Please review and upgrade the org.apache.hbase:hbase-server to the 
> latest version 2.1.0 
>  
> cc: 
> 2018-08-20 12:14:15.918996
> Please review and upgrade the org.apache.hbase:hbase-server to the 
> latest version 2.1.0 
>  
> cc: 
> 2018-08-27 12:15:18.169745
> Please review and upgrade the org.apache.hbase:hbase-server to the 
> latest version 2.1.0 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-5087) Beam Dependency Update Request: org.apache.kudu:kudu-client 1.7.1

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-5087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-5087:

Description: 


2018-08-06 12:13:44.769883

Please review and upgrade the org.apache.kudu:kudu-client to the latest 
version 1.7.1 
 
cc: 

2018-08-13 12:15:08.713667

Please review and upgrade the org.apache.kudu:kudu-client to the latest 
version 1.7.1 
 
cc: 

2018-08-20 12:15:23.382955

Please review and upgrade the org.apache.kudu:kudu-client to the latest 
version 1.7.1 
 
cc: 

2018-08-27 12:16:00.300748

Please review and upgrade the org.apache.kudu:kudu-client to the latest 
version 1.7.1 
 
cc: 

  was:


2018-08-06 12:13:44.769883

Please review and upgrade the org.apache.kudu:kudu-client to the latest 
version 1.7.1 
 
cc: 

2018-08-13 12:15:08.713667

Please review and upgrade the org.apache.kudu:kudu-client to the latest 
version 1.7.1 
 
cc: 

2018-08-20 12:15:23.382955

Please review and upgrade the org.apache.kudu:kudu-client to the latest 
version 1.7.1 
 
cc: 


> Beam Dependency Update Request: org.apache.kudu:kudu-client 1.7.1
> -
>
> Key: BEAM-5087
> URL: https://issues.apache.org/jira/browse/BEAM-5087
> Project: Beam
>  Issue Type: Sub-task
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Assignee: Tim Robertson
>Priority: Major
>
> 2018-08-06 12:13:44.769883
> Please review and upgrade the org.apache.kudu:kudu-client to the 
> latest version 1.7.1 
>  
> cc: 
> 2018-08-13 12:15:08.713667
> Please review and upgrade the org.apache.kudu:kudu-client to the 
> latest version 1.7.1 
>  
> cc: 
> 2018-08-20 12:15:23.382955
> Please review and upgrade the org.apache.kudu:kudu-client to the 
> latest version 1.7.1 
>  
> cc: 
> 2018-08-27 12:16:00.300748
> Please review and upgrade the org.apache.kudu:kudu-client to the 
> latest version 1.7.1 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-4956) Beam Dependency Update Request: org.apache.hbase:hbase-shaded-server 2.0.0-alpha2

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-4956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-4956:

Description: 


2018-07-25 20:29:00.961205

Please review and upgrade the org.apache.hbase:hbase-shaded-server to 
the latest version 2.0.0-alpha2 
 
cc: 

2018-08-06 12:12:30.539804

Please review and upgrade the org.apache.hbase:hbase-shaded-server to 
the latest version 2.0.0-alpha2 
 
cc: 

2018-08-13 12:14:05.047570

Please review and upgrade the org.apache.hbase:hbase-shaded-server to 
the latest version 2.0.0-alpha2 
 
cc: 

2018-08-20 12:14:27.200876

Please review and upgrade the org.apache.hbase:hbase-shaded-server to 
the latest version 2.0.0-alpha2 
 
cc: 

2018-08-27 12:15:29.233250

Please review and upgrade the org.apache.hbase:hbase-shaded-server to 
the latest version 2.0.0-alpha2 
 
cc: 

  was:


2018-07-25 20:29:00.961205

Please review and upgrade the org.apache.hbase:hbase-shaded-server to 
the latest version 2.0.0-alpha2 
 
cc: 

2018-08-06 12:12:30.539804

Please review and upgrade the org.apache.hbase:hbase-shaded-server to 
the latest version 2.0.0-alpha2 
 
cc: 

2018-08-13 12:14:05.047570

Please review and upgrade the org.apache.hbase:hbase-shaded-server to 
the latest version 2.0.0-alpha2 
 
cc: 

2018-08-20 12:14:27.200876

Please review and upgrade the org.apache.hbase:hbase-shaded-server to 
the latest version 2.0.0-alpha2 
 
cc: 


> Beam Dependency Update Request: org.apache.hbase:hbase-shaded-server 
> 2.0.0-alpha2
> -
>
> Key: BEAM-4956
> URL: https://issues.apache.org/jira/browse/BEAM-4956
> Project: Beam
>  Issue Type: Sub-task
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Assignee: Tim Robertson
>Priority: Major
>
> 2018-07-25 20:29:00.961205
> Please review and upgrade the org.apache.hbase:hbase-shaded-server to 
> the latest version 2.0.0-alpha2 
>  
> cc: 
> 2018-08-06 12:12:30.539804
> Please review and upgrade the org.apache.hbase:hbase-shaded-server to 
> the latest version 2.0.0-alpha2 
>  
> cc: 
> 2018-08-13 12:14:05.047570
> Please review and upgrade the org.apache.hbase:hbase-shaded-server to 
> the latest version 2.0.0-alpha2 
>  
> cc: 
> 2018-08-20 12:14:27.200876
> Please review and upgrade the org.apache.hbase:hbase-shaded-server to 
> the latest version 2.0.0-alpha2 
>  
> cc: 
> 2018-08-27 12:15:29.233250
> Please review and upgrade the org.apache.hbase:hbase-shaded-server to 
> the latest version 2.0.0-alpha2 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (BEAM-5231) Beam Dependency Update Request: org.apache.hive:hive-common 3.1.0

[Beam JIRA Bot (JIRA)]

Beam JIRA Bot created BEAM-5231:
---

 Summary: Beam Dependency Update Request: 
org.apache.hive:hive-common 3.1.0
 Key: BEAM-5231
 URL: https://issues.apache.org/jira/browse/BEAM-5231
 Project: Beam
  Issue Type: Sub-task
  Components: dependencies
Reporter: Beam JIRA Bot
Assignee: Tim Robertson




2018-08-27 12:15:36.531792

Please review and upgrade the org.apache.hive:hive-common to the latest 
version 3.1.0 
 
cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-4955) Beam Dependency Update Request: org.apache.hbase:hbase-shaded-client 2.1.0

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-4955:

Description: 


2018-07-25 20:28:51.823671

Please review and upgrade the org.apache.hbase:hbase-shaded-client to 
the latest version 2.1.0 
 
cc: 

2018-08-06 12:12:22.319940

Please review and upgrade the org.apache.hbase:hbase-shaded-client to 
the latest version 2.1.0 
 
cc: 

2018-08-13 12:13:56.805066

Please review and upgrade the org.apache.hbase:hbase-shaded-client to 
the latest version 2.1.0 
 
cc: 

2018-08-20 12:14:21.628455

Please review and upgrade the org.apache.hbase:hbase-shaded-client to 
the latest version 2.1.0 
 
cc: 

2018-08-27 12:15:23.647605

Please review and upgrade the org.apache.hbase:hbase-shaded-client to 
the latest version 2.1.0 
 
cc: 

  was:


2018-07-25 20:28:51.823671

Please review and upgrade the org.apache.hbase:hbase-shaded-client to 
the latest version 2.1.0 
 
cc: 

2018-08-06 12:12:22.319940

Please review and upgrade the org.apache.hbase:hbase-shaded-client to 
the latest version 2.1.0 
 
cc: 

2018-08-13 12:13:56.805066

Please review and upgrade the org.apache.hbase:hbase-shaded-client to 
the latest version 2.1.0 
 
cc: 

2018-08-20 12:14:21.628455

Please review and upgrade the org.apache.hbase:hbase-shaded-client to 
the latest version 2.1.0 
 
cc: 


> Beam Dependency Update Request: org.apache.hbase:hbase-shaded-client 2.1.0
> --
>
> Key: BEAM-4955
> URL: https://issues.apache.org/jira/browse/BEAM-4955
> Project: Beam
>  Issue Type: Sub-task
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Assignee: Tim Robertson
>Priority: Major
>
> 2018-07-25 20:28:51.823671
> Please review and upgrade the org.apache.hbase:hbase-shaded-client to 
> the latest version 2.1.0 
>  
> cc: 
> 2018-08-06 12:12:22.319940
> Please review and upgrade the org.apache.hbase:hbase-shaded-client to 
> the latest version 2.1.0 
>  
> cc: 
> 2018-08-13 12:13:56.805066
> Please review and upgrade the org.apache.hbase:hbase-shaded-client to 
> the latest version 2.1.0 
>  
> cc: 
> 2018-08-20 12:14:21.628455
> Please review and upgrade the org.apache.hbase:hbase-shaded-client to 
> the latest version 2.1.0 
>  
> cc: 
> 2018-08-27 12:15:23.647605
> Please review and upgrade the org.apache.hbase:hbase-shaded-client to 
> the latest version 2.1.0 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-4981) Beam Dependency Update Request: io.netty:netty-all 5.0.0.Alpha2

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-4981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-4981:

Description: 


2018-07-25 20:31:33.148217

Please review and upgrade the io.netty:netty-all to the latest version 
5.0.0.Alpha2 
 
cc: 

2018-08-06 12:14:05.424327

Please review and upgrade the io.netty:netty-all to the latest version 
5.0.0.Alpha2 
 
cc: 

2018-08-13 12:15:33.991438

Please review and upgrade the io.netty:netty-all to the latest version 
5.0.0.Alpha2 
 
cc: 

2018-08-20 12:15:39.734758

Please review and upgrade the io.netty:netty-all to the latest version 
5.0.0.Alpha2 
 
cc: 

2018-08-27 12:16:12.599874

Please review and upgrade the io.netty:netty-all to the latest version 
5.0.0.Alpha2 
 
cc: 

  was:


2018-07-25 20:31:33.148217

Please review and upgrade the io.netty:netty-all to the latest version 
5.0.0.Alpha2 
 
cc: 

2018-08-06 12:14:05.424327

Please review and upgrade the io.netty:netty-all to the latest version 
5.0.0.Alpha2 
 
cc: 

2018-08-13 12:15:33.991438

Please review and upgrade the io.netty:netty-all to the latest version 
5.0.0.Alpha2 
 
cc: 

2018-08-20 12:15:39.734758

Please review and upgrade the io.netty:netty-all to the latest version 
5.0.0.Alpha2 
 
cc: 


> Beam Dependency Update Request: io.netty:netty-all 5.0.0.Alpha2
> ---
>
> Key: BEAM-4981
> URL: https://issues.apache.org/jira/browse/BEAM-4981
> Project: Beam
>  Issue Type: Sub-task
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Assignee: Chamikara Jayalath
>Priority: Major
>
> 2018-07-25 20:31:33.148217
> Please review and upgrade the io.netty:netty-all to the latest 
> version 5.0.0.Alpha2 
>  
> cc: 
> 2018-08-06 12:14:05.424327
> Please review and upgrade the io.netty:netty-all to the latest 
> version 5.0.0.Alpha2 
>  
> cc: 
> 2018-08-13 12:15:33.991438
> Please review and upgrade the io.netty:netty-all to the latest 
> version 5.0.0.Alpha2 
>  
> cc: 
> 2018-08-20 12:15:39.734758
> Please review and upgrade the io.netty:netty-all to the latest 
> version 5.0.0.Alpha2 
>  
> cc: 
> 2018-08-27 12:16:12.599874
> Please review and upgrade the io.netty:netty-all to the latest 
> version 5.0.0.Alpha2 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-4985) Beam Dependency Update Request: io.opencensus:opencensus-contrib-grpc-metrics 0.15.0

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-4985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-4985:

Description: 


2018-07-25 20:32:03.733087

Please review and upgrade the 
io.opencensus:opencensus-contrib-grpc-metrics to the latest version 0.15.0 
 
cc: 

2018-08-06 12:14:29.306714

Please review and upgrade the 
io.opencensus:opencensus-contrib-grpc-metrics to the latest version 0.15.0 
 
cc: 

2018-08-13 12:15:59.071459

Please review and upgrade the 
io.opencensus:opencensus-contrib-grpc-metrics to the latest version 0.15.0 
 
cc: 

2018-08-20 12:15:56.313339

Please review and upgrade the 
io.opencensus:opencensus-contrib-grpc-metrics to the latest version 0.15.0 
 
cc: 

2018-08-27 12:16:28.800558

Please review and upgrade the 
io.opencensus:opencensus-contrib-grpc-metrics to the latest version 0.15.0 
 
cc: 

  was:


2018-07-25 20:32:03.733087

Please review and upgrade the 
io.opencensus:opencensus-contrib-grpc-metrics to the latest version 0.15.0 
 
cc: 

2018-08-06 12:14:29.306714

Please review and upgrade the 
io.opencensus:opencensus-contrib-grpc-metrics to the latest version 0.15.0 
 
cc: 

2018-08-13 12:15:59.071459

Please review and upgrade the 
io.opencensus:opencensus-contrib-grpc-metrics to the latest version 0.15.0 
 
cc: 

2018-08-20 12:15:56.313339

Please review and upgrade the 
io.opencensus:opencensus-contrib-grpc-metrics to the latest version 0.15.0 
 
cc: 


> Beam Dependency Update Request: io.opencensus:opencensus-contrib-grpc-metrics 
> 0.15.0
> 
>
> Key: BEAM-4985
> URL: https://issues.apache.org/jira/browse/BEAM-4985
> Project: Beam
>  Issue Type: Sub-task
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Priority: Major
>
> 2018-07-25 20:32:03.733087
> Please review and upgrade the 
> io.opencensus:opencensus-contrib-grpc-metrics to the latest version 0.15.0 
>  
> cc: 
> 2018-08-06 12:14:29.306714
> Please review and upgrade the 
> io.opencensus:opencensus-contrib-grpc-metrics to the latest version 0.15.0 
>  
> cc: 
> 2018-08-13 12:15:59.071459
> Please review and upgrade the 
> io.opencensus:opencensus-contrib-grpc-metrics to the latest version 0.15.0 
>  
> cc: 
> 2018-08-20 12:15:56.313339
> Please review and upgrade the 
> io.opencensus:opencensus-contrib-grpc-metrics to the latest version 0.15.0 
>  
> cc: 
> 2018-08-27 12:16:28.800558
> Please review and upgrade the 
> io.opencensus:opencensus-contrib-grpc-metrics to the latest version 0.15.0 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-4977) Beam Dependency Update Request: io.dropwizard.metrics:metrics-core 4.1.0-rc2

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-4977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-4977:

Description: 


2018-07-25 20:31:12.560286

Please review and upgrade the io.dropwizard.metrics:metrics-core to the 
latest version 4.1.0-rc2 
 
cc: 

2018-08-06 12:13:49.600351

Please review and upgrade the io.dropwizard.metrics:metrics-core to the 
latest version 4.1.0-rc2 
 
cc: 

2018-08-13 12:15:16.600478

Please review and upgrade the io.dropwizard.metrics:metrics-core to the 
latest version 4.1.0-rc2 
 
cc: 

2018-08-20 12:15:28.768620

Please review and upgrade the io.dropwizard.metrics:metrics-core to the 
latest version 4.1.0-rc2 
 
cc: 

2018-08-27 12:16:05.660353

Please review and upgrade the io.dropwizard.metrics:metrics-core to the 
latest version 4.1.0-rc2 
 
cc: 

  was:


2018-07-25 20:31:12.560286

Please review and upgrade the io.dropwizard.metrics:metrics-core to the 
latest version 4.1.0-rc2 
 
cc: 

2018-08-06 12:13:49.600351

Please review and upgrade the io.dropwizard.metrics:metrics-core to the 
latest version 4.1.0-rc2 
 
cc: 

2018-08-13 12:15:16.600478

Please review and upgrade the io.dropwizard.metrics:metrics-core to the 
latest version 4.1.0-rc2 
 
cc: 

2018-08-20 12:15:28.768620

Please review and upgrade the io.dropwizard.metrics:metrics-core to the 
latest version 4.1.0-rc2 
 
cc: 


> Beam Dependency Update Request: io.dropwizard.metrics:metrics-core 4.1.0-rc2
> 
>
> Key: BEAM-4977
> URL: https://issues.apache.org/jira/browse/BEAM-4977
> Project: Beam
>  Issue Type: Sub-task
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Assignee: Scott Wegner
>Priority: Major
>
> 2018-07-25 20:31:12.560286
> Please review and upgrade the io.dropwizard.metrics:metrics-core to 
> the latest version 4.1.0-rc2 
>  
> cc: 
> 2018-08-06 12:13:49.600351
> Please review and upgrade the io.dropwizard.metrics:metrics-core to 
> the latest version 4.1.0-rc2 
>  
> cc: 
> 2018-08-13 12:15:16.600478
> Please review and upgrade the io.dropwizard.metrics:metrics-core to 
> the latest version 4.1.0-rc2 
>  
> cc: 
> 2018-08-20 12:15:28.768620
> Please review and upgrade the io.dropwizard.metrics:metrics-core to 
> the latest version 4.1.0-rc2 
>  
> cc: 
> 2018-08-27 12:16:05.660353
> Please review and upgrade the io.dropwizard.metrics:metrics-core to 
> the latest version 4.1.0-rc2 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-4999) Beam Dependency Update Request: com.carrotsearch.randomizedtesting:randomizedtesting-runner 2.6.3

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-4999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-4999:

Description: 


2018-07-25 20:33:34.278692

Please review and upgrade the 
com.carrotsearch.randomizedtesting:randomizedtesting-runner to the latest 
version 2.6.3 
 
cc: 

2018-08-06 12:15:09.509698

Please review and upgrade the 
com.carrotsearch.randomizedtesting:randomizedtesting-runner to the latest 
version 2.6.3 
 
cc: 

2018-08-13 12:16:46.379403

Please review and upgrade the 
com.carrotsearch.randomizedtesting:randomizedtesting-runner to the latest 
version 2.6.3 
 
cc: 

2018-08-20 12:16:18.934917

Please review and upgrade the 
com.carrotsearch.randomizedtesting:randomizedtesting-runner to the latest 
version 2.6.3 
 
cc: 

2018-08-27 12:16:43.016483

Please review and upgrade the 
com.carrotsearch.randomizedtesting:randomizedtesting-runner to the latest 
version 2.6.3 
 
cc: 

  was:


2018-07-25 20:33:34.278692

Please review and upgrade the 
com.carrotsearch.randomizedtesting:randomizedtesting-runner to the latest 
version 2.6.3 
 
cc: 

2018-08-06 12:15:09.509698

Please review and upgrade the 
com.carrotsearch.randomizedtesting:randomizedtesting-runner to the latest 
version 2.6.3 
 
cc: 

2018-08-13 12:16:46.379403

Please review and upgrade the 
com.carrotsearch.randomizedtesting:randomizedtesting-runner to the latest 
version 2.6.3 
 
cc: 

2018-08-20 12:16:18.934917

Please review and upgrade the 
com.carrotsearch.randomizedtesting:randomizedtesting-runner to the latest 
version 2.6.3 
 
cc: 


> Beam Dependency Update Request: 
> com.carrotsearch.randomizedtesting:randomizedtesting-runner 2.6.3
> -
>
> Key: BEAM-4999
> URL: https://issues.apache.org/jira/browse/BEAM-4999
> Project: Beam
>  Issue Type: Sub-task
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Assignee: Cao Manh Dat
>Priority: Major
>
> 2018-07-25 20:33:34.278692
> Please review and upgrade the 
> com.carrotsearch.randomizedtesting:randomizedtesting-runner to the latest 
> version 2.6.3 
>  
> cc: 
> 2018-08-06 12:15:09.509698
> Please review and upgrade the 
> com.carrotsearch.randomizedtesting:randomizedtesting-runner to the latest 
> version 2.6.3 
>  
> cc: 
> 2018-08-13 12:16:46.379403
> Please review and upgrade the 
> com.carrotsearch.randomizedtesting:randomizedtesting-runner to the latest 
> version 2.6.3 
>  
> cc: 
> 2018-08-20 12:16:18.934917
> Please review and upgrade the 
> com.carrotsearch.randomizedtesting:randomizedtesting-runner to the latest 
> version 2.6.3 
>  
> cc: 
> 2018-08-27 12:16:43.016483
> Please review and upgrade the 
> com.carrotsearch.randomizedtesting:randomizedtesting-runner to the latest 
> version 2.6.3 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-5001) Beam Dependency Update Request: org.scala-lang:scala-library 2.13.0-M4

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-5001:

Description: 


2018-07-25 20:33:44.345851

Please review and upgrade the org.scala-lang:scala-library to the 
latest version 2.13.0-M4 
 
cc: 

2018-08-06 12:15:17.577869

Please review and upgrade the org.scala-lang:scala-library to the 
latest version 2.13.0-M4 
 
cc: 

2018-08-13 12:16:54.632139

Please review and upgrade the org.scala-lang:scala-library to the 
latest version 2.13.0-M4 
 
cc: 

2018-08-20 12:16:24.411893

Please review and upgrade the org.scala-lang:scala-library to the 
latest version 2.13.0-M4 
 
cc: 

2018-08-27 12:16:48.560584

Please review and upgrade the org.scala-lang:scala-library to the 
latest version 2.13.0-M4 
 
cc: 

  was:


2018-07-25 20:33:44.345851

Please review and upgrade the org.scala-lang:scala-library to the 
latest version 2.13.0-M4 
 
cc: 

2018-08-06 12:15:17.577869

Please review and upgrade the org.scala-lang:scala-library to the 
latest version 2.13.0-M4 
 
cc: 

2018-08-13 12:16:54.632139

Please review and upgrade the org.scala-lang:scala-library to the 
latest version 2.13.0-M4 
 
cc: 

2018-08-20 12:16:24.411893

Please review and upgrade the org.scala-lang:scala-library to the 
latest version 2.13.0-M4 
 
cc: 


> Beam Dependency Update Request: org.scala-lang:scala-library 2.13.0-M4
> --
>
> Key: BEAM-5001
> URL: https://issues.apache.org/jira/browse/BEAM-5001
> Project: Beam
>  Issue Type: Sub-task
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Priority: Major
>
> 2018-07-25 20:33:44.345851
> Please review and upgrade the org.scala-lang:scala-library to the 
> latest version 2.13.0-M4 
>  
> cc: 
> 2018-08-06 12:15:17.577869
> Please review and upgrade the org.scala-lang:scala-library to the 
> latest version 2.13.0-M4 
>  
> cc: 
> 2018-08-13 12:16:54.632139
> Please review and upgrade the org.scala-lang:scala-library to the 
> latest version 2.13.0-M4 
>  
> cc: 
> 2018-08-20 12:16:24.411893
> Please review and upgrade the org.scala-lang:scala-library to the 
> latest version 2.13.0-M4 
>  
> cc: 
> 2018-08-27 12:16:48.560584
> Please review and upgrade the org.scala-lang:scala-library to the 
> latest version 2.13.0-M4 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-4984) Beam Dependency Update Request: io.opencensus:opencensus-api 0.15.0

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-4984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-4984:

Description: 


2018-07-25 20:31:53.817585

Please review and upgrade the io.opencensus:opencensus-api to the 
latest version 0.15.0 
 
cc: 

2018-08-06 12:14:21.013056

Please review and upgrade the io.opencensus:opencensus-api to the 
latest version 0.15.0 
 
cc: 

2018-08-13 12:15:50.820809

Please review and upgrade the io.opencensus:opencensus-api to the 
latest version 0.15.0 
 
cc: 

2018-08-20 12:15:50.557322

Please review and upgrade the io.opencensus:opencensus-api to the 
latest version 0.15.0 
 
cc: 

2018-08-27 12:16:23.528203

Please review and upgrade the io.opencensus:opencensus-api to the 
latest version 0.15.0 
 
cc: 

  was:


2018-07-25 20:31:53.817585

Please review and upgrade the io.opencensus:opencensus-api to the 
latest version 0.15.0 
 
cc: 

2018-08-06 12:14:21.013056

Please review and upgrade the io.opencensus:opencensus-api to the 
latest version 0.15.0 
 
cc: 

2018-08-13 12:15:50.820809

Please review and upgrade the io.opencensus:opencensus-api to the 
latest version 0.15.0 
 
cc: 

2018-08-20 12:15:50.557322

Please review and upgrade the io.opencensus:opencensus-api to the 
latest version 0.15.0 
 
cc: 


> Beam Dependency Update Request: io.opencensus:opencensus-api 0.15.0
> ---
>
> Key: BEAM-4984
> URL: https://issues.apache.org/jira/browse/BEAM-4984
> Project: Beam
>  Issue Type: Sub-task
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Priority: Major
>
> 2018-07-25 20:31:53.817585
> Please review and upgrade the io.opencensus:opencensus-api to the 
> latest version 0.15.0 
>  
> cc: 
> 2018-08-06 12:14:21.013056
> Please review and upgrade the io.opencensus:opencensus-api to the 
> latest version 0.15.0 
>  
> cc: 
> 2018-08-13 12:15:50.820809
> Please review and upgrade the io.opencensus:opencensus-api to the 
> latest version 0.15.0 
>  
> cc: 
> 2018-08-20 12:15:50.557322
> Please review and upgrade the io.opencensus:opencensus-api to the 
> latest version 0.15.0 
>  
> cc: 
> 2018-08-27 12:16:23.528203
> Please review and upgrade the io.opencensus:opencensus-api to the 
> latest version 0.15.0 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-4982) Beam Dependency Update Request: io.netty:netty-transport-native-epoll 5.0.0.Alpha2

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-4982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-4982:

Description: 


2018-07-25 20:31:42.182471

Please review and upgrade the io.netty:netty-transport-native-epoll to 
the latest version 5.0.0.Alpha2 
 
cc: 

2018-08-06 12:14:13.141909

Please review and upgrade the io.netty:netty-transport-native-epoll to 
the latest version 5.0.0.Alpha2 
 
cc: 

2018-08-13 12:15:42.691508

Please review and upgrade the io.netty:netty-transport-native-epoll to 
the latest version 5.0.0.Alpha2 
 
cc: 

2018-08-20 12:15:45.103065

Please review and upgrade the io.netty:netty-transport-native-epoll to 
the latest version 5.0.0.Alpha2 
 
cc: 

2018-08-27 12:16:18.187792

Please review and upgrade the io.netty:netty-transport-native-epoll to 
the latest version 5.0.0.Alpha2 
 
cc: 

  was:


2018-07-25 20:31:42.182471

Please review and upgrade the io.netty:netty-transport-native-epoll to 
the latest version 5.0.0.Alpha2 
 
cc: 

2018-08-06 12:14:13.141909

Please review and upgrade the io.netty:netty-transport-native-epoll to 
the latest version 5.0.0.Alpha2 
 
cc: 

2018-08-13 12:15:42.691508

Please review and upgrade the io.netty:netty-transport-native-epoll to 
the latest version 5.0.0.Alpha2 
 
cc: 

2018-08-20 12:15:45.103065

Please review and upgrade the io.netty:netty-transport-native-epoll to 
the latest version 5.0.0.Alpha2 
 
cc: 


> Beam Dependency Update Request: io.netty:netty-transport-native-epoll 
> 5.0.0.Alpha2
> --
>
> Key: BEAM-4982
> URL: https://issues.apache.org/jira/browse/BEAM-4982
> Project: Beam
>  Issue Type: Sub-task
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Assignee: Chamikara Jayalath
>Priority: Major
>
> 2018-07-25 20:31:42.182471
> Please review and upgrade the io.netty:netty-transport-native-epoll 
> to the latest version 5.0.0.Alpha2 
>  
> cc: 
> 2018-08-06 12:14:13.141909
> Please review and upgrade the io.netty:netty-transport-native-epoll 
> to the latest version 5.0.0.Alpha2 
>  
> cc: 
> 2018-08-13 12:15:42.691508
> Please review and upgrade the io.netty:netty-transport-native-epoll 
> to the latest version 5.0.0.Alpha2 
>  
> cc: 
> 2018-08-20 12:15:45.103065
> Please review and upgrade the io.netty:netty-transport-native-epoll 
> to the latest version 5.0.0.Alpha2 
>  
> cc: 
> 2018-08-27 12:16:18.187792
> Please review and upgrade the io.netty:netty-transport-native-epoll 
> to the latest version 5.0.0.Alpha2 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (BEAM-5235) Beam Dependency Update Request: org.mongodb:mongo-java-driver 3.8.1

[Beam JIRA Bot (JIRA)]

Beam JIRA Bot created BEAM-5235:
---

 Summary: Beam Dependency Update Request: 
org.mongodb:mongo-java-driver 3.8.1
 Key: BEAM-5235
 URL: https://issues.apache.org/jira/browse/BEAM-5235
 Project: Beam
  Issue Type: Sub-task
  Components: dependencies
Reporter: Beam JIRA Bot




2018-08-27 12:16:10.928088

Please review and upgrade the org.mongodb:mongo-java-driver to the 
latest version 3.8.1 
 
cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-5004) Beam Dependency Update Request: org.slf4j:slf4j-jdk14 1.8.0-beta2

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-5004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-5004:

Description: 


2018-07-25 20:34:03.782739

Please review and upgrade the org.slf4j:slf4j-jdk14 to the latest 
version 1.8.0-beta2 
 
cc: 

2018-08-06 12:15:33.737791

Please review and upgrade the org.slf4j:slf4j-jdk14 to the latest 
version 1.8.0-beta2 
 
cc: 

2018-08-13 12:17:11.414966

Please review and upgrade the org.slf4j:slf4j-jdk14 to the latest 
version 1.8.0-beta2 
 
cc: 

2018-08-20 12:16:35.559945

Please review and upgrade the org.slf4j:slf4j-jdk14 to the latest 
version 1.8.0-beta2 
 
cc: 

2018-08-27 12:16:59.447764

Please review and upgrade the org.slf4j:slf4j-jdk14 to the latest 
version 1.8.0-beta2 
 
cc: 

  was:


2018-07-25 20:34:03.782739

Please review and upgrade the org.slf4j:slf4j-jdk14 to the latest 
version 1.8.0-beta2 
 
cc: 

2018-08-06 12:15:33.737791

Please review and upgrade the org.slf4j:slf4j-jdk14 to the latest 
version 1.8.0-beta2 
 
cc: 

2018-08-13 12:17:11.414966

Please review and upgrade the org.slf4j:slf4j-jdk14 to the latest 
version 1.8.0-beta2 
 
cc: 

2018-08-20 12:16:35.559945

Please review and upgrade the org.slf4j:slf4j-jdk14 to the latest 
version 1.8.0-beta2 
 
cc: 


> Beam Dependency Update Request: org.slf4j:slf4j-jdk14 1.8.0-beta2
> -
>
> Key: BEAM-5004
> URL: https://issues.apache.org/jira/browse/BEAM-5004
> Project: Beam
>  Issue Type: Sub-task
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Assignee: yifan zou
>Priority: Major
>
> 2018-07-25 20:34:03.782739
> Please review and upgrade the org.slf4j:slf4j-jdk14 to the latest 
> version 1.8.0-beta2 
>  
> cc: 
> 2018-08-06 12:15:33.737791
> Please review and upgrade the org.slf4j:slf4j-jdk14 to the latest 
> version 1.8.0-beta2 
>  
> cc: 
> 2018-08-13 12:17:11.414966
> Please review and upgrade the org.slf4j:slf4j-jdk14 to the latest 
> version 1.8.0-beta2 
>  
> cc: 
> 2018-08-20 12:16:35.559945
> Please review and upgrade the org.slf4j:slf4j-jdk14 to the latest 
> version 1.8.0-beta2 
>  
> cc: 
> 2018-08-27 12:16:59.447764
> Please review and upgrade the org.slf4j:slf4j-jdk14 to the latest 
> version 1.8.0-beta2 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-5153) Beam Dependency Update Request: org.apache.qpid:proton-j 0.29.0

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-5153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-5153:

Description: 


2018-08-15 03:02:21.460499

Please review and upgrade the org.apache.qpid:proton-j to the latest 
version 0.29.0 
 
cc: 

2018-08-20 12:16:13.405155

Please review and upgrade the org.apache.qpid:proton-j to the latest 
version 0.29.0 
 
cc: 

2018-08-27 12:16:37.680960

Please review and upgrade the org.apache.qpid:proton-j to the latest 
version 0.29.0 
 
cc: 

  was:


2018-08-15 03:02:21.460499

Please review and upgrade the org.apache.qpid:proton-j to the latest 
version 0.29.0 
 
cc: 

2018-08-20 12:16:13.405155

Please review and upgrade the org.apache.qpid:proton-j to the latest 
version 0.29.0 
 
cc: 


> Beam Dependency Update Request: org.apache.qpid:proton-j 0.29.0
> ---
>
> Key: BEAM-5153
> URL: https://issues.apache.org/jira/browse/BEAM-5153
> Project: Beam
>  Issue Type: Sub-task
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Priority: Major
>
> 2018-08-15 03:02:21.460499
> Please review and upgrade the org.apache.qpid:proton-j to the latest 
> version 0.29.0 
>  
> cc: 
> 2018-08-20 12:16:13.405155
> Please review and upgrade the org.apache.qpid:proton-j to the latest 
> version 0.29.0 
>  
> cc: 
> 2018-08-27 12:16:37.680960
> Please review and upgrade the org.apache.qpid:proton-j to the latest 
> version 0.29.0 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-5003) Beam Dependency Update Request: org.slf4j:slf4j-api 1.8.0-beta2

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-5003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-5003:

Description: 


2018-07-25 20:33:54.577172

Please review and upgrade the org.slf4j:slf4j-api to the latest version 
1.8.0-beta2 
 
cc: 

2018-08-06 12:15:25.568553

Please review and upgrade the org.slf4j:slf4j-api to the latest version 
1.8.0-beta2 
 
cc: 

2018-08-13 12:17:03.134784

Please review and upgrade the org.slf4j:slf4j-api to the latest version 
1.8.0-beta2 
 
cc: 

2018-08-20 12:16:29.883029

Please review and upgrade the org.slf4j:slf4j-api to the latest version 
1.8.0-beta2 
 
cc: 

2018-08-27 12:16:54.073040

Please review and upgrade the org.slf4j:slf4j-api to the latest version 
1.8.0-beta2 
 
cc: 

  was:


2018-07-25 20:33:54.577172

Please review and upgrade the org.slf4j:slf4j-api to the latest version 
1.8.0-beta2 
 
cc: 

2018-08-06 12:15:25.568553

Please review and upgrade the org.slf4j:slf4j-api to the latest version 
1.8.0-beta2 
 
cc: 

2018-08-13 12:17:03.134784

Please review and upgrade the org.slf4j:slf4j-api to the latest version 
1.8.0-beta2 
 
cc: 

2018-08-20 12:16:29.883029

Please review and upgrade the org.slf4j:slf4j-api to the latest version 
1.8.0-beta2 
 
cc: 


> Beam Dependency Update Request: org.slf4j:slf4j-api 1.8.0-beta2
> ---
>
> Key: BEAM-5003
> URL: https://issues.apache.org/jira/browse/BEAM-5003
> Project: Beam
>  Issue Type: Sub-task
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Assignee: yifan zou
>Priority: Major
>
> 2018-07-25 20:33:54.577172
> Please review and upgrade the org.slf4j:slf4j-api to the latest 
> version 1.8.0-beta2 
>  
> cc: 
> 2018-08-06 12:15:25.568553
> Please review and upgrade the org.slf4j:slf4j-api to the latest 
> version 1.8.0-beta2 
>  
> cc: 
> 2018-08-13 12:17:03.134784
> Please review and upgrade the org.slf4j:slf4j-api to the latest 
> version 1.8.0-beta2 
>  
> cc: 
> 2018-08-20 12:16:29.883029
> Please review and upgrade the org.slf4j:slf4j-api to the latest 
> version 1.8.0-beta2 
>  
> cc: 
> 2018-08-27 12:16:54.073040
> Please review and upgrade the org.slf4j:slf4j-api to the latest 
> version 1.8.0-beta2 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-5006) Beam Dependency Update Request: org.apache.solr:solr-core 7.4.0

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-5006:

Description: 


2018-07-25 20:34:14.062044

Please review and upgrade the org.apache.solr:solr-core to the latest 
version 7.4.0 
 
cc: 

2018-08-06 12:15:42.060244

Please review and upgrade the org.apache.solr:solr-core to the latest 
version 7.4.0 
 
cc: 

2018-08-13 12:17:20.410676

Please review and upgrade the org.apache.solr:solr-core to the latest 
version 7.4.0 
 
cc: 

2018-08-20 12:16:41.115803

Please review and upgrade the org.apache.solr:solr-core to the latest 
version 7.4.0 
 
cc: 

2018-08-27 12:17:04.784650

Please review and upgrade the org.apache.solr:solr-core to the latest 
version 7.4.0 
 
cc: 

  was:


2018-07-25 20:34:14.062044

Please review and upgrade the org.apache.solr:solr-core to the latest 
version 7.4.0 
 
cc: 

2018-08-06 12:15:42.060244

Please review and upgrade the org.apache.solr:solr-core to the latest 
version 7.4.0 
 
cc: 

2018-08-13 12:17:20.410676

Please review and upgrade the org.apache.solr:solr-core to the latest 
version 7.4.0 
 
cc: 

2018-08-20 12:16:41.115803

Please review and upgrade the org.apache.solr:solr-core to the latest 
version 7.4.0 
 
cc: 


> Beam Dependency Update Request: org.apache.solr:solr-core 7.4.0
> ---
>
> Key: BEAM-5006
> URL: https://issues.apache.org/jira/browse/BEAM-5006
> Project: Beam
>  Issue Type: Sub-task
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Assignee: Tim Robertson
>Priority: Major
>
> 2018-07-25 20:34:14.062044
> Please review and upgrade the org.apache.solr:solr-core to the latest 
> version 7.4.0 
>  
> cc: 
> 2018-08-06 12:15:42.060244
> Please review and upgrade the org.apache.solr:solr-core to the latest 
> version 7.4.0 
>  
> cc: 
> 2018-08-13 12:17:20.410676
> Please review and upgrade the org.apache.solr:solr-core to the latest 
> version 7.4.0 
>  
> cc: 
> 2018-08-20 12:16:41.115803
> Please review and upgrade the org.apache.solr:solr-core to the latest 
> version 7.4.0 
>  
> cc: 
> 2018-08-27 12:17:04.784650
> Please review and upgrade the org.apache.solr:solr-core to the latest 
> version 7.4.0 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (BEAM-5236) Beam Dependency Update Request: org.springframework:spring-expression 5.0.8.RELEASE

[Beam JIRA Bot (JIRA)]

Beam JIRA Bot created BEAM-5236:
---

 Summary: Beam Dependency Update Request: 
org.springframework:spring-expression 5.0.8.RELEASE
 Key: BEAM-5236
 URL: https://issues.apache.org/jira/browse/BEAM-5236
 Project: Beam
  Issue Type: Sub-task
  Components: dependencies
Reporter: Beam JIRA Bot




2018-08-27 12:17:26.503153

Please review and upgrade the org.springframework:spring-expression to 
the latest version 5.0.8.RELEASE 
 
cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (BEAM-5238) Beam Dependency Update Request: org.elasticsearch.plugin:transport-netty4-client 6.4.0

[Beam JIRA Bot (JIRA)]

Beam JIRA Bot created BEAM-5238:
---

 Summary: Beam Dependency Update Request: 
org.elasticsearch.plugin:transport-netty4-client 6.4.0
 Key: BEAM-5238
 URL: https://issues.apache.org/jira/browse/BEAM-5238
 Project: Beam
  Issue Type: Sub-task
  Components: dependencies
Reporter: Beam JIRA Bot
Assignee: Etienne Chauchot




2018-08-27 12:17:35.622044

Please review and upgrade the 
org.elasticsearch.plugin:transport-netty4-client to the latest version 6.4.0 
 
cc: [~timrobertson100], 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-5008) Beam Dependency Update Request: org.apache.solr:solr-test-framework 7.4.0

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-5008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-5008:

Description: 


2018-07-25 20:34:32.698775

Please review and upgrade the org.apache.solr:solr-test-framework to 
the latest version 7.4.0 
 
cc: 

2018-08-06 12:15:58.493346

Please review and upgrade the org.apache.solr:solr-test-framework to 
the latest version 7.4.0 
 
cc: 

2018-08-13 12:17:37.412362

Please review and upgrade the org.apache.solr:solr-test-framework to 
the latest version 7.4.0 
 
cc: 

2018-08-20 12:16:52.207130

Please review and upgrade the org.apache.solr:solr-test-framework to 
the latest version 7.4.0 
 
cc: 

2018-08-27 12:17:15.623778

Please review and upgrade the org.apache.solr:solr-test-framework to 
the latest version 7.4.0 
 
cc: 

  was:


2018-07-25 20:34:32.698775

Please review and upgrade the org.apache.solr:solr-test-framework to 
the latest version 7.4.0 
 
cc: 

2018-08-06 12:15:58.493346

Please review and upgrade the org.apache.solr:solr-test-framework to 
the latest version 7.4.0 
 
cc: 

2018-08-13 12:17:37.412362

Please review and upgrade the org.apache.solr:solr-test-framework to 
the latest version 7.4.0 
 
cc: 

2018-08-20 12:16:52.207130

Please review and upgrade the org.apache.solr:solr-test-framework to 
the latest version 7.4.0 
 
cc: 


> Beam Dependency Update Request: org.apache.solr:solr-test-framework 7.4.0
> -
>
> Key: BEAM-5008
> URL: https://issues.apache.org/jira/browse/BEAM-5008
> Project: Beam
>  Issue Type: Sub-task
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Assignee: Tim Robertson
>Priority: Major
>
> 2018-07-25 20:34:32.698775
> Please review and upgrade the org.apache.solr:solr-test-framework to 
> the latest version 7.4.0 
>  
> cc: 
> 2018-08-06 12:15:58.493346
> Please review and upgrade the org.apache.solr:solr-test-framework to 
> the latest version 7.4.0 
>  
> cc: 
> 2018-08-13 12:17:37.412362
> Please review and upgrade the org.apache.solr:solr-test-framework to 
> the latest version 7.4.0 
>  
> cc: 
> 2018-08-20 12:16:52.207130
> Please review and upgrade the org.apache.solr:solr-test-framework to 
> the latest version 7.4.0 
>  
> cc: 
> 2018-08-27 12:17:15.623778
> Please review and upgrade the org.apache.solr:solr-test-framework to 
> the latest version 7.4.0 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-5010) Beam Dependency Update Request: com.diffplug.spotless:spotless-plugin-gradle 3.14.0

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-5010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-5010:

Description: 


2018-07-25 20:34:43.135425

Please review and upgrade the 
com.diffplug.spotless:spotless-plugin-gradle to the latest version 3.14.0 
 
cc: 

2018-08-02 11:42:53.371288

Please review and upgrade the 
com.diffplug.spotless:spotless-plugin-gradle to the latest version 3.14.0 

cc: 

2018-08-06 12:16:06.737378

Please review and upgrade the 
com.diffplug.spotless:spotless-plugin-gradle to the latest version 3.14.0 
 
cc: 

2018-08-13 12:17:45.864295

Please review and upgrade the 
com.diffplug.spotless:spotless-plugin-gradle to the latest version 3.14.0 
 
cc: 

2018-08-20 12:16:57.784631

Please review and upgrade the 
com.diffplug.spotless:spotless-plugin-gradle to the latest version 3.14.0 
 
cc: 

2018-08-27 12:17:21.140394

Please review and upgrade the 
com.diffplug.spotless:spotless-plugin-gradle to the latest version 3.14.0 
 
cc: 

  was:


2018-07-25 20:34:43.135425

Please review and upgrade the 
com.diffplug.spotless:spotless-plugin-gradle to the latest version 3.14.0 
 
cc: 

2018-08-02 11:42:53.371288

Please review and upgrade the 
com.diffplug.spotless:spotless-plugin-gradle to the latest version 3.14.0 

cc: 

2018-08-06 12:16:06.737378

Please review and upgrade the 
com.diffplug.spotless:spotless-plugin-gradle to the latest version 3.14.0 
 
cc: 

2018-08-13 12:17:45.864295

Please review and upgrade the 
com.diffplug.spotless:spotless-plugin-gradle to the latest version 3.14.0 
 
cc: 

2018-08-20 12:16:57.784631

Please review and upgrade the 
com.diffplug.spotless:spotless-plugin-gradle to the latest version 3.14.0 
 
cc: 


> Beam Dependency Update Request: com.diffplug.spotless:spotless-plugin-gradle 
> 3.14.0
> ---
>
> Key: BEAM-5010
> URL: https://issues.apache.org/jira/browse/BEAM-5010
> Project: Beam
>  Issue Type: Sub-task
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Priority: Major
>
> 2018-07-25 20:34:43.135425
> Please review and upgrade the 
> com.diffplug.spotless:spotless-plugin-gradle to the latest version 3.14.0 
>  
> cc: 
> 2018-08-02 11:42:53.371288
> Please review and upgrade the 
> com.diffplug.spotless:spotless-plugin-gradle to the latest version 3.14.0 
> cc: 
> 2018-08-06 12:16:06.737378
> Please review and upgrade the 
> com.diffplug.spotless:spotless-plugin-gradle to the latest version 3.14.0 
>  
> cc: 
> 2018-08-13 12:17:45.864295
> Please review and upgrade the 
> com.diffplug.spotless:spotless-plugin-gradle to the latest version 3.14.0 
>  
> cc: 
> 2018-08-20 12:16:57.784631
> Please review and upgrade the 
> com.diffplug.spotless:spotless-plugin-gradle to the latest version 3.14.0 
>  
> cc: 
> 2018-08-27 12:17:21.140394
> Please review and upgrade the 
> com.diffplug.spotless:spotless-plugin-gradle to the latest version 3.14.0 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-5014) Beam Dependency Update Request: com.clearspring.analytics:stream 2.9.6

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-5014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-5014:

Description: 


2018-07-25 20:35:03.818461

Please review and upgrade the com.clearspring.analytics:stream to the 
latest version 2.9.6 
 
cc: 

2018-08-06 12:16:19.882469

Please review and upgrade the com.clearspring.analytics:stream to the 
latest version 2.9.6 
 
cc: 

2018-08-13 12:18:02.810770

Please review and upgrade the com.clearspring.analytics:stream to the 
latest version 2.9.6 
 
cc: 

2018-08-20 12:17:10.290844

Please review and upgrade the com.clearspring.analytics:stream to the 
latest version 2.9.6 
 
cc: 

2018-08-27 12:17:28.326890

Please review and upgrade the com.clearspring.analytics:stream to the 
latest version 2.9.6 
 
cc: 

  was:


2018-07-25 20:35:03.818461

Please review and upgrade the com.clearspring.analytics:stream to the 
latest version 2.9.6 
 
cc: 

2018-08-06 12:16:19.882469

Please review and upgrade the com.clearspring.analytics:stream to the 
latest version 2.9.6 
 
cc: 

2018-08-13 12:18:02.810770

Please review and upgrade the com.clearspring.analytics:stream to the 
latest version 2.9.6 
 
cc: 

2018-08-20 12:17:10.290844

Please review and upgrade the com.clearspring.analytics:stream to the 
latest version 2.9.6 
 
cc: 


> Beam Dependency Update Request: com.clearspring.analytics:stream 2.9.6
> --
>
> Key: BEAM-5014
> URL: https://issues.apache.org/jira/browse/BEAM-5014
> Project: Beam
>  Issue Type: Sub-task
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Priority: Major
>
> 2018-07-25 20:35:03.818461
> Please review and upgrade the com.clearspring.analytics:stream to the 
> latest version 2.9.6 
>  
> cc: 
> 2018-08-06 12:16:19.882469
> Please review and upgrade the com.clearspring.analytics:stream to the 
> latest version 2.9.6 
>  
> cc: 
> 2018-08-13 12:18:02.810770
> Please review and upgrade the com.clearspring.analytics:stream to the 
> latest version 2.9.6 
>  
> cc: 
> 2018-08-20 12:17:10.290844
> Please review and upgrade the com.clearspring.analytics:stream to the 
> latest version 2.9.6 
>  
> cc: 
> 2018-08-27 12:17:28.326890
> Please review and upgrade the com.clearspring.analytics:stream to the 
> latest version 2.9.6 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (BEAM-5237) Beam Dependency Update Request: org.elasticsearch.client:transport 6.4.0

[Beam JIRA Bot (JIRA)]

Beam JIRA Bot created BEAM-5237:
---

 Summary: Beam Dependency Update Request: 
org.elasticsearch.client:transport 6.4.0
 Key: BEAM-5237
 URL: https://issues.apache.org/jira/browse/BEAM-5237
 Project: Beam
  Issue Type: Sub-task
  Components: dependencies
Reporter: Beam JIRA Bot
Assignee: Etienne Chauchot




2018-08-27 12:17:33.728604

Please review and upgrade the org.elasticsearch.client:transport to the 
latest version 6.4.0 
 
cc: [~timrobertson100], 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (BEAM-5007) Beam Dependency Update Request: org.apache.solr:solr-solrj 7.4.0

[Beam JIRA Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Beam JIRA Bot updated BEAM-5007:

Description: 


2018-07-25 20:34:23.395935

Please review and upgrade the org.apache.solr:solr-solrj to the latest 
version 7.4.0 
 
cc: 

2018-08-06 12:15:50.132806

Please review and upgrade the org.apache.solr:solr-solrj to the latest 
version 7.4.0 
 
cc: 

2018-08-13 12:17:28.905883

Please review and upgrade the org.apache.solr:solr-solrj to the latest 
version 7.4.0 
 
cc: 

2018-08-20 12:16:46.736637

Please review and upgrade the org.apache.solr:solr-solrj to the latest 
version 7.4.0 
 
cc: 

2018-08-27 12:17:10.154075

Please review and upgrade the org.apache.solr:solr-solrj to the latest 
version 7.4.0 
 
cc: 

  was:


2018-07-25 20:34:23.395935

Please review and upgrade the org.apache.solr:solr-solrj to the latest 
version 7.4.0 
 
cc: 

2018-08-06 12:15:50.132806

Please review and upgrade the org.apache.solr:solr-solrj to the latest 
version 7.4.0 
 
cc: 

2018-08-13 12:17:28.905883

Please review and upgrade the org.apache.solr:solr-solrj to the latest 
version 7.4.0 
 
cc: 

2018-08-20 12:16:46.736637

Please review and upgrade the org.apache.solr:solr-solrj to the latest 
version 7.4.0 
 
cc: 


> Beam Dependency Update Request: org.apache.solr:solr-solrj 7.4.0
> 
>
> Key: BEAM-5007
> URL: https://issues.apache.org/jira/browse/BEAM-5007
> Project: Beam
>  Issue Type: Sub-task
>  Components: dependencies
>Reporter: Beam JIRA Bot
>Assignee: Tim Robertson
>Priority: Major
>
> 2018-07-25 20:34:23.395935
> Please review and upgrade the org.apache.solr:solr-solrj to the 
> latest version 7.4.0 
>  
> cc: 
> 2018-08-06 12:15:50.132806
> Please review and upgrade the org.apache.solr:solr-solrj to the 
> latest version 7.4.0 
>  
> cc: 
> 2018-08-13 12:17:28.905883
> Please review and upgrade the org.apache.solr:solr-solrj to the 
> latest version 7.4.0 
>  
> cc: 
> 2018-08-20 12:16:46.736637
> Please review and upgrade the org.apache.solr:solr-solrj to the 
> latest version 7.4.0 
>  
> cc: 
> 2018-08-27 12:17:10.154075
> Please review and upgrade the org.apache.solr:solr-solrj to the 
> latest version 7.4.0 
>  
> cc: 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Work logged] (BEAM-5107) Support ES 6.x for ElasticsearchIO

[ASF GitHub Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-5107?focusedWorklogId=138362&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-138362
 ]

ASF GitHub Bot logged work on BEAM-5107:


Author: ASF GitHub Bot
Created on: 27/Aug/18 12:24
Start Date: 27/Aug/18 12:24
Worklog Time Spent: 10m 
  Work Description: timrobertson100 commented on issue #6211: [BEAM-5107] 
Support ES-6.x for ElasticsearchIO
URL: https://github.com/apache/beam/pull/6211#issuecomment-416209329
 
 
   Assuming it is a trivial change can I suggest we jump to `6.4.0` before 
committing?  


This is an automated message from the Apache Git Service.
To respond to the message, please log on 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: 138362)
Time Spent: 7h 40m  (was: 7.5h)

> Support ES 6.x for ElasticsearchIO
> --
>
> Key: BEAM-5107
> URL: https://issues.apache.org/jira/browse/BEAM-5107
> Project: Beam
>  Issue Type: Improvement
>  Components: io-java-elasticsearch
>Reporter: Dat Tran
>Assignee: Etienne Chauchot
>Priority: Major
>  Time Spent: 7h 40m
>  Remaining Estimate: 0h
>
> Elasticsearch has released 6.3.2 but ElasticsearchIO only supports 2x-5.x.
> We should support ES 6.x for ElasticsearchIO.
> https://www.elastic.co/guide/en/elasticsearch/reference/current/index.html
> https://github.com/apache/beam/blob/master/sdks/java/io/elasticsearch/src/main/java/org/apache/beam/sdk/io/elasticsearch/ElasticsearchIO.java



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Work logged] (BEAM-5107) Support ES 6.x for ElasticsearchIO

[ASF GitHub Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-5107?focusedWorklogId=138366&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-138366
 ]

ASF GitHub Bot logged work on BEAM-5107:


Author: ASF GitHub Bot
Created on: 27/Aug/18 12:31
Start Date: 27/Aug/18 12:31
Worklog Time Spent: 10m 
  Work Description: echauchot commented on issue #6211: [BEAM-5107] Support 
ES-6.x for ElasticsearchIO
URL: https://github.com/apache/beam/pull/6211#issuecomment-416210945
 
 
   @timrobertson100 +1 of course
   PS: auto deps mecanism will finally stop spamming me :)


This is an automated message from the Apache Git Service.
To respond to the message, please log on 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: 138366)
Time Spent: 7h 50m  (was: 7h 40m)

> Support ES 6.x for ElasticsearchIO
> --
>
> Key: BEAM-5107
> URL: https://issues.apache.org/jira/browse/BEAM-5107
> Project: Beam
>  Issue Type: Improvement
>  Components: io-java-elasticsearch
>Reporter: Dat Tran
>Assignee: Etienne Chauchot
>Priority: Major
>  Time Spent: 7h 50m
>  Remaining Estimate: 0h
>
> Elasticsearch has released 6.3.2 but ElasticsearchIO only supports 2x-5.x.
> We should support ES 6.x for ElasticsearchIO.
> https://www.elastic.co/guide/en/elasticsearch/reference/current/index.html
> https://github.com/apache/beam/blob/master/sdks/java/io/elasticsearch/src/main/java/org/apache/beam/sdk/io/elasticsearch/ElasticsearchIO.java



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Build failed in Jenkins: beam_PostCommit_Java_GradleBuild #1357

[Apache Jenkins Server]

See 


--
[...truncated 18.37 MB...]
Aug 27, 2018 12:43:28 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2018-08-27T12:43:22.109Z: Elided trivial flatten 
Aug 27, 2018 12:43:28 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2018-08-27T12:43:22.150Z: Fusing consumer SpannerIO.Write/Write 
mutations to Cloud Spanner/Wait.OnSignal/Wait/Map into SpannerIO.Write/Write 
mutations to Cloud Spanner/Create seed/Read(CreateSource)
Aug 27, 2018 12:43:28 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2018-08-27T12:43:22.183Z: Fusing consumer SpannerIO.Write/Write 
mutations to Cloud Spanner/Read information schema into SpannerIO.Write/Write 
mutations to Cloud Spanner/Wait.OnSignal/Wait/Map
Aug 27, 2018 12:43:28 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2018-08-27T12:43:22.224Z: Fusing consumer SpannerIO.Write/Write 
mutations to Cloud Spanner/Schema 
View/Combine.GloballyAsSingletonView/BatchViewOverrides.GroupByWindowHashAsKeyAndWindowAsSortKey/BatchViewOverrides.GroupByKeyAndSortValuesOnly/Write
 into SpannerIO.Write/Write mutations to Cloud Spanner/Schema 
View/Combine.GloballyAsSingletonView/BatchViewOverrides.GroupByWindowHashAsKeyAndWindowAsSortKey/ParDo(UseWindowHashAsKeyAndWindowAsSortKey)
Aug 27, 2018 12:43:28 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2018-08-27T12:43:22.278Z: Fusing consumer SpannerIO.Write/Write 
mutations to Cloud Spanner/Schema 
View/Combine.GloballyAsSingletonView/ParDo(IsmRecordForSingularValuePerWindow) 
into SpannerIO.Write/Write mutations to Cloud Spanner/Schema 
View/Combine.GloballyAsSingletonView/BatchViewOverrides.GroupByWindowHashAsKeyAndWindowAsSortKey/BatchViewOverrides.GroupByKeyAndSortValuesOnly/Read
Aug 27, 2018 12:43:28 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2018-08-27T12:43:22.360Z: Fusing consumer SpannerIO.Write/Write 
mutations to Cloud Spanner/Schema 
View/Combine.GloballyAsSingletonView/Combine.globally(Singleton)/WithKeys/AddKeys/Map
 into SpannerIO.Write/Write mutations to Cloud Spanner/Read information schema
Aug 27, 2018 12:43:28 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2018-08-27T12:43:22.409Z: Fusing consumer SpannerIO.Write/Write 
mutations to Cloud Spanner/Schema 
View/Combine.GloballyAsSingletonView/Combine.globally(Singleton)/Combine.perKey(Singleton)/Combine.GroupedValues
 into SpannerIO.Write/Write mutations to Cloud Spanner/Schema 
View/Combine.GloballyAsSingletonView/Combine.globally(Singleton)/Combine.perKey(Singleton)/GroupByKey/Read
Aug 27, 2018 12:43:28 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2018-08-27T12:43:22.452Z: Fusing consumer SpannerIO.Write/Write 
mutations to Cloud Spanner/Schema 
View/Combine.GloballyAsSingletonView/Combine.globally(Singleton)/Values/Values/Map
 into SpannerIO.Write/Write mutations to Cloud Spanner/Schema 
View/Combine.GloballyAsSingletonView/Combine.globally(Singleton)/Combine.perKey(Singleton)/Combine.GroupedValues/Extract
Aug 27, 2018 12:43:28 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2018-08-27T12:43:22.494Z: Fusing consumer SpannerIO.Write/Write 
mutations to Cloud Spanner/Schema 
View/Combine.GloballyAsSingletonView/BatchViewOverrides.GroupByWindowHashAsKeyAndWindowAsSortKey/ParDo(UseWindowHashAsKeyAndWindowAsSortKey)
 into SpannerIO.Write/Write mutations to Cloud Spanner/Schema 
View/Combine.GloballyAsSingletonView/Combine.globally(Singleton)/Values/Values/Map
Aug 27, 2018 12:43:28 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2018-08-27T12:43:22.532Z: Fusing consumer SpannerIO.Write/Write 
mutations to Cloud Spanner/Schema 
View/Combine.GloballyAsSingletonView/Combine.globally(Singleton)/Combine.perKey(Singleton)/Combine.GroupedValues/Extract
 into SpannerIO.Write/Write mutations to Cloud Spanner/Schema 
View/Combine.GloballyAsSingletonView/Combine.globally(Singleton)/Combine.perKey(Singleton)/Combine.GroupedValues
Aug 27, 2018 12:43:28 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2018-08-27T12:43:22.563Z: Fusing consumer SpannerIO.Write/Write 
mutations to Cloud Spanner/Schema 
View/Combine.GloballyAsSingletonView/Combine.globally(Singleton)/Combine.perKey(Singleton)/GroupByKey+SpannerIO.Write/Write
 mutations to Cloud Spanner/Schema 
View/Combine.GloballyAsSingletonView/Combine.globally(Singleton)/Combine.perKey(Singleton)/Combine.GroupedValues/Partial
 into SpannerIO.Write/Write mutations to Cloud Spanner/Schema 
View/Combine.GloballyAsSing

[beam] branch master updated (439ac0d -> 31ceabb)

[iemejia]

This is an automated email from the ASF dual-hosted git repository.

iemejia pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/beam.git.


from 439ac0d  [BEAM-5092] Prevent hash-lookup of schema on every record 
(#6268)
 add 44cf83a  Fix accidental rename of AwsModuleTest to 
AwsModuleAmazonSNSMock
 new 31ceabb  Merge pull request #6269: Fix accidental rename of 
AwsModuleTest to AwsModuleAmazonSNSMock

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 .../io/aws/options/{AwsModuleAmazonSNSMock.java => AwsModuleTest.java}  | 2 +-
 .../src/test/java/org/apache/beam/sdk/io/aws/s3/S3FileSystemTest.java   | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
 rename 
sdks/java/io/amazon-web-services/src/test/java/org/apache/beam/sdk/io/aws/options/{AwsModuleAmazonSNSMock.java
 => AwsModuleTest.java} (99%)

[beam] 01/01: Merge pull request #6269: Fix accidental rename of AwsModuleTest to AwsModuleAmazonSNSMock

[iemejia]

This is an automated email from the ASF dual-hosted git repository.

iemejia pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/beam.git

commit 31ceabb44c536ceb38056a6fba6de0653559f257
Merge: 439ac0d 44cf83a
Author: Ismaël Mejía 
AuthorDate: Mon Aug 27 14:49:27 2018 +0200

Merge pull request #6269: Fix accidental rename of AwsModuleTest to 
AwsModuleAmazonSNSMock

 .../io/aws/options/{AwsModuleAmazonSNSMock.java => AwsModuleTest.java}  | 2 +-
 .../src/test/java/org/apache/beam/sdk/io/aws/s3/S3FileSystemTest.java   | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

[jira] [Created] (BEAM-5239) Allow configure latencyTrackingInterval

[Jozef Vilcek (JIRA)]

Jozef Vilcek created BEAM-5239:
--

 Summary: Allow configure latencyTrackingInterval
 Key: BEAM-5239
 URL: https://issues.apache.org/jira/browse/BEAM-5239
 Project: Beam
  Issue Type: New Feature
  Components: runner-flink
Affects Versions: 2.6.0
Reporter: Jozef Vilcek
Assignee: Aljoscha Krettek


Because of FLINK-10226, we need to be able to set latencyTrackingConfiguration 
for flink via FlinkPipelineOptions



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (BEAM-5239) Allow configure latencyTrackingInterval

[Jozef Vilcek (JIRA)]

[ 
https://issues.apache.org/jira/browse/BEAM-5239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16593612#comment-16593612
 ] 

Jozef Vilcek commented on BEAM-5239:


Going to create PR

> Allow configure latencyTrackingInterval
> ---
>
> Key: BEAM-5239
> URL: https://issues.apache.org/jira/browse/BEAM-5239
> Project: Beam
>  Issue Type: New Feature
>  Components: runner-flink
>Affects Versions: 2.6.0
>Reporter: Jozef Vilcek
>Assignee: Aljoscha Krettek
>Priority: Major
>
> Because of FLINK-10226, we need to be able to set 
> latencyTrackingConfiguration for flink via FlinkPipelineOptions



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Build failed in Jenkins: beam_PostCommit_Java_GradleBuild #1358

[Apache Jenkins Server]

See 


Changes:

[ajhalaria] Fix accidental rename of AwsModuleTest to AwsModuleAmazonSNSMock

--
[...truncated 19.81 MB...]
INFO: 2018-08-27T13:32:18.755Z: Fusing consumer SpannerIO.Write/Write 
mutations to Cloud Spanner/Sample keys/GroupByKey/Reify into 
SpannerIO.Write/Write mutations to Cloud Spanner/Sample 
keys/GroupByKey+SpannerIO.Write/Write mutations to Cloud Spanner/Sample 
keys/Combine.GroupedValues/Partial
Aug 27, 2018 1:32:20 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2018-08-27T13:32:18.800Z: Fusing consumer SpannerIO.Write/Write 
mutations to Cloud Spanner/Sample keys/GroupByKey+SpannerIO.Write/Write 
mutations to Cloud Spanner/Sample keys/Combine.GroupedValues/Partial into 
SpannerIO.Write/Write mutations to Cloud Spanner/Extract keys
Aug 27, 2018 1:32:20 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2018-08-27T13:32:18.848Z: Fusing consumer SpannerIO.Write/Write 
mutations to Cloud Spanner/Wait.OnSignal/To wait view 
0/Sample.Any/Combine.globally(SampleAny)/Combine.perKey(SampleAny)/GroupByKey/Write
 into SpannerIO.Write/Write mutations to Cloud Spanner/Wait.OnSignal/To wait 
view 
0/Sample.Any/Combine.globally(SampleAny)/Combine.perKey(SampleAny)/GroupByKey/Reify
Aug 27, 2018 1:32:20 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2018-08-27T13:32:18.885Z: Fusing consumer SpannerIO.Write/Write 
mutations to Cloud Spanner/Keys sample as view/GBKaSVForSize/Write into 
SpannerIO.Write/Write mutations to Cloud Spanner/Keys sample as 
view/ParMultiDo(ToIsmRecordForMapLike)
Aug 27, 2018 1:32:20 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2018-08-27T13:32:18.930Z: Fusing consumer SpannerIO.Write/Write 
mutations to Cloud Spanner/Wait.OnSignal/To wait view 
0/View.AsList/ParDo(ToIsmRecordForGlobalWindow) into SpannerIO.Write/Write 
mutations to Cloud Spanner/Wait.OnSignal/To wait view 
0/Sample.Any/Flatten.Iterables/FlattenIterables/FlatMap
Aug 27, 2018 1:32:20 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2018-08-27T13:32:18.975Z: Fusing consumer SpannerIO.Write/Write 
mutations to Cloud Spanner/Keys sample as view/GBKaSVForKeys/Write into 
SpannerIO.Write/Write mutations to Cloud Spanner/Keys sample as 
view/ParMultiDo(ToIsmRecordForMapLike)
Aug 27, 2018 1:32:20 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2018-08-27T13:32:19.019Z: Fusing consumer SpannerIO.Write/Write 
mutations to Cloud Spanner/Wait.OnSignal/To wait view 
0/Sample.Any/Flatten.Iterables/FlattenIterables/FlatMap into 
SpannerIO.Write/Write mutations to Cloud Spanner/Wait.OnSignal/To wait view 
0/Sample.Any/Combine.globally(SampleAny)/Values/Values/Map
Aug 27, 2018 1:32:20 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2018-08-27T13:32:19.065Z: Fusing consumer SpannerIO.Write/Write 
mutations to Cloud Spanner/Wait.OnSignal/To wait view 
0/Sample.Any/Combine.globally(SampleAny)/Values/Values/Map into 
SpannerIO.Write/Write mutations to Cloud Spanner/Wait.OnSignal/To wait view 
0/Sample.Any/Combine.globally(SampleAny)/Combine.perKey(SampleAny)/Combine.GroupedValues/Extract
Aug 27, 2018 1:32:20 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2018-08-27T13:32:19.110Z: Fusing consumer SpannerIO.Write/Write 
mutations to Cloud Spanner/Keys sample as view/ParDo(ToIsmMetadataRecordForKey) 
into SpannerIO.Write/Write mutations to Cloud Spanner/Keys sample as 
view/GBKaSVForKeys/Read
Aug 27, 2018 1:32:20 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2018-08-27T13:32:19.154Z: Fusing consumer SpannerIO.Write/Write 
mutations to Cloud Spanner/Wait.OnSignal/To wait view 
0/Sample.Any/Combine.globally(SampleAny)/Combine.perKey(SampleAny)/Combine.GroupedValues/Extract
 into SpannerIO.Write/Write mutations to Cloud Spanner/Wait.OnSignal/To wait 
view 
0/Sample.Any/Combine.globally(SampleAny)/Combine.perKey(SampleAny)/Combine.GroupedValues
Aug 27, 2018 1:32:20 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2018-08-27T13:32:19.199Z: Fusing consumer SpannerIO.Write/Write 
mutations to Cloud Spanner/Wait.OnSignal/To wait view 
0/Sample.Any/Combine.globally(SampleAny)/WithKeys/AddKeys/Map into 
SpannerIO.Write/Write mutations to Cloud Spanner/Wait.OnSignal/To wait view 
0/ParDo(CollectWindows)
Aug 27, 2018 1:32:20 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2018-08-27T13:32:19.240Z: Fusing consumer SpannerIO.Write/Write 
mutations to Cloud Spanner/Wait.OnSignal/To wait view 
0/Sample.Any/C

[jira] [Comment Edited] (BEAM-5172) org.apache.beam.sdk.io.elasticsearch/ElasticsearchIOTest is flaky

[Etienne Chauchot (JIRA)]

[ 
https://issues.apache.org/jira/browse/BEAM-5172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16593656#comment-16593656
 ] 

Etienne Chauchot edited comment on BEAM-5172 at 8/27/18 1:37 PM:
-

For testWrite timeout in ES2: starting the embedded ES node is blocking so 
connection timeout in testWrite cannot be due to embedded ES not started when 
the test runs. I'll add a simple temporisation if the connection fails before 
launching the tests.


was (Author: echauchot):
For testWrite timeout in ES2: starting the embedded ES node is blocking so 
connection timeout in testWrite cannot be due to embedded ES not started when 
the test runs. I'll add a simple temporisation if the connection fail before 
launching the tests.

> org.apache.beam.sdk.io.elasticsearch/ElasticsearchIOTest is flaky
> -
>
> Key: BEAM-5172
> URL: https://issues.apache.org/jira/browse/BEAM-5172
> Project: Beam
>  Issue Type: Bug
>  Components: io-java-elasticsearch, test-failures
>Reporter: Valentyn Tymofieiev
>Assignee: Etienne Chauchot
>Priority: Major
>
> In a recent PostCommit builld, 
> https://builds.apache.org/job/beam_PostCommit_Java_GradleBuild/1290/testReport/junit/org.apache.beam.sdk.io.elasticsearch/ElasticsearchIOTest/testRead/
>  failed with:
> Error Message
> java.lang.AssertionError: Count/Flatten.PCollections.out: 
> Expected: <400L>
>  but: was <470L>
> Stacktrace
> java.lang.AssertionError: Count/Flatten.PCollections.out: 
> Expected: <400L>
>  but: was <470L>
>   at 
> org.apache.beam.sdk.testing.PAssert$PAssertionSite.capture(PAssert.java:168)
>   at org.apache.beam.sdk.testing.PAssert.thatSingleton(PAssert.java:413)
>   at org.apache.beam.sdk.testing.PAssert.thatSingleton(PAssert.java:404)
>   at 
> org.apache.beam.sdk.io.elasticsearch.ElasticsearchIOTestCommon.testRead(ElasticsearchIOTestCommon.java:124)
>   at 
> org.apache.beam.sdk.io.elasticsearch.ElasticsearchIOTest.testRead(ElasticsearchIOTest.java:125)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at 
> org.junit.rules.ExpectedException$ExpectedExceptionStatement.evaluate(ExpectedException.java:239)
>   at 
> org.apache.beam.sdk.testing.TestPipeline$1.evaluate(TestPipeline.java:319)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>   at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:106)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
>   at 
> org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:66)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
>   at sun.ref

[jira] [Commented] (BEAM-5172) org.apache.beam.sdk.io.elasticsearch/ElasticsearchIOTest is flaky

[Etienne Chauchot (JIRA)]

[ 
https://issues.apache.org/jira/browse/BEAM-5172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16593656#comment-16593656
 ] 

Etienne Chauchot commented on BEAM-5172:


For testWrite timeout in ES2: starting the embedded ES node is blocking so 
connection timeout in testWrite cannot be due to embedded ES not started when 
the test runs. I'll add a simple temporisation if the connection fail before 
launching the tests.

> org.apache.beam.sdk.io.elasticsearch/ElasticsearchIOTest is flaky
> -
>
> Key: BEAM-5172
> URL: https://issues.apache.org/jira/browse/BEAM-5172
> Project: Beam
>  Issue Type: Bug
>  Components: io-java-elasticsearch, test-failures
>Reporter: Valentyn Tymofieiev
>Assignee: Etienne Chauchot
>Priority: Major
>
> In a recent PostCommit builld, 
> https://builds.apache.org/job/beam_PostCommit_Java_GradleBuild/1290/testReport/junit/org.apache.beam.sdk.io.elasticsearch/ElasticsearchIOTest/testRead/
>  failed with:
> Error Message
> java.lang.AssertionError: Count/Flatten.PCollections.out: 
> Expected: <400L>
>  but: was <470L>
> Stacktrace
> java.lang.AssertionError: Count/Flatten.PCollections.out: 
> Expected: <400L>
>  but: was <470L>
>   at 
> org.apache.beam.sdk.testing.PAssert$PAssertionSite.capture(PAssert.java:168)
>   at org.apache.beam.sdk.testing.PAssert.thatSingleton(PAssert.java:413)
>   at org.apache.beam.sdk.testing.PAssert.thatSingleton(PAssert.java:404)
>   at 
> org.apache.beam.sdk.io.elasticsearch.ElasticsearchIOTestCommon.testRead(ElasticsearchIOTestCommon.java:124)
>   at 
> org.apache.beam.sdk.io.elasticsearch.ElasticsearchIOTest.testRead(ElasticsearchIOTest.java:125)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at 
> org.junit.rules.ExpectedException$ExpectedExceptionStatement.evaluate(ExpectedException.java:239)
>   at 
> org.apache.beam.sdk.testing.TestPipeline$1.evaluate(TestPipeline.java:319)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>   at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:106)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
>   at 
> org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:66)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.gradle.i

[jira] [Work logged] (BEAM-5062) Add ability to configure S3ClientOptions

[ASF GitHub Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-5062?focusedWorklogId=138392&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-138392
 ]

ASF GitHub Bot logged work on BEAM-5062:


Author: ASF GitHub Bot
Created on: 27/Aug/18 13:41
Start Date: 27/Aug/18 13:41
Worklog Time Spent: 10m 
  Work Description: iemejia commented on issue #6122: [BEAM-5062] Add 
ability to provide custom S3ClientOptions
URL: https://github.com/apache/beam/pull/6122#issuecomment-416230340
 
 
   Hi, I see why `S3ClientOptions` seems cleaner, after looking at the comment 
in the linked ticket it seems the future of the S3 API is builder-oriented so 
maybe worth going back to the suggested track. WDYT ? (again not that I am 
super fan of letting the builder open but don't see a better trade-off).


This is an automated message from the Apache Git Service.
To respond to the message, please log on 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: 138392)
Time Spent: 2h 10m  (was: 2h)

> Add ability to configure S3ClientOptions
> 
>
> Key: BEAM-5062
> URL: https://issues.apache.org/jira/browse/BEAM-5062
> Project: Beam
>  Issue Type: Improvement
>  Components: io-java-aws
>Reporter: Kirill Kozlov
>Assignee: Kirill Kozlov
>Priority: Minor
>  Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> It would be very useful to have an ability to configure 
> [S3ClientOptions|https://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/s3/S3ClientOptions.html]
>  for Apache Beam jobs.
> For example, there are some implementations of S3, that does not support 
> virtual-hosted-style URLs for buckets, only path-style. Currently it's 
> impossible to enable path style access for amazon s3 client, which is used by 
> an apache-beam job.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Work logged] (BEAM-5239) Allow configure latencyTrackingInterval

[ASF GitHub Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-5239?focusedWorklogId=138396&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-138396
 ]

ASF GitHub Bot logged work on BEAM-5239:


Author: ASF GitHub Bot
Created on: 27/Aug/18 13:50
Start Date: 27/Aug/18 13:50
Worklog Time Spent: 10m 
  Work Description: JozoVilcek opened a new pull request #6278: [BEAM-5239] 
Enable to configure latencyTrackingInterval
URL: https://github.com/apache/beam/pull/6278
 
 
   
   
   
   
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on 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: 138396)
Time Spent: 10m
Remaining Estimate: 0h

> Allow configure latencyTrackingInterval
> ---
>
> Key: BEAM-5239
> URL: https://issues.apache.org/jira/browse/BEAM-5239
> Project: Beam
>  Issue Type: New Feature
>  Components: runner-flink
>Affects Versions: 2.6.0
>Reporter: Jozef Vilcek
>Assignee: Aljoscha Krettek
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Because of FLINK-10226, we need to be able to set 
> latencyTrackingConfiguration for flink via FlinkPipelineOptions



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Work logged] (BEAM-5172) org.apache.beam.sdk.io.elasticsearch/ElasticsearchIOTest is flaky

[ASF GitHub Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-5172?focusedWorklogId=138423&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-138423
 ]

ASF GitHub Bot logged work on BEAM-5172:


Author: ASF GitHub Bot
Created on: 27/Aug/18 14:48
Start Date: 27/Aug/18 14:48
Worklog Time Spent: 10m 
  Work Description: echauchot opened a new pull request #6279:  [BEAM-5172] 
Fix Elasticsearch UTests flakiness
URL: https://github.com/apache/beam/pull/6279
 
 
   
   This PR fixes the flakiness in some ES tests: 
   - in testRead() index contains more data than inserted
   - in testWrite() connection timeout to embedded Elasticsearch 2.4.
   
   Every flakiness issue is tackled in one specific commit. IMHO for the sake 
of history isolation they should not be squashed.
   R: @timrobertson100
   
   Follow this checklist to help us incorporate your contribution quickly and 
easily:
   
- [X] Format the pull request title like `[BEAM-XXX] Fixes bug in 
ApproximateQuantiles`, where you replace `BEAM-XXX` with the appropriate JIRA 
issue, if applicable. This will automatically link the pull request to the 
issue.
- [X] If this contribution is large, please file an Apache [Individual 
Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
   
   It will help us expedite review of your Pull Request if you tag someone 
(e.g. `@username`) to look at it.
   
   Post-Commit Tests Status (on master branch)
   

   
   Lang | SDK | Apex | Dataflow | Flink | Gearpump | Samza | Spark
   --- | --- | --- | --- | --- | --- | --- | ---
   Go | [![Build 
Status](https://builds.apache.org/job/beam_PostCommit_Go_GradleBuild/lastCompletedBuild/badge/icon)](https://builds.apache.org/job/beam_PostCommit_Go_GradleBuild/lastCompletedBuild/)
 | --- | --- | --- | --- | --- | ---
   Java | [![Build 
Status](https://builds.apache.org/job/beam_PostCommit_Java_GradleBuild/lastCompletedBuild/badge/icon)](https://builds.apache.org/job/beam_PostCommit_Java_GradleBuild/lastCompletedBuild/)
 | [![Build 
Status](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Apex_Gradle/lastCompletedBuild/badge/icon)](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Apex_Gradle/lastCompletedBuild/)
 | [![Build 
Status](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Dataflow_Gradle/lastCompletedBuild/badge/icon)](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Dataflow_Gradle/lastCompletedBuild/)
 | [![Build 
Status](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Flink_Gradle/lastCompletedBuild/badge/icon)](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Flink_Gradle/lastCompletedBuild/)
 | [![Build 
Status](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Gearpump_Gradle/lastCompletedBuild/badge/icon)](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Gearpump_Gradle/lastCompletedBuild/)
 | [![Build 
Status](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Samza_Gradle/lastCompletedBuild/badge/icon)](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Samza_Gradle/lastCompletedBuild/)
 | [![Build 
Status](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Spark_Gradle/lastCompletedBuild/badge/icon)](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Spark_Gradle/lastCompletedBuild/)
   Python | [![Build 
Status](https://builds.apache.org/job/beam_PostCommit_Python_Verify/lastCompletedBuild/badge/icon)](https://builds.apache.org/job/beam_PostCommit_Python_Verify/lastCompletedBuild/)
 | --- | [![Build 
Status](https://builds.apache.org/job/beam_PostCommit_Py_VR_Dataflow/lastCompletedBuild/badge/icon)](https://builds.apache.org/job/beam_PostCommit_Py_VR_Dataflow/lastCompletedBuild/)
  [![Build 
Status](https://builds.apache.org/job/beam_PostCommit_Py_ValCont/lastCompletedBuild/badge/icon)](https://builds.apache.org/job/beam_PostCommit_Py_ValCont/lastCompletedBuild/)
 | --- | --- | --- | ---
   
   
   
   
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on 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: 138423)
Time Spent: 10m
Remaining Estimate: 0h

> org.apache.beam.sdk.io.elasticsearch/ElasticsearchIOTest is flaky
> -
>
> Key: BEAM-5172
> URL: https://issues.apache.org/jira/browse/BEAM-5172
> 

[jira] [Work logged] (BEAM-4783) Spark SourceRDD Not Designed With Dynamic Allocation In Mind

[ASF GitHub Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-4783?focusedWorklogId=138431&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-138431
 ]

ASF GitHub Bot logged work on BEAM-4783:


Author: ASF GitHub Bot
Created on: 27/Aug/18 15:17
Start Date: 27/Aug/18 15:17
Worklog Time Spent: 10m 
  Work Description: kyle-winkelman commented on a change in pull request 
#6181: [BEAM-4783] Add bundleSize for splitting BoundedSources.
URL: https://github.com/apache/beam/pull/6181#discussion_r212977881
 
 

 ##
 File path: 
runners/spark/src/main/java/org/apache/beam/runners/spark/translation/GroupCombineFunctions.java
 ##
 @@ -52,13 +50,11 @@
 .map(WindowingHelpers.unwindowFunction())
 .mapToPair(TranslationUtils.toPairFunction())
 .mapToPair(CoderHelpers.toByteFunction(keyCoder, wvCoder));
-// use a default parallelism HashPartitioner.
-Partitioner partitioner = new 
HashPartitioner(rdd.rdd().sparkContext().defaultParallelism());
 
 // using mapPartitions allows to preserve the partitioner
 // and avoid unnecessary shuffle downstream.
 return pairRDD
-.groupByKey(partitioner)
+.groupByKey()
 
 Review comment:
   This will cause the 
[Partitioner.defaultPartitioner](https://github.com/apache/spark/blob/master/core/src/main/scala/org/apache/spark/Partitioner.scala#L62)
 to be used. When called on a SourceRDD this should be a HashPartitioner with 
the number of partitions equal to the number of splits created by the 
bundleSize. When called on a SourceDStream this should be a HashPartitioner 
with the number of partitions equal to the defaultParallelism.


This is an automated message from the Apache Git Service.
To respond to the message, please log on 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: 138431)
Time Spent: 40m  (was: 0.5h)

> Spark SourceRDD Not Designed With Dynamic Allocation In Mind
> 
>
> Key: BEAM-4783
> URL: https://issues.apache.org/jira/browse/BEAM-4783
> Project: Beam
>  Issue Type: Improvement
>  Components: runner-spark
>Affects Versions: 2.5.0
>Reporter: Kyle Winkelman
>Assignee: Jean-Baptiste Onofré
>Priority: Major
>  Labels: newbie
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> When the spark-runner is used along with the configuration 
> spark.dynamicAllocation.enabled=true the SourceRDD does not detect this. It 
> then falls back to the value calculated in this description:
>   // when running on YARN/SparkDeploy it's the result of max(totalCores, 
> 2).
>   // when running on Mesos it's 8.
>   // when running local it's the total number of cores (local = 1, 
> local[N] = N,
>   // local[*] = estimation of the machine's cores).
>   // ** the configuration "spark.default.parallelism" takes precedence 
> over all of the above **
> So in most cases this default is quite small. This is an issue when using a 
> very large input file as it will only get split in half.
> I believe that when Dynamic Allocation is enable the SourceRDD should use the 
> DEFAULT_BUNDLE_SIZE and possibly expose a SparkPipelineOptions that allows 
> you to change this DEFAULT_BUNDLE_SIZE.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (BEAM-4567) Can't use mongo connector with Atlas MongoDB

[Saber (JIRA)]

[ 
https://issues.apache.org/jira/browse/BEAM-4567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16593862#comment-16593862
 ] 

Saber commented on BEAM-4567:
-

Hello,

We are facing the same issue with mongodb atlas, is there any update on this 
issue ?

Thank you

> Can't use mongo connector with Atlas MongoDB
> 
>
> Key: BEAM-4567
> URL: https://issues.apache.org/jira/browse/BEAM-4567
> Project: Beam
>  Issue Type: Bug
>  Components: io-java-mongodb
>Affects Versions: 2.4.0
> Environment: Google Cloud Dataflow
>Reporter: Lucas de Sio Rosa
>Assignee: Jean-Baptiste Onofré
>Priority: Major
>  Labels: mongodb
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> I can't use the MongoDB connector with a managed Atlas instance. The current 
> implementations makes use of splitVector which is a high-privilege function 
> that cannot be assigned to any user in Atlas.
> An open Jira issue for MongoDB suggests using $sample and $bucketAuto to 
> circunvent this necessity.
> Following is the exception thrown (removed some identifiable information):
> Exception in thread "main" 
> org.apache.beam.sdk.Pipeline$PipelineExecutionException: 
> com.mongodb.MongoCommandException: Command failed with error 13: 'not 
> authorized on  to execute command \{ splitVector: 
> ".", keyPattern: { _id: 1 }, force: false, maxChunkSize: 1 
> }' on server . The full response is \{ "ok" : 0.0, "errmsg" : "not 
> authorized on  to execute command { splitVector: 
> \".\", keyPattern: { _id: 1 }, force: false, maxChunkSize: 
> 1 }", "code" : 13, "codeName" : "Unauthorized" }
>  
>  at org.apache.beam.sdk.Pipeline.run(Pipeline.java:317)
>  
>  at org.apache.beam.sdk.Pipeline.run(Pipeline.java:297)
>  
>  at 
> br.dotz.datalake.ingest.mongodb.MongoDBCollectorPipeline.main(MongoDBCollectorPipeline.java:27)
>  
> Caused by: com.mongodb.MongoCommandException: Command failed with error 13: 
> 'not authorized on  to execute command \{ splitVector: 
> ".", keyPattern: { _id: 1 }, force: false, maxChunkSize: 1 
> }' on server . The full response is \{ "ok" : 0.0, "errmsg" : "not 
> authorized on  to execute command { splitVector: 
> \".\", keyPattern: { _id: 1 }, force: false, maxChunkSize: 
> 1 }", "code" : 13, "codeName" : "Unauthorized" }
>  
>  at 
> com.mongodb.connection.ProtocolHelper.getCommandFailureException(ProtocolHelper.java:115)
>  
>  at com.mongodb.connection.CommandProtocol.execute(CommandProtocol.java:114)
>  
>  at 
> com.mongodb.connection.DefaultServer$DefaultServerProtocolExecutor.execute(DefaultServer.java:159)
>  
>  at 
> com.mongodb.connection.DefaultServerConnection.executeProtocol(DefaultServerConnection.java:286)
>  
>  at 
> com.mongodb.connection.DefaultServerConnection.command(DefaultServerConnection.java:173)
>  
>  at 
> com.mongodb.operation.CommandOperationHelper.executeWrappedCommandProtocol(CommandOperationHelper.java:215)
>  
>  at 
> com.mongodb.operation.CommandOperationHelper.executeWrappedCommandProtocol(CommandOperationHelper.java:186)
>  
>  at 
> com.mongodb.operation.CommandOperationHelper.executeWrappedCommandProtocol(CommandOperationHelper.java:178)
>  
>  at 
> com.mongodb.operation.CommandOperationHelper.executeWrappedCommandProtocol(CommandOperationHelper.java:91)
>  
>  at 
> com.mongodb.operation.CommandOperationHelper.executeWrappedCommandProtocol(CommandOperationHelper.java:84)
>  
>  at 
> com.mongodb.operation.CommandReadOperation.execute(CommandReadOperation.java:55)
>  
>  at com.mongodb.Mongo.execute(Mongo.java:772)
>  
>  at com.mongodb.Mongo$2.execute(Mongo.java:759)
>  
>  at com.mongodb.MongoDatabaseImpl.runCommand(MongoDatabaseImpl.java:130)
>  
>  at com.mongodb.MongoDatabaseImpl.runCommand(MongoDatabaseImpl.java:124)
>  
>  at com.mongodb.MongoDatabaseImpl.runCommand(MongoDatabaseImpl.java:114)
>  
>  at 
> org.apache.beam.sdk.io.mongodb.MongoDbIO$BoundedMongoDbSource.split(MongoDbIO.java:332)
>  
>  at 
> org.apache.beam.runners.direct.BoundedReadEvaluatorFactory$InputProvider.getInitialInputs(BoundedReadEvaluatorFactory.java:210)
>  
>  at 
> org.apache.beam.runners.direct.ReadEvaluatorFactory$InputProvider.getInitialInputs(ReadEvaluatorFactory.java:87)
>  
>  at 
> org.apache.beam.runners.direct.RootProviderRegistry.getInitialInputs(RootProviderRegistry.java:62)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (BEAM-5154) Add TestResults reporter for python postcommit tests.

[Mikhail Gryzykhin (JIRA)]

[ 
https://issues.apache.org/jira/browse/BEAM-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16593866#comment-16593866
 ] 

Mikhail Gryzykhin commented on BEAM-5154:
-

Test results reporter is added for tests.

Auto Jira ticket creation need testing after INFRA configured plugin.

> Add TestResults reporter for python postcommit tests.
> -
>
> Key: BEAM-5154
> URL: https://issues.apache.org/jira/browse/BEAM-5154
> Project: Beam
>  Issue Type: Bug
>  Components: testing
>Reporter: Mikhail Gryzykhin
>Assignee: Mikhail Gryzykhin
>Priority: Major
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> We want to configure TestResults reporter for:
>  # tracking history of tests
>  # Auto Jira ticket creation on test failures.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (BEAM-5240) Create post-commit tests dashboard

[Mikhail Gryzykhin (JIRA)]

Mikhail Gryzykhin created BEAM-5240:
---

 Summary: Create post-commit tests dashboard
 Key: BEAM-5240
 URL: https://issues.apache.org/jira/browse/BEAM-5240
 Project: Beam
  Issue Type: Sub-task
  Components: testing
Reporter: Mikhail Gryzykhin
Assignee: Mikhail Gryzykhin






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (BEAM-5240) Create post-commit tests dashboard

[Mikhail Gryzykhin (JIRA)]

[ 
https://issues.apache.org/jira/browse/BEAM-5240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16593870#comment-16593870
 ] 

Mikhail Gryzykhin commented on BEAM-5240:
-

Dashboard is currently running at  
[http://104.154.241.245.|http://104.154.241.245/]

It is needed to add Jira tickets statistics and potentially add domain name.

> Create post-commit tests dashboard
> --
>
> Key: BEAM-5240
> URL: https://issues.apache.org/jira/browse/BEAM-5240
> Project: Beam
>  Issue Type: Sub-task
>  Components: testing
>Reporter: Mikhail Gryzykhin
>Assignee: Mikhail Gryzykhin
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (BEAM-5207) :beam-runners-apex:compileTestJava dependency issue

[Andrew Pilloud (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Pilloud resolved BEAM-5207.
--
   Resolution: Duplicate
Fix Version/s: Not applicable

I'm convinced this is BEAM-5035 with logs lost in the race

> :beam-runners-apex:compileTestJava dependency issue
> ---
>
> Key: BEAM-5207
> URL: https://issues.apache.org/jira/browse/BEAM-5207
> Project: Beam
>  Issue Type: New Feature
>  Components: build-system
>Reporter: Andrew Pilloud
>Assignee: Luke Cwik
>Priority: Major
> Fix For: Not applicable
>
>
> Build failed without much in the way of errors, it appears to be some sort of 
> race condition. 
> https://builds.apache.org/job/beam_PostCommit_Java_GradleBuild/1321
>  
> All input files are considered out-of-date for incremental task 
> ':beam-runners-apex:compileTestJava'



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (BEAM-5116) beam_PostCommit_Java_GradleBuild :beam-runners-google-cloud-dataflow-java:examplesJavaIntegrationTest Failed build. System failure.

[Mikhail Gryzykhin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BEAM-5116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mikhail Gryzykhin reassigned BEAM-5116:
---

Assignee: (was: Mikhail Gryzykhin)

> beam_PostCommit_Java_GradleBuild 
> :beam-runners-google-cloud-dataflow-java:examplesJavaIntegrationTest Failed 
> build. System failure.
> ---
>
> Key: BEAM-5116
> URL: https://issues.apache.org/jira/browse/BEAM-5116
> Project: Beam
>  Issue Type: Bug
>  Components: build-system, test-failures
>Reporter: Mikhail Gryzykhin
>Priority: Major
>
> [https://builds.apache.org/view/A-D/view/Beam/job/beam_PostCommit_Java_GradleBuild/1214/]
> Find log subset below. Suspect is fail is due to memory limitations or zip 
> source availability/integrity.
> > Task :beam-runners-google-cloud-dataflow-java:examplesJavaIntegrationTest 
> > FAILED
> Build cache key for task 
> ':beam-runners-google-cloud-dataflow-java:examplesJavaIntegrationTest' is 
> 12c45ad8abd6cf3734c37d0c2592d429
> Task ':beam-runners-google-cloud-dataflow-java:examplesJavaIntegrationTest' 
> is not up-to-date because:
>   No history is available.
> Starting process 'Gradle Test Executor 129'. Working directory: 
> /home/jenkins/jenkins-slave/workspace/beam_PostCommit_Java_GradleBuild/src/runners/google-cloud-dataflow-java
>  Command: /usr/local/asfpackages/java/jdk1.8.0_172/bin/java 
> -DbeamTestPipelineOptions=["--runner=TestDataflowRunner","--project=apache-beam-testing","--tempRoot=gs://temp-storage-for-end-to-end-tests"]
>  
> -Djava.security.manager=worker.org.gradle.process.internal.worker.child.BootstrapSecurityManager
>  -Dorg.gradle.native=false -Dfile.encoding=UTF-8 -Duser.country=US 
> -Duser.language=en -Duser.variant -ea -cp 
> /home/jenkins/.gradle/caches/4.8/workerMain/gradle-worker.jar 
> worker.org.gradle.process.internal.worker.GradleWorkerMain 'Gradle Test 
> Executor 129'
> Successfully started process 'Gradle Test Executor 129'
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGBUS (0x7) at pc=0x7fc14674a4e2, pid=7054, tid=0x7fc0c1150700
> #
> # JRE version: Java(TM) SE Runtime Environment (8.0_172-b11) (build 
> 1.8.0_172-b11)
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.172-b11 mixed mode 
> linux-amd64 compressed oops)
> # Problematic frame:
> # C  [libzip.so+0x124e2]  newEntry+0x62
> #
> # Failed to write core dump. Core dumps have been disabled. To enable core 
> dumping, try "ulimit -c unlimited" before starting Java again
> #
> # An error report file with more information is saved as:
> # 
> /home/jenkins/jenkins-slave/workspace/beam_PostCommit_Java_GradleBuild/src/runners/google-cloud-dataflow-java/hs_err_pid7054.log
> Compiled method (nm)1382  211 n 0   
> java.util.zip.ZipFile::getEntry (native)
>  total in heap  [0x7fc1313495d0,0x7fc131349940] = 880
>  relocation [0x7fc1313496f8,0x7fc131349740] = 72
>  main code  [0x7fc131349740,0x7fc131349940] = 512
> #
> # If you would like to submit a bug report, please visit:
> #   
> [http://bugreport.java.com/bugreport/crash.jsp]
> # The crash happened outside the Java Virtual Machine in native code.
> # See problematic frame for where to report the bug.
> #



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (BEAM-5122) beam_PostCommit_Java_GradleBuild org.apache.beam.sdk.extensions.sql.meta.provider.pubsub.PubsubJsonIT.testUsesDlq

[Andrew Pilloud (JIRA)]

[ 
https://issues.apache.org/jira/browse/BEAM-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16593887#comment-16593887
 ] 

Andrew Pilloud commented on BEAM-5122:
--

https://builds.apache.org/job/beam_PostCommit_Java_GradleBuild/1350/testReport/junit/org.apache.beam.sdk.extensions.sql.meta.provider.pubsub/PubsubJsonIT/testUsesDlq/

> beam_PostCommit_Java_GradleBuild 
> org.apache.beam.sdk.extensions.sql.meta.provider.pubsub.PubsubJsonIT.testUsesDlq
> -
>
> Key: BEAM-5122
> URL: https://issues.apache.org/jira/browse/BEAM-5122
> Project: Beam
>  Issue Type: Bug
>  Components: test-failures
>Reporter: Mikhail Gryzykhin
>Assignee: Anton Kedin
>Priority: Critical
>  Time Spent: 6.5h
>  Remaining Estimate: 0h
>
> [https://builds.apache.org/job/beam_PostCommit_Java_GradleBuild/1216/testReport/junit/org.apache.beam.sdk.extensions.sql.meta.provider.pubsub/PubsubJsonIT/testUsesDlq/history/]
> Test flakes with timeout of getting update on pubsub:
> java.lang.AssertionError: Did not receive signal on 
> projects/apache-beam-testing/subscriptions/result-subscription--6677803195159868432
>  in 60s at 
> org.apache.beam.sdk.io.gcp.pubsub.TestPubsubSignal.pollForResultForDuration(TestPubsubSignal.java:269)
>  at 
> org.apache.beam.sdk.io.gcp.pubsub.TestPubsubSignal.waitForSuccess(TestPubsubSignal.java:237)
>  at 
> org.apache.beam.sdk.extensions.sql.meta.provider.pubsub.PubsubJsonIT.testUsesDlq(PubsubJsonIT.java:206)
> [https://builds.apache.org/job/beam_PostCommit_Java_GradleBuild/1216/testReport/org.apache.beam.sdk.extensions.sql.meta.provider.pubsub/PubsubJsonIT/testUsesDlq/]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (BEAM-5122) beam_PostCommit_Java_GradleBuild org.apache.beam.sdk.extensions.sql.meta.provider.pubsub.PubsubJsonIT.testUsesDlq

[Andrew Pilloud (JIRA)]

[ 
https://issues.apache.org/jira/browse/BEAM-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16593889#comment-16593889
 ] 

Andrew Pilloud commented on BEAM-5122:
--

https://builds.apache.org/job/beam_PostCommit_Java_GradleBuild/1353/testReport/junit/org.apache.beam.sdk.extensions.sql.meta.provider.pubsub/PubsubJsonIT/testUsesDlq/

> beam_PostCommit_Java_GradleBuild 
> org.apache.beam.sdk.extensions.sql.meta.provider.pubsub.PubsubJsonIT.testUsesDlq
> -
>
> Key: BEAM-5122
> URL: https://issues.apache.org/jira/browse/BEAM-5122
> Project: Beam
>  Issue Type: Bug
>  Components: test-failures
>Reporter: Mikhail Gryzykhin
>Assignee: Anton Kedin
>Priority: Critical
>  Time Spent: 6.5h
>  Remaining Estimate: 0h
>
> [https://builds.apache.org/job/beam_PostCommit_Java_GradleBuild/1216/testReport/junit/org.apache.beam.sdk.extensions.sql.meta.provider.pubsub/PubsubJsonIT/testUsesDlq/history/]
> Test flakes with timeout of getting update on pubsub:
> java.lang.AssertionError: Did not receive signal on 
> projects/apache-beam-testing/subscriptions/result-subscription--6677803195159868432
>  in 60s at 
> org.apache.beam.sdk.io.gcp.pubsub.TestPubsubSignal.pollForResultForDuration(TestPubsubSignal.java:269)
>  at 
> org.apache.beam.sdk.io.gcp.pubsub.TestPubsubSignal.waitForSuccess(TestPubsubSignal.java:237)
>  at 
> org.apache.beam.sdk.extensions.sql.meta.provider.pubsub.PubsubJsonIT.testUsesDlq(PubsubJsonIT.java:206)
> [https://builds.apache.org/job/beam_PostCommit_Java_GradleBuild/1216/testReport/org.apache.beam.sdk.extensions.sql.meta.provider.pubsub/PubsubJsonIT/testUsesDlq/]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)