Hi
Is there a way, where I can add a custom (newly created) Tuple to a new
DataSet or already existing DataSet?
DataSet set = env.fromElements (myCustomTuple);
works fine, but only with same datatype in case of Tuple2 or higher.
Tuple2 creates a problem (as stated in JavaDoc it needs all
elements
+1 to what ufuk said. :D
On May 27, 2015 6:13 PM, "Kostas Tzoumas" wrote:
> very excited to see this starting!
>
> On Wed, May 27, 2015 at 6:06 PM, Ufuk Celebi wrote:
>
> >
> > On 27 May 2015, at 17:05, Timo Walther wrote:
> >
> > > It's rather passion for the future of the project than passion
very excited to see this starting!
On Wed, May 27, 2015 at 6:06 PM, Ufuk Celebi wrote:
>
> On 27 May 2015, at 17:05, Timo Walther wrote:
>
> > It's rather passion for the future of the project than passion for SQL
> ;-)
> >
> > I always try to think like someone from the economy. And IMO the gu
On 27 May 2015, at 17:05, Timo Walther wrote:
> It's rather passion for the future of the project than passion for SQL ;-)
>
> I always try to think like someone from the economy. And IMO the guys from
> economy are still thinking in SQL. If you want to persuade someone coming
> from the SQL
Theodore Vasiloudis created FLINK-2102:
--
Summary: Add predict operation for LabeledVector
Key: FLINK-2102
URL: https://issues.apache.org/jira/browse/FLINK-2102
Project: Flink
Issue Type:
Hi Peter,
Thanks a lot for your feedback. It's exiting to see, that somebody uses
the layer already. :)
The current prototype is going to be merged soon. However, I am more
than happy to extend the functionality of the layer. Can you please
share your example with me, so I can see what the proble
It's rather passion for the future of the project than passion for SQL ;-)
I always try to think like someone from the economy. And IMO the guys
from economy are still thinking in SQL. If you want to persuade someone
coming from the SQL world, you should offer a SQL interface to run
legacy cod
+1 for committer passion!
Please don't get me wrong, I think SQL on Flink would be a great feature.
I just wanted to make the point that the Table API needs to mirror all SQL
features, if SQL is implemented on top of the Table API.
2015-05-27 16:34 GMT+02:00 Kostas Tzoumas :
> I think Fabian's
I think Fabian's arguments make a lot of sense.
However, if Timo *really wants* to start SQL on top of Table, that is what
he will do a great job at :-) As usual, we can keep it in beta status in
flink-staging until it is mature... and it will help create issues for the
Table API and give directio
IMO, it is better to have one feature that is reasonably well developed
instead of two half-baked features. That's why I proposed to advance the
Table API a bit further before starting the next big thing. I played around
with the Table API recently and I think it definitely needs a bit more
contrib
Rico Bergmann created FLINK-2101:
Summary: Scheme Inference doesn't work for Tuple5
Key: FLINK-2101
URL: https://issues.apache.org/jira/browse/FLINK-2101
Project: Flink
Issue Type: Bug
I see no reason why a SQL interface cannot be "bootstrapped" concurrently.
It would initially not support many operations,
but would act as a good source to test and drive functionality from the
Table API.
@Ted:
I would like to learn a bit more about the stack and internal abstractions
of Drill.
I didn't know that paper... Thanks for sharing.
I've worked on a SQL layer for Stratosphere some time ago, using Apache
Calcite (called Optiq back then). I think the project provides a lot of
very good tooling for creating a SQL layer. So if we decide to go for SQL
on Flink, I would suggest to us
Hey everyone,
I experimented with the Storm compatibility layer Matthias wrote, and ran
some Storm examples on Flink. I found that Storm's SimpleJoin example does
not work. I suppose it is because of the multiple input streams. I'm
willing to add another example instead.
Right now, I'm getting it
Timo Walther created FLINK-2100:
---
Summary: Add ITCases for all Table API examples
Key: FLINK-2100
URL: https://issues.apache.org/jira/browse/FLINK-2100
Project: Flink
Issue Type: New Feature
Timo Walther created FLINK-2099:
---
Summary: Add a SQL API
Key: FLINK-2099
URL: https://issues.apache.org/jira/browse/FLINK-2099
Project: Flink
Issue Type: New Feature
Components: Table
Stephan Ewen created FLINK-2098:
---
Summary: Checkpoint barrier initiation at source is not aligned
with snapshotting
Key: FLINK-2098
URL: https://issues.apache.org/jira/browse/FLINK-2098
Project: Flink
Hi Vijendra,
welcome! You can find information about contributing and code guidelines
on the website:
http://flink.apache.org/how-to-contribute.html
http://flink.apache.org/coding-guidelines.html
Feel free to ask questions if you have any problems.
Regards,
Timo
On 27.05.2015 12:57, Vijendr
Hi!
I am new to the open source would and wanted to start my journey with
Flink. I found an issue that I think would be good for me:
https://issues.apache.org/jira/browse/FLINK-2077
I had a few queries regarding it and it would be great if you could help
with them.
1. The issue talks about cleani
Stephan, not sure what you mean by this exactly... But I guess, this a
an "add-on" that can be done later. Seems to be related to
https://issues.apache.org/jira/browse/FLINK-1929
I will open a JIRA for the new "terminate" message and assign it to myself.
-Matthias
On 05/27/2015 12:36 PM, Stepha
+1 for the second option.
How about we allow to pass a flag that indicates whether a checkpoint
should be taken together with the canceling?
On Wed, May 27, 2015 at 12:27 PM, Aljoscha Krettek
wrote:
> I would also prefer the second option. The first is rather a hack but not
> an option. :D
> O
I would also prefer the second option. The first is rather a hack but not
an option. :D
On May 27, 2015 9:14 AM, "Márton Balassi" wrote:
> +1 for the second option:
>
> It would also provide possibility to properly commit a state checkpoint
> after the terminate message was triggered. In some cas
Stephan Ewen created FLINK-2097:
---
Summary: Add support for JobSessions
Key: FLINK-2097
URL: https://issues.apache.org/jira/browse/FLINK-2097
Project: Flink
Issue Type: New Feature
Com
It would be an interesting addition.
Such a method cannot be done fully type safe in Java, but that might be
okay, since it is user-code internal.
On Wed, May 27, 2015 at 11:52 AM, Flavio Pompermaier
wrote:
> Sorry, to be effective the project should also take in input the target
> tuple itself
Sorry, to be effective the project should also take in input the target
tuple itself :)
Tuple3 reuse = tuple.project(reuse, 0,2,5)?
On Wed, May 27, 2015 at 11:51 AM, Flavio Pompermaier
wrote:
> Hi flinkers,
>
> it happens very often to me that I have to output a reuse tuple that
> basically is
Hi flinkers,
it happens very often to me that I have to output a reuse tuple that
basically is a subset of the data contained of the input tuple..do you
think it could be useful to add a project method to Tuple class?
So that to be able to write something like:
Tuple3 reuse = tuple.project(0,2,5
Hi Henry!
I think the idea was to have a dedicated streaming mode as long as the
default cluster mode does not support batch and streaming equally well.
Once we have reached this level in the dedicated streaming mode, this will
be the default cluster mode. I share your doubts about whether it is a
Hi Matthias,
I understand your point about "advertising" the interfaces but there is so
much stuff to be advertised :). Honestly, I think ProgramDescription
doesn't add much value although it is kind of neat. Parameters can be
described in the code or by displaying a help message. However, I'm in
+1 for the second option:
It would also provide possibility to properly commit a state checkpoint
after the terminate message was triggered. In some cases this can be a
desirable behaviour.
On Wed, May 27, 2015 at 8:46 AM, Gyula Fóra wrote:
> Hey,
>
> I would also strongly prefer the second opt
29 matches
Mail list logo
