cui created CALCITE-3351:
Summary: calcite mysql utf8中文查询报错
Key: CALCITE-3351
URL: https://issues.apache.org/jira/browse/CALCITE-3351
Project: Calcite
Issue Type: Bug
Components: core
I think it will work. I once did similar things and was playing around with
VolcanoPlanner and RelOptMaterializations.
Shubham Kumar 于2019年9月16日周一 下午8:32写道：
> Hey everyone,
>
> Thank you for the help.
>
> @Stamatis, @Danny : Thanks for pointing out that the reltosql api should
> be used
Import order and length of a single line of code is too long were what I
faced.
In Apache Beam, we are using gradle and have adopted
https://github.com/diffplug/spotless. So there is a command to fix unused
import, import ordering, line length, etc there (gradle spotlessApply).
-Rui
On Mon,
I’m sorry that we do not have the technology to auto-correct. People also
complain that there are coding standards that are not captured in check style
rules, so we are caught between a rock and a hard place.
I agree, something like https://github.com/editorconfig/editorconfig/issues/231
Rui>Import order and length of a single line of code is too long were what I
faced.
I guess both of them could be configured in IDE.
Even though it might look boring/complicated, configuring import order in
IDE pays off quickly.
Rui>In Apache Beam, we are using gradle and have adopted
Hi community,
Is there a maven command or auto-formatter to fix checkstyle error when
developing in Calcite repo? I am less familiar with maven and did some
searches in both [1] and Google but found no luck.
[1]: https://calcite.apache.org/develop/
-Rui
Rui>when developing in Calcite repo?
Hi, could you please clarify which issues do you run into the most?
Rui>auto-formatter to fix checkstyle error
That would really be awesome.
Unfortunately, my experience with Checkstyle project 5 years ago was that
core developers did not value "automatic
Thanks. I will try to setup IDE then.
I don't have a clear idea how to use spotless for maven. I could spend some
time to explore it and if it's easy to setup, I will report it back to you.
-Rui
On Mon, Sep 16, 2019 at 12:51 PM Vladimir Sitnikov <
sitnikov.vladi...@gmail.com> wrote:
>
The minimum spotless maven can do is:
remove unused import
correct import order
check license header
To use it is also easy after enabling it in maven pom:
mvn spotless:check // check the style
mvn spotless:apply // apply spotless fix
The difference though is the default setting of code style
If you use IntelliJ IDEA for developing, you can generate a check style conf
xml file for Calcite, then use this conf file in your code style config for
Java. You should first download a check style plugin.
Best,
Danny Chan
在 2019年9月17日 +0800 AM3:09，Rui Wang ，写道：
> Hi community,
>
> Is there a
Out of curiosity does anybody know if popular DBMS (Postgres, Oracle, SQL
Server, etc.) support "hoisting"?
Performing it all the time does not seem a very good idea (constant
reduction, histograms, and other optimization techniques would be
impossible)
while leaving its configuration to the
I found evidence that MSSQL[1] and Sybase ASE[2] do it.
I agree, it's not a free lunch. For instance, if a column has a
non-uniform distribution, some values might be much more selective
than others, and it would be much better to know which value you are
dealing with at planning time, rather
Zhenqiu Huang created CALCITE-3349:
--
Summary: Add Function DDL into SqlKind DDL enum
Key: CALCITE-3349
URL: https://issues.apache.org/jira/browse/CALCITE-3349
Project: Calcite
Issue Type:
Hi, Shubham Kumar
If I understand correctly, you want get the optimized(by materialized view)
SQL String. I wrote a simple test as below, please check if it's helpful
for you.
@Test public void testDEV() {
final String m = "select \"deptno\", \"empid\", \"name\""
+ "from \"emps\" where
Hey everyone,
Thank you for the help.
@Stamatis, @Danny : Thanks for pointing out that the reltosql api should
be used after volcano planner execution which considers materializations
and lattices, I understand it now.
@Xing: Yeah, it works perfectly fine, I am able to see simple substitutions
Wang Yanlin created CALCITE-3350:
Summary: Keep origin type for RexLiteral when deserialized from
json string
Key: CALCITE-3350
URL: https://issues.apache.org/jira/browse/CALCITE-3350
Project:
Hi Contributors,
I'm writing this email and hope to start a discussion about
https://issues.apache.org/jira/browse/CALCITE-3334 .
The approach of substitution-based materialized view matching is effective
for its simplicity and extensibility. But now and then we confront
materialization matching
Thanks a lot Danny and Haisheng for comments on the doc ~
And more comments are welcome ~
Best,
Jin
XING JIN 于2019年9月16日周一 下午9:17写道：
> Hi Contributors,
>
> I'm writing this email and hope to start a discussion about
> https://issues.apache.org/jira/browse/CALCITE-3334 .
>
> The approach of
18 matches
Mail list logo
