Now there is a blog post on the update:
https://blogs.apache.org/infra/entry/apache_gains_additional_travis_ci
It seems that Apache now has 30 concurrent builds and is a paying Travis
user/customer.
On Thu, Apr 2, 2015 at 3:58 PM, Robert Metzger wrote:
> I just found out that the execution time
I would also be in favour of making the distinction between the API and
common API layer more clear by using different names. This will ease the
understanding of the source code.
In the wake of a possible renaming we could also get rid of the legacy code
org.apache.flink.optimizer.dag.MatchNode an
Thanks for the feedback guys!
Apparently The Scala Shell compiles the Shell input to some kind of virtual
directory.
It should be possible to create a jar from it's content and then hand it
over to Flink for execution in some way.
I will further investigate..
cheers,
Nikolaas
2015-04-15 11:20 GMT
On 15 Apr 2015, at 15:01, Stephan Ewen wrote:
> I think we can rename the base operators.
>
> Renaming the subclass of DataSet would be extremely api breaking. I think
> that is not worth it.
Oh, that's right. We return MapOperator for DataSet operations. Stephan's point
makes sense.
I think we can rename the base operators.
Renaming the subclass of DataSet would be extremely api breaking. I think
that is not worth it.
Am 15.04.2015 14:11 schrieb "Aljoscha Krettek" :
> This is just a personal annoyance and I think we are to advanced to
> change this now, but here goes: Could
On 15 Apr 2015, at 14:11, Aljoscha Krettek wrote:
> This is just a personal annoyance and I think we are to advanced to
> change this now, but here goes: Could we rename the classes in the
> API, so that for example MapOperator becomes MapDataSet or MapSet, and
> the actual operators in the comm
This is just a personal annoyance and I think we are to advanced to
change this now, but here goes: Could we rename the classes in the
API, so that for example MapOperator becomes MapDataSet or MapSet, and
the actual operators in the common package become MapOperator instead
of MapOperatorBase.
My
Sibao Hong created FLINK-1891:
-
Summary: Add isEmpty check when the input dir
Key: FLINK-1891
URL: https://issues.apache.org/jira/browse/FLINK-1891
Project: Flink
Issue Type: Bug
Compon
To give a bit of context for the exception:
To execute a program, the classes of the user functions need to be
available the executing TaskManagers.
- If you execute locally from the IDE, all classes are in the classpath
anyways.
- If you use the remote environment, you need to attach the jar f
