Sent this to [hidden email], but that might not be the appropriate forum for it. Finally got a chance to sit down and run through a few tests. Upfront, I have been able to resolve my issue sufficiently to move forward, but seems there’s an issue with the current bits for both 1.0-SNAPSHOT and 0.10-SNAPSHOT in the remote Maven repos. Notes
0.10-SNAPSHOT source build Steps
Result
0.10-SNAPSHOT with fetched binary dependencies Steps
Result
1.0-SNAPSHOT source build Steps
Result
1.0-SNAPSHOT with fetched binary dependencies Steps
Result
Discussion
Prez Cannady p: 617 500 3378 |
One correction, line 3 of 1.0-SHAPSHOT source build should read “checked out master branch (snapshot version 1.0-SNAPSHOT)."
Prez Cannady p: 617 500 3378
|
Hi Prez, thanks a lot for the thorough research you did on this issue. The issue with "1.0-SNAPSHOT with fetched binary dependencies" should be resolved by a fix I've pushed to master yesterday: a) The "change-scala-version" script wasn't adopted to the renamed examples directory, that's why it failed renaming the artifacts for _2.11. That's why the maven dependencies ended up being mixed between Scala 2.11 and 2.10. b) The deployment of the scala 2.11 build failed because the "flink-table" module contained java code in the scala/ directory. Also the code was not compliant with our java checkstyle. I hope with these two fixes, the scala 2.11 problems are resolved for now. Regards, Robert On Tue, Jan 19, 2016 at 6:43 AM, Prez Cannady <[hidden email]> wrote:
|
Morning, Robert.
You’re right; the 1.0-SNAPSHOT with fetched binaries issue is resolved now. Unfortunately, it now emits the same error as 0.10-SNAPSHOT with fetched binaries. There is a fix for that: It’s definitely in the release-0.10 and master branches I grabbed the sources jar for the latest 1.0-SNAPSHOT and 0.10-SNAPSHOT: /** * Gets the Flink (internal) accumulators values. * @return the serialized map */ public Map<AccumulatorRegistry.Metric, Accumulator<?, ?>> deserializeFlinkAccumulators() throws IOException, ClassNotFoundException { return flinkAccumulators.deserializeValue(ClassLoader.getSystemClassLoader()); } ClassLoader.getSystemClassLoader() should be getClass().getClassLoader(). Not sure why it’s not taking in the build, but there’s the problem. Prez Cannady p: 617 500 3378
|
Hi Prez! I merged the pull request into master a while back. Have a look here (https://github.com/apache/flink/commits/master commits of January 15th). Is it possible that you are using a cached older version? Greetings, Stephan On Wed, Jan 20, 2016 at 4:00 PM, Prez Cannady <[hidden email]> wrote:
|
Apologies for the late reply; been on the road.
I’ve been blowing away my Maven and Gradle repos for each test to make sure I’m pulling down the latest snapshots. I’ve also looked into the source jars directly from the snapshot repo: 1.0-SNAPSHOT: https://repository.apache.org/content/repositories/snapshots/org/apache/flink/flink-runtime_2.11/1.0-SNAPSHOT/ 0.10-SNAPSHOT: https://repository.apache.org/content/repositories/snapshots/org/apache/flink/flink-runtime_2.11/0.10-SNAPSHOT/ I note that the jars date to January 14, which may be right on the cusp of when this commit was taken (7 days ago). And while the change you and I first discussed made it (https://github.com/apache/flink/commit/0ae46b596949808f56c40bd7a68f478bc10206ab), the second did not (https://github.com/apache/flink/commit/cfcb5d7ba5c22295c0ae628f8d9a2447e2286985). Perhaps there’s a fresher repo I should be using? Prez Cannady p: 617 500 3378
|
Hi Prez, https://repository.apache.org/content/repositories/snapshots is the only repository distributing snapshot builds. The latest scala 2.11 1.0-SNAPSHOT flink runtime: https://repository.apache.org/content/repositories/snapshots/org/apache/flink/flink-runtime_2.11/1.0-SNAPSHOT/flink-runtime_2.11-1.0-20160121.212759-212-sources.jar contains both your changes. The problem with the snapshot builds is that they are not going through always (for example when the travis build times out). It might be the case that that 0.10-SNAPSHOT build timed out ... The likelihood that this happens is higher for 0.10-SNAPSHOT because we are not publishing into that branch that frequently. If you urgently need the 0.10-SNAPSHOT version fixed, I can deploy the version manually for you. Otherwise, I would recommend to use 1.0-SNAPSHOT. On Thu, Jan 21, 2016 at 5:54 PM, Prez Cannady <[hidden email]> wrote:
|
Free forum by Nabble | Edit this page |