Hi,
IgottheSqlNodebyusingSqlParse.parseQuery()(Sqlbellow),butIcannotfindtheback_tickinSqlIdentifer
Sql:
SELECT`sql`,id1FROMtestdata
DebugwithIDEA:
Thanks a lot, Stamatis~
I will run slow tests from my local.
Best,
Jin
在 2019年12月14日星期六,Stamatis Zampetakis 写道:
> Hi Jin,
>
> If the test run fine locally at your machine (e.g., ./gradlew testSlow)
> then they should be fine in the CI.
> Labels are only available for committers yes!
>
> Best,
Hi Jin,
If the test run fine locally at your machine (e.g., ./gradlew testSlow)
then they should be fine in the CI.
Labels are only available for committers yes!
Best,
Stamatis
On Fri, Dec 13, 2019 at 4:52 PM XING JIN wrote:
> Thanks a lot Ruben ~
> I'm working on "[CALCITE-3478] Restructure
Thanks a lot Ruben ~
I'm working on "[CALCITE-3478] Restructure tests for materialized views" (
https://github.com/apache/calcite/pull/1560) , which contains "slow tests".
But I'm not sure how to add the label to PR. Is it only available for
committers ?
BTW, It's great if someone can help review
The Apache Jenkins build system has built Calcite-Master (build #1497)
Status: Failure
Check console output at https://builds.apache.org/job/Calcite-Master/1497/ to
view the results.
Hi Rui,
I'm glad that the fix was useful.
Thanks,
Igor
On Thu, Dec 12, 2019 at 8:16 PM Rui Wang wrote:
> Absolutely. Thanks lgor for the contribution! :)
>
>
> -Rui
>
> On Wed, Dec 11, 2019 at 10:54 PM Stamatis Zampetakis
> wrote:
>
> > So basically thanks to Igor :)
> >
> > On Wed, Dec 11,
Thanks for your clarification, Haisheng.
I am curious how to join the tables from different datasources.
Supposing there is tb1 in datasource1 and tb2 in datasource2 and the SQL is
`select tb1.col1, tb2.col2 from tb1, tb2 where tb1.id = tb2.id`, how to join
two of tables together and get
Yes, indeed.
Juan Pan (Trista)
Senior DBA & PPMC of Apache ShardingSphere(Incubating)
E-mail: panj...@apache.org
On 12/12/2019 18:00,Alessandro Solimando wrote:
Adapters must be needed by data sources not supporting SQL, I think this is
what Juan Pan was asking
Hi Jin,
this is the expected behavior: slow tests are not executed by default in PR
CI.
If you want slow tests to be executed in your PR, you need to explicitly
add the label "slow-tests-needed", as specified by [1].
You can see a PR example with this label here [2].
Best regards,
Ruben
[1]