[
https://issues.apache.org/jira/browse/FLINK-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14511638#comment-14511638
]
Fabian Hueske commented on FLINK-1848:
--
No, the issue hasn't been fixed yet
> Paths
[
https://issues.apache.org/jira/browse/FLINK-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14511631#comment-14511631
]
Fabian Hueske commented on FLINK-1682:
--
The following classes in the {{flink-optimize
[
https://issues.apache.org/jira/browse/FLINK-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14511585#comment-14511585
]
ASF GitHub Bot commented on FLINK-1615:
---
Github user Elbehery commented on the pull
Github user Elbehery commented on the pull request:
https://github.com/apache/flink/pull/621#issuecomment-96041144
@aljoscha Yes I wrote these Pojos myself, and I have tested the handler to
retrieve distinct data, coz the tweets has redundant fields.
I have added the License
[
https://issues.apache.org/jira/browse/FLINK-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14511377#comment-14511377
]
ASF GitHub Bot commented on FLINK-1930:
---
Github user vasia commented on the pull req
Github user vasia commented on the pull request:
https://github.com/apache/flink/pull/624#issuecomment-96003734
Hi @uce!
I confirm that your changes solve my issue, both on the test program and
dataset, as well as on my original application. Thanks a lot ^^
---
If your project is
[
https://issues.apache.org/jira/browse/FLINK-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14511329#comment-14511329
]
ASF GitHub Bot commented on FLINK-938:
--
Github user mxm commented on the pull request:
Github user mxm commented on the pull request:
https://github.com/apache/flink/pull/248#issuecomment-95990793
This will work for most use cases where the JobManager is started within
the same cluster as the TaskManagers. It will certainly fail if the JobManager
resides in a different
Github user uce commented on the pull request:
https://github.com/apache/flink/pull/248#issuecomment-95981935
I've just checked EC2. The default AMIs all return the cloud internal
hostname, which is accessible (given the correct security setup). I count this
as an indicator that just
[
https://issues.apache.org/jira/browse/FLINK-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14511291#comment-14511291
]
ASF GitHub Bot commented on FLINK-938:
--
Github user uce commented on the pull request:
[
https://issues.apache.org/jira/browse/FLINK-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14511243#comment-14511243
]
ASF GitHub Bot commented on FLINK-1938:
---
Github user vikhyat commented on the pull r
Github user vikhyat commented on the pull request:
https://github.com/apache/flink/pull/623#issuecomment-95969891
Sorry about that, I had given up on my last attempt because I couldn't
figure out how to do the Maven-Grunt integration. After working on a few other
Maven-based projects
[
https://issues.apache.org/jira/browse/FLINK-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14511203#comment-14511203
]
ASF GitHub Bot commented on FLINK-1930:
---
GitHub user uce opened a pull request:
GitHub user uce opened a pull request:
https://github.com/apache/flink/pull/624
[FLINK-1930] Separate output buffer pool and result partition life cycle
The problem: when a pipelined result is only consumed partially, the buffer
pool associated with the result partition will be dest
[
https://issues.apache.org/jira/browse/FLINK-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14511160#comment-14511160
]
ASF GitHub Bot commented on FLINK-1938:
---
Github user StephanEwen commented on the pu
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/623#issuecomment-95952682
Wow, this comes with a bit of a surprise, given that it is a followup to a
year-old discussion in the pre-Apache project "Stratosphere".
Because such a long time ha
[
https://issues.apache.org/jira/browse/FLINK-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14511138#comment-14511138
]
ASF GitHub Bot commented on FLINK-1938:
---
Github user vikhyat commented on the pull r
Github user vikhyat commented on the pull request:
https://github.com/apache/flink/pull/623#issuecomment-95949279
The build is failing because of the license checker (RAT) hanging, not sure
why it's happening.
When building locally I get the same issue both on master as well a
[
https://issues.apache.org/jira/browse/FLINK-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14511126#comment-14511126
]
ASF GitHub Bot commented on FLINK-1867:
---
Github user aljoscha commented on the pull
Github user aljoscha closed the pull request at:
https://github.com/apache/flink/pull/612
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is ena
Github user aljoscha commented on the pull request:
https://github.com/apache/flink/pull/612#issuecomment-95946066
Manually merged.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this featur
[
https://issues.apache.org/jira/browse/FLINK-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14511127#comment-14511127
]
ASF GitHub Bot commented on FLINK-1867:
---
Github user aljoscha closed the pull reques
[
https://issues.apache.org/jira/browse/FLINK-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aljoscha Krettek resolved FLINK-1867.
-
Resolution: Fixed
Resolved in
https://github.com/apache/flink/commit/b2aafe585303e9eceb57
[
https://issues.apache.org/jira/browse/FLINK-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aljoscha Krettek resolved FLINK-1880.
-
Resolution: Fixed
Resolved in
https://github.com/apache/flink/commit/b2aafe585303e9eceb57
[
https://issues.apache.org/jira/browse/FLINK-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1458#comment-1458
]
ASF GitHub Bot commented on FLINK-1938:
---
GitHub user vikhyat opened a pull request:
Vikhyat Korrapati created FLINK-1938:
Summary: Add Grunt for building the front-end
Key: FLINK-1938
URL: https://issues.apache.org/jira/browse/FLINK-1938
Project: Flink
Issue Type: Improv
GitHub user vikhyat opened a pull request:
https://github.com/apache/flink/pull/623
[FLINK-1938] Add Grunt for building the front-end
This is the first step towards implementing the web interface refactoring I
proposed last year:
https://groups.google.com/forum/#!topic/stratosphere
[
https://issues.apache.org/jira/browse/FLINK-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1456#comment-1456
]
mustafa elbehery commented on FLINK-1615:
-
Myself ofcourse.. I will create a new P
Github user asfgit closed the pull request at:
https://github.com/apache/flink/pull/620
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
[
https://issues.apache.org/jira/browse/FLINK-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14510983#comment-14510983
]
ASF GitHub Bot commented on FLINK-1615:
---
Github user aljoscha commented on the pull
Github user aljoscha commented on the pull request:
https://github.com/apache/flink/pull/621#issuecomment-95926348
The build still fails because of missing license headers in the model
package.
By the way, did you write the files in the model package yourself or were
they gen
[
https://issues.apache.org/jira/browse/FLINK-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14510960#comment-14510960
]
ASF GitHub Bot commented on FLINK-1807:
---
Github user thvasilo commented on a diff in
Github user thvasilo commented on a diff in the pull request:
https://github.com/apache/flink/pull/613#discussion_r29044450
--- Diff:
flink-staging/flink-ml/src/test/scala/org/apache/flink/ml/optimization/GradientDescentITSuite.scala
---
@@ -0,0 +1,212 @@
+/*
+ * Licensed
Github user thvasilo commented on a diff in the pull request:
https://github.com/apache/flink/pull/613#discussion_r29044413
--- Diff:
flink-staging/flink-ml/src/test/scala/org/apache/flink/ml/optimization/GradientDescentITSuite.scala
---
@@ -0,0 +1,212 @@
+/*
+ * Licensed
[
https://issues.apache.org/jira/browse/FLINK-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14510958#comment-14510958
]
ASF GitHub Bot commented on FLINK-1807:
---
Github user thvasilo commented on a diff in
[
https://issues.apache.org/jira/browse/FLINK-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14510955#comment-14510955
]
ASF GitHub Bot commented on FLINK-1807:
---
Github user thvasilo commented on a diff in
Github user thvasilo commented on a diff in the pull request:
https://github.com/apache/flink/pull/613#discussion_r29044309
--- Diff:
flink-staging/flink-ml/src/main/scala/org/apache/flink/ml/optimization/RegularizationType.scala
---
@@ -0,0 +1,112 @@
+/*
+ * Licensed to t
Github user thvasilo commented on a diff in the pull request:
https://github.com/apache/flink/pull/613#discussion_r29044212
--- Diff:
flink-staging/flink-ml/src/main/scala/org/apache/flink/ml/common/WeightVector.scala
---
@@ -0,0 +1,45 @@
+/*
+ * Licensed to the Apache Sof
[
https://issues.apache.org/jira/browse/FLINK-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14510953#comment-14510953
]
ASF GitHub Bot commented on FLINK-1807:
---
Github user thvasilo commented on a diff in
Github user thvasilo commented on the pull request:
https://github.com/apache/flink/pull/613#issuecomment-95917745
Some Travis builds are failing because of the 4MB log limit; one of tests
is running 2000 iterations creating a lot of log output.
Ideas on how to fix?
There is [
[
https://issues.apache.org/jira/browse/FLINK-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14510952#comment-14510952
]
ASF GitHub Bot commented on FLINK-1807:
---
Github user thvasilo commented on the pull
[
https://issues.apache.org/jira/browse/FLINK-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14510898#comment-14510898
]
ASF GitHub Bot commented on FLINK-1925:
---
GitHub user tillrohrmann opened a pull requ
GitHub user tillrohrmann opened a pull request:
https://github.com/apache/flink/pull/622
[FLINK-1925] Fixes blocked method submitTask on the TM
The ```submitTask``` method which processes the ```SubmitTask``` message
blocks while downloading the task jars from the ```JobManager```.
[
https://issues.apache.org/jira/browse/FLINK-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14510754#comment-14510754
]
ASF GitHub Bot commented on FLINK-1486:
---
Github user mxm commented on the pull reque
Github user mxm commented on the pull request:
https://github.com/apache/flink/pull/372#issuecomment-95880258
Yes, it should be simple for the user. It makes sense to have one print
method which just prints the output on the client. In addition, we could have
another *advanced* print
[
https://issues.apache.org/jira/browse/FLINK-924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14510740#comment-14510740
]
ASF GitHub Bot commented on FLINK-924:
--
Github user qmlmoon commented on the pull requ
Github user qmlmoon commented on the pull request:
https://github.com/apache/flink/pull/35#issuecomment-95876902
I rebased the PR on the current master and removed the annoying merge
commits.
---
If your project is set up for it, you can reply to this email and have your
reply appear
[
https://issues.apache.org/jira/browse/FLINK-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14510712#comment-14510712
]
ASF GitHub Bot commented on FLINK-1486:
---
Github user StephanEwen commented on the pu
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/372#issuecomment-95869290
Okay, let's just try and not make this too confusing for users. Do we need
all three versions?
1. `print()`
2. `printWithParallelId()`
3. `printWithPre
Github user gyfora commented on the pull request:
https://github.com/apache/flink/pull/620#issuecomment-95868976
It's a shame that we need to remove additional references to make the
serialization work properly, but otherwise it looks good.
Let's merge it soon
---
If your pr
[
https://issues.apache.org/jira/browse/FLINK-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14510709#comment-14510709
]
ASF GitHub Bot commented on FLINK-1514:
---
Github user vasia commented on the pull req
[
https://issues.apache.org/jira/browse/FLINK-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14510710#comment-14510710
]
ASF GitHub Bot commented on FLINK-1789:
---
Github user StephanEwen commented on the pu
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/593#issuecomment-95868495
I think that keeping the classpaths in sync is really crucial. What is the
problem in exposing this to the client as well?
Can we make the following assumption
Github user vasia commented on the pull request:
https://github.com/apache/flink/pull/408#issuecomment-95868450
Hey Andra,
there are several issues we'll need to fix/add after this is merged. A
Pagerank example is one of them :) I have gathered and will open all related
JIRAs
Github user Elbehery commented on the pull request:
https://github.com/apache/flink/pull/442#issuecomment-95866843
@aljoscha u were right.. I could not find the code on my repo, somehow it
was lost !!! ..
I have created a new PR now, #621 .. it has the same commit of #442
[
https://issues.apache.org/jira/browse/FLINK-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14510698#comment-14510698
]
ASF GitHub Bot commented on FLINK-1615:
---
Github user Elbehery commented on the pull
GitHub user Elbehery opened a pull request:
https://github.com/apache/flink/pull/621
[FLINK-1615] [java api] SimpleTweetInputFormat
A replacement for PR #442
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Elbehery/flink tweet_in
[
https://issues.apache.org/jira/browse/FLINK-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14510694#comment-14510694
]
ASF GitHub Bot commented on FLINK-1514:
---
Github user andralungu commented on the pul
[
https://issues.apache.org/jira/browse/FLINK-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14510695#comment-14510695
]
ASF GitHub Bot commented on FLINK-1615:
---
GitHub user Elbehery opened a pull request:
Github user andralungu commented on the pull request:
https://github.com/apache/flink/pull/408#issuecomment-95866092
I noticed that there is no GSAPageRank example in the latest version of the
code.
I'd like to take care of that once this PR gets merged, to get to
understand this
GitHub user mbalassi opened a pull request:
https://github.com/apache/flink/pull/620
[streaming] Serialization robustness improvements
Resolves the following issues:
* Streaming sometimes used Java's SerializationUtils instead of Flink's
InstantiationUtils.
* Stream
Github user mxm commented on the pull request:
https://github.com/apache/flink/pull/372#issuecomment-95855310
Just saying that a prefix helps to identify output, even if everything is
printed on the client. Additionally, including the task id in the output can be
useful for debugging.
[
https://issues.apache.org/jira/browse/FLINK-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14510661#comment-14510661
]
ASF GitHub Bot commented on FLINK-1486:
---
Github user mxm commented on the pull reque
[
https://issues.apache.org/jira/browse/FLINK-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ufuk Celebi reassigned FLINK-1930:
--
Assignee: Ufuk Celebi
> NullPointerException in vertex-centric iteration
>
[
https://issues.apache.org/jira/browse/FLINK-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14510650#comment-14510650
]
Stephan Ewen commented on FLINK-1930:
-
Seems like a bug that the pools get released to
[
https://issues.apache.org/jira/browse/FLINK-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14510649#comment-14510649
]
Stephan Ewen commented on FLINK-1930:
-
And this is the only exception that you see, it
[
https://issues.apache.org/jira/browse/FLINK-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14510627#comment-14510627
]
ASF GitHub Bot commented on FLINK-1615:
---
Github user aljoscha commented on the pull
Github user aljoscha commented on the pull request:
https://github.com/apache/flink/pull/442#issuecomment-95846017
The problem is, that I can't see it in the github interface. On what branch
are your changes? Could you please rebase them on top of the current master?
---
If your proj
[
https://issues.apache.org/jira/browse/FLINK-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14510623#comment-14510623
]
ASF GitHub Bot commented on FLINK-1789:
---
Github user aljoscha commented on the pull
Github user aljoscha commented on the pull request:
https://github.com/apache/flink/pull/593#issuecomment-95845500
OK, @StephanEwen, any thoughts on this? Should we allow that the local user
code class loader in the client potentially doesn't have the same jars
available as the worker
70 matches
Mail list logo
