Nice article indeed. In Coral [1], we have simplified this process to the
end user where those steps can be done through implementing a small number
of abstract methods, listed here [2].
[1] https://github.com/linkedin/coral
[2]
https://github.com/linkedin/coral/blob/master/coral-common/src/main/j
Congrats Ruben!
Haisheng, thanks a lot for serving as a chair!
Enrico Olivelli 于2022年1月23日周日 05:17写道:
> Congrats!
>
> Enrico
>
> Il Sab 22 Gen 2022, 03:03 xiong duan ha scritto:
>
> > Congratulations to Ruben and thanks to Haisheng!
> >
> > Danny Chan 于2022年1月21日周五 12:19写道:
> >
> > > Congratu
Hi Stamatis,
Thanks for driving this discussion.
Big +1 on the idea. They are undoubtedly very helpful for newcomers to
Calcite. I have heard a lot of requests in the dev mailing lists to get
more started documentation.
At the same time, we need take careful to decide what contents to put in
thi
Hi all,
First of all thanks a lot to everyone who participated and supported the
idea of the meetup.
Special thanks to Alexey, Ioan, and Gavin, for presenting their work. All
presentations were very interesting and valuable contributions to the
community.
You can find their presentations here [1].
Hi all,
I have been dabbling with Calcite for a while out of interest and curiosity
and, in order to become more familiar with the code and the overall
architecture, I've tried implementing an adapter [1] to run SQL queries
over SPARQL endpoints. As Gavin has done, I have also planned to share som
Hi all,
Taking the recent email of Gavin [1] (sharing his article on GraphQL to SQL
conversion) as a motive, I wanted to see what people think of creating a
new section in the website for putting this and other useful stuff such as
Michael's notebooks, Querifylabs blogs [2], etc.
We could have on
Thanks for sharing this Gavin, very nice article!
On Sun, Jan 23, 2022 at 7:00 PM Gavin Ray wrote:
> I thought that someone else might find it useful, since there was no
> existing guide covering building new frontends.
> It looks best on Jetbrains Datalore, but you can also view it using the
>
Hi Julian,
I don't think there is an easy way to understand the Queryable interface
unless you check how it is used. I don't see it as something that you need
to implement no matter what but more as a convenience API that will
facilitate the integration with the Enumerable operators (if you rely o
To the best of my knowledge there is no document getting into details about
the Queryable interface etc. The best way to approach this as Gavin
mentioned is to see how it is used in the project and outside of it.
One thing that I wanted to mention is that you can build a system using
Calcite witho
I also had a separate module in mind when I made the comment during the
meetup.
Although, I don't want to force people to rewrite their code in another
language in order to be accepted, the truth is that using Java 8 will be
the easiest way to get this in.
I think we are using Java 8 in the bigges
I thought that someone else might find it useful, since there was no
existing guide covering building new frontends.
It looks best on Jetbrains Datalore, but you can also view it using the
".ipynb" in the Github repo:
https://datalore.jetbrains.com/view/notebook/JYTVfn90xYSmv6U5f2NIQR
https://gith
Hi Justin,
the same table could be used to describe different concepts/classes.
For instance, you could have a single table "Employee" where the column
"job_type" is used to describe the different kinds of jobs (and therefore
employees) you have.
At that point, you could have "White Collar Employ
Thanks😁
xiong duan 于2022年1月5日周三 09:11写道:
> Hi LakeShen,
> You can find some Calcite Learning Resources here
> https://lists.apache.org/thread/g5nqv2oc80261y5sm1bwlhbpf986lmdw.
>
> R. C. Howell 于2022年1月5日周三 04:50写道:
>
> > Just my 2¢. I’ve found the examples on github useful as well as the v
Thanks Hongze for your recommendations.
On Saturday, January 22, 2022, 09:59:00 PM EST, Hongze Zhang
wrote:
I think '=' is being shown because by "format json" the statement produced a
JSON value expression rather than a regular
JSON string. Ideally "format json" should not be at the
Hi Alessandro,
That is very fascinating. Most of those situations won't apply to this
optimization though, since it requires the tables of the union to be
identical rather than different tables representing unions of different
ontologies, that is, this will only apply optimizations when an ontolo
Hello everyone,
SQL queries automatically generated by semantic queries (see [1] for
instance) are pretty generous on UNIONs, so I'd say that in this area, you
will have many practical cases matching the patterns highlighted here.
The main idea is that when you have a concept hierarchy in your ont
16 matches
Mail list logo