That's awesome. I'm sure it will make it easier for Chinese-speaking users
to get help.
For development decisions, please continue to abide for the Apache way -
decisions must be made on the mailing list. Not in meeting rooms, or phone
calls, or online chat. It's not always convenient, but it
hi, guys:
I create a WeChat group for China Users of Apache Calcite, to make it
easy to communicate about Calcite. Now we have 2 committers in the group ,
if you have problems about calcite , join us, let's communicate and
discuss here.
In Chinese :
It seemed reasonable when I introduced it, and seems very reasonable, that a
relational expression (even in the relational model) can have multiple physical
properties. Consider these questions that the planner might ask:
Example 1:
“Are you sorted on hiredate?”
“Yes”
“Are you sorted on
Stamatis, here is some recent work we did on that topic:
http://www.sysnet.ucsd.edu/sysnet/miscpapers/datalog-icbd16.pdf
References section has more pointers to other related work.
Thanks,
Walaa.
On Sun, Apr 7, 2019 at 11:15 PM Stamatis Zampetakis wrote:
>
> Hello,
>
> @Julian: It looks like
Hi Haisheng,
Thanks for raising awareness around this topic. I also think we should try
to find a solution.
Initially, the Volcano planner was designed to be able to cover multiple
models (and not only the relational). For non-relational models composite
traits may be indispensable. I don't know
Many thanks to reviewers for merging PRs and Kevin for upgrading Jetty.
There's still CALCITE-2983 [1], but I think I can make rc0 available for
voting soon.
In the meantime, I'd like to get CALCITE-2882 in if I can hear back from
the author: https://github.com/apache/calcite-avatica/pull/86
Hi Mark,
It is not easy to understand what is missing from the pieces of code you
shared.
In the example that I've shared with you, I don't remember seeing anywhere
CREATE VIEW statements. I suppose you are trying to execute a
java.sql.Statement but I am afraid this will not work. You don't need
Forward Xu created CALCITE-2985:
---
Summary: Add the JSON_STORAGE_SIZE function
Key: CALCITE-2985
URL: https://issues.apache.org/jira/browse/CALCITE-2985
Project: Calcite
Issue Type: New Feature
Forward Xu created CALCITE-2984:
---
Summary: Add the JSON_STORAGE_SIZE function
Key: CALCITE-2984
URL: https://issues.apache.org/jira/browse/CALCITE-2984
Project: Calcite
Issue Type: New Feature
Kevin Risden created CALCITE-2983:
-
Summary: Add Avatica compatibility page for TLS and IBM Java
Key: CALCITE-2983
URL: https://issues.apache.org/jira/browse/CALCITE-2983
Project: Calcite
Dear Stamatis,
Thank you for your reply.
I have since been trying to create materialized views via calcite without
much success, I don't know if you can perhaps help with that?
I have set up my rootschema as:
final DataSource ds = JdbcSchema.dataSource( dburl, "org.postgresql.Driver"
);
pengzhiwei created CALCITE-2982:
---
Summary: SqlItemOpeator should throw understandable exception
message for incorrect field type
Key: CALCITE-2982
URL: https://issues.apache.org/jira/browse/CALCITE-2982
Hi Mark,
I suppose that the views cannot be discovered automatically so you will
have to register them explicitly. If you are connecting to Postgres using
the JsonModel then you might find the tests in MaterializationTest [1]
useful. Most likely you will have to change the SchemaFactory to use
Hello,
@Julian: It looks like an interesting project, looking forward to see what
comes out of it.
@Walaa: The current implementation takes care of UNION ALL but it seems
relatively easy to extend it for UNION. At least with a naive
implementation. Research-wise, I am not very familiar with the
14 matches
Mail list logo
