A few months ago, I raised the possibility to automating our website
builds, so that we will not need to manually build the site on our
machines and push it to the calcite-site repository.
I've been quite busy and haven't been able to look into it, however I am
planning to look into in the
Hi,
Since we have commited CALCITE-2969, and in the next release of 1.21, we will
deprecate EquiJoin and make enumerable hash join support non-equi join
condition, the optimization door is open to us.
Currently Calcite often generates complicated and inefficient plan for boolean
context
It seems that we can disable parallel execution selectively for certain
test classes by annotating them with @net.jcip.annotations.NotThreadSafe.
Maybe this can do the trick for parameterized tests while we wait for the
permanent fix.
On Mon, Jun 3, 2019 at 10:57 PM Haisheng Yuan
wrote:
> I
I don't konw if there is an API for that but visiting the parsed/validated
SqlNode tree can do what you asked for.
Thanks,
Gelbana
On Tue, Jun 4, 2019 at 12:12 AM Adam Rivelli wrote:
> Hi all,
>
> I'm trying to extract all of the (fully qualified) columns used by a query
> - similar to the
Hi all,
I'm trying to extract all of the (fully qualified) columns used by a query
- similar to the information provided by
RelMetadataQuery.getTableReferences()
I am inclining to change threadCount to 4, then see how it works in CI, at
least it solves the problem on my laptop.
If the problem still shows up in CI, or it solves the problem but makes the CI
test much slower, I would rather tear up the parameterized test case.
- Haisheng
> Am I correct that this problem only shows up on machines with 1 CPU?
No, my laptop has 2 CPUs, it still shows up.
Thanks ~
Haisheng Yuan
--
发件人：Julian Hyde
日 期：2019年06月04日 01:56:56
收件人：dev
主 题：Re: [DISCUSS] Parallel parameterized
Am I correct that this problem only shows up on machines with 1 CPU?
Such machines exist in virtualization environments (e.g. Travis) but the
machines we use for everyday development have multiple CPUs. So, could we add a
parameter so that we can turn off parallel tests only in CI?
My goal is
I agree that if things are SQL-like, then they should be true standard SQL (or
a thoughtful superset of it).
That said, there is also a place for other languages. Ideally (1) those
languages map down to an algebra that can be transformed and optimized, (2)
those languages read from or write to
The Apache Jenkins build system has built Calcite-Master (build #1205)
Status: Failure
Check console output at https://builds.apache.org/job/Calcite-Master/1205/ to
view the results.
Is that different from what I mentioned in my Jira comment ? Here it is
again:
Connection connection = DriverManager.getConnection("jdbc:calcite:", info);
connection.unwrap(CalciteConnection.class).getRootSchema().unwrap(CalciteSchema.class).add("
*TEXT*", new RelProtoDataType() {
Hi all,
thanks for opening this discussion, Stamatis.
I think there might be a third way. We could try to check if tuning
surefire configuration solves the problem.
Right now on calcite's pom.xml file we have:
both
1
true
Thanks to Haisheng's tests, we know that changing threadCount from 1
to
Hi all,
The past few days we had observed various problems on Jenkins (and
elsewhere) which made our test suite hang.
Haisheng and Ruben found out that the problem was the parallel execution of
parameterized tests [1]. I see two ways to unblock this situation and avoid
such problems in the
User-defined types are probably the way to go.
> On Jun 2, 2019, at 8:28 PM, Muhammad Gelbana wrote:
>
> That was my first attempt and it worked, but Julian pointed out that I can
> support a type without modifying the parser (which I prefer) but I couldn't
> get it to return the column type
I have also noticed this project, this grammar is too faraway from SQL
standard. But the idea is good, like the CEP grammar.
Best,
Danny Chan
在 2019年6月3日 +0800 AM10:52，Albert ，写道：
> found some efforts in bringing sql to machine learning world.
>
Currently we provide answer to metadata query through RelMetadataProvider [1],
there are some sub-classes of it:
RelMetadataProvider
|
|- VolcanoRelMetadataProvider
|- ChainedRelMetadataProvider/DefaultRelMetadataProvider
|- HepRelMetadataProvider
|- CachingRelMetadataProvider
|-
16 matches
Mail list logo
