+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
e SQL functionality. I can
implement an SQL operator and extend the Table API if functionality is
missing.
On 27.05.2015 16:41, Fabian Hueske wrote:
+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
+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
te:
> >
> > > 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
grams, and SQL scripts.
>
> On Wed, May 27, 2015 at 3:49 PM, Robert Metzger
> wrote:
>
> > 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).
... 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
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
It would also be relatively simple (I think) to retarget drill to Flink if
Flink doesn't provide enough typing meta-data to do traditional SQL.
On Tue, May 26, 2015 at 12:52 PM, Fabian Hueske wrote:
> Hi,
>
> Flink's Table API is pretty close to what SQL provides. IMO, the best
> approach woul
Hi,
Flink's Table API is pretty close to what SQL provides. IMO, the best
approach would be to leverage that and build a SQL parser (maybe together
with a logical optimizer) on top of the Table API. Parser (and optimizer)
could be built using Apache Calcite which is providing exactly this.
Since
Hey everyone,
I would be interested in having a complete SQL API in Flink. How is the
status there? Is someone already working on it? If not, I would like to
work on it. I found http://ijcsi.org/papers/IJCSI-12-1-1-169-174.pdf but
I couldn't find anything on the mailing list or Jira. Otherwise
12 matches
Mail list logo