Build failed in Jenkins: Calcite » Calcite-snapshots #488

2023-06-16 Thread Apache Jenkins Server 
See 


Changes:

[Benchao Li] [CALCITE-5783] Support hint for TableFunctionScan


--
[...truncated 382.71 KB...]
 13.0sec, 
org.apache.calcite.adapter.geode.rel.GeodeBookstoreTest > 
testInSetFilterWithNestedStringField()
 12.9sec, 
org.apache.calcite.adapter.geode.rel.GeodeAllDataTypesTest > 
testSqlMultipleTimeWhereFilter()
 13.2sec, 
org.apache.calcite.adapter.geode.rel.GeodeAllDataTypesTest > 
testSqlWhereWithMultipleOrForAllFields()
 13.0sec, 
org.apache.calcite.adapter.geode.rel.GeodeBookstoreTest > 
testMissingProjectRelationOnGroupByColumnMatchingProjectedFields()
 13.0sec, 
org.apache.calcite.adapter.geode.rel.GeodeBookstoreTest > 
testSortWithProjection()
 13.0sec, 
org.apache.calcite.adapter.geode.rel.GeodeBookstoreTest > 
testAddMissingGroupByColumnToProjectedFields()
 12.9sec, 
org.apache.calcite.adapter.geode.rel.GeodeBookstoreTest > 
testLimit()
 13.3sec, 
org.apache.calcite.adapter.geode.rel.GeodeAllDataTypesTest > 
testSqlWhereWithMultipleOrForLiteralFields()
 12.9sec, 
org.apache.calcite.adapter.geode.rel.GeodeZipsTest > 
testMaxRaw()
 13.1sec, 
org.apache.calcite.adapter.geode.rel.GeodeBookstoreTest > 
testFilterWithNestedField()
 13.2sec, 
org.apache.calcite.adapter.geode.rel.GeodeBookstoreTest > 
testSortWithProjectionAndLimit()
 13.2sec, 
org.apache.calcite.adapter.geode.rel.GeodeBookstoreTest > 
testCount()
 13.2sec, 
org.apache.calcite.adapter.geode.rel.GeodeBookstoreTest > 
testWhereWithOr()
 13.5sec, 
org.apache.calcite.adapter.geode.rel.GeodeAllDataTypesTest > 
testSqlSingleTimestampWhereFilter()
 14.0sec, 
org.apache.calcite.adapter.geode.rel.GeodeAllDataTypesTest > 
testSqlSingleDateWhereFilter()
 14.3sec, 
org.apache.calcite.adapter.geode.rel.GeodeAllDataTypesTest > 
testSqlSingleTimeWhereFilter()
 25.5sec,   12 completed,   0 failed,   0 skipped, 
org.apache.calcite.adapter.geode.rel.GeodeAllDataTypesTest
  2.0sec, 
org.apache.calcite.adapter.geode.rel.GeodeBookstoreTest > 
testMaxMinSumAvg()
  2.5sec, 
org.apache.calcite.adapter.geode.rel.GeodeBookstoreTest > 
testMaxMinSumAvgInGroupBy()
  2.3sec, 
org.apache.calcite.adapter.geode.rel.GeodeBookstoreTest > 
testWhereWithOrAnd()
 26.4sec,   36 completed,   0 failed,   0 skipped, 
org.apache.calcite.adapter.geode.rel.GeodeBookstoreTest
  2.5sec, 
org.apache.calcite.adapter.geode.rel.GeodeZipsTest > 
testWhereWithOrForLargeValueList()
  2.5sec, 
org.apache.calcite.adapter.geode.rel.GeodeZipsTest > 
testItemPredicate()
WARNING  27.1sec,   14 completed,   0 failed,   3 
skipped, org.apache.calcite.adapter.geode.rel.GeodeZipsTest
WARNING  39.4sec,   62 completed,   0 failed,   3 
skipped, Gradle Test Run :geode:test

> Task :babel:test
Warning: JDBC driver threw non-SQLException
Warning: JDBC driver threw non-SQLException
 19.8sec, org.apache.calcite.test.BabelQuidemTest > 
test(String)[4], [4] sql/big-query.iq

> Task :spark:publishSparkPublicationToNexusRepository

> Task :plus:test
 42.8sec, org.apache.calcite.adapter.tpch.TpchTest 
> testQuery06()
 22.7sec, org.apache.calcite.adapter.tpch.TpchTest 
> testQuery14()
 21.0sec, org.apache.calcite.adapter.tpch.TpchTest 
> testQuery22()
 23.3sec, org.apache.calcite.adapter.tpch.TpchTest 
> testQuery13()
 43.4sec, org.apache.calcite.adapter.tpch.TpchTest 
> testQuery01()
 23.7sec, org.apache.calcite.adapter.tpch.TpchTest 
> testQuery12()
 25.0sec, org.apache.calcite.adapter.tpch.TpchTest 
> testQuery10()
 43.9sec, org.apache.calcite.adapter.tpch.TpchTest 
> testQuery04()
 23.0sec, org.apache.calcite.adapter.tpch.TpchTest 
> testQuery20()
 43.9sec, org.apache.calcite.adapter.tp

TAC Applications for Community Over Code North America and Asia now open

2023-06-16 Thread Gavin McDonald 
Hi All,

(This email goes out to all our user and dev project mailing lists, so you
may receive this
email more than once.)

The Travel Assistance Committee has opened up applications to help get
people to the following events:


*Community Over Code Asia 2023 - *
*August 18th to August 20th in Beijing , China*

Applications for this event closes on the 6th July so time is short, please
apply as soon as possible. TAC is prioritising applications from the Asia
and Oceania regions.

More details on this event can be found at:
https://apachecon.com/acasia2023/

More information on how to apply please read: https://tac.apache.org/


*Community Over Code North America - *
*October 7th to October 10th in Halifax, Canada*

Applications for this event closes on the 22nd July. We expect many
applications so please do apply as soon as you can. TAC is prioritising
applications from the North and South America regions.

More details on this event can be found at: https://communityovercode.org/

More information on how to apply please read: https://tac.apache.org/


*Have you applied to be a Speaker?*

If you have applied or intend to apply as a Speaker at either of these
events, and think you
may require assistance for Travel and/or Accommodation - TAC advises that
you do not
wait until you have been notified of your speaker status and to apply
early. Should you
not be accepted as a speaker and still wish to attend you can amend you
application to
include Conference fees, or, you may withdraw your application.

The call for presentations for Halifax is here:
https://communityovercode.org/call-for-presentations/
and you have until the 13th of July to apply.

The call for presentations for Beijing is here:
https://apachecon.com/acasia2023/cfp.html
and you have until the 18th June to apply.

*IMPORTANT Note on Visas:*

It is important that you apply for a Visa as soon as possible - do not wait
until you know if you have been accepted for Travel Assistance or not, as
due to current wait times for Interviews in some Countries, waiting that
long may be too late, so please do apply for a Visa right away. Contact
tac-ap...@tac.apache.org if you need any more information or assistance in
this area.

*Spread the Word!!*

TAC encourages you to spread the word about Travel Assistance to get to
these events, so feel free to repost as you see fit on Social Media, at
work, schools, universities etc etc...

Thank You and hope to see you all soon

Gavin McDonald on behalf of the ASF Travel Assistance Committee.

Build failed in Jenkins: Calcite » Calcite-snapshots #489

2023-06-16 Thread Apache Jenkins Server 
See 


Changes:

[Julian Hyde] [CALCITE-5761] Allow DECADE, CENTURY, and MILLENNIUM time units 
in DATE_TRUNC, TIMESTAMP_TRUNC, DATETIME_TRUNC functions


--
[...truncated 9.14 KB...]
> Task :buildSrc:fmpp:autostyleKotlinCheck
> Task :buildSrc:fmpp:autostyleKotlinGradleCheck
> Task :buildSrc:fmpp:autostyleCheck
> Task :buildSrc:fmpp:processTestResources NO-SOURCE
> Task :buildSrc:javacc:autostyleKotlinCheck
> Task :buildSrc:javacc:autostyleKotlinGradleCheck
> Task :buildSrc:javacc:autostyleCheck
> Task :buildSrc:javacc:processTestResources NO-SOURCE
> Task :buildSrc:fmpp:compileKotlin
> Task :buildSrc:fmpp:compileJava NO-SOURCE
> Task :buildSrc:fmpp:classes
> Task :buildSrc:fmpp:inspectClassesForKotlinIC
> Task :buildSrc:fmpp:jar
> Task :buildSrc:fmpp:assemble
> Task :buildSrc:fmpp:compileTestKotlin NO-SOURCE
> Task :buildSrc:fmpp:compileTestJava NO-SOURCE

> Task :buildSrc:javacc:compileKotlin
w: 
:
 (66, 13): 'setter for main: String?' is deprecated. Deprecated in Java

> Task :buildSrc:fmpp:pluginUnderTestMetadata
> Task :buildSrc:fmpp:testClasses UP-TO-DATE
> Task :buildSrc:javacc:compileJava NO-SOURCE
> Task :buildSrc:fmpp:test NO-SOURCE
> Task :buildSrc:buildext:compileKotlin
> Task :buildSrc:javacc:classes
> Task :buildSrc:javacc:inspectClassesForKotlinIC
> Task :buildSrc:buildext:compileJava NO-SOURCE
> Task :buildSrc:buildext:classes
> Task :buildSrc:buildext:inspectClassesForKotlinIC
> Task :buildSrc:javacc:jar
> Task :buildSrc:javacc:assemble
> Task :buildSrc:javacc:compileTestKotlin NO-SOURCE
> Task :buildSrc:javacc:compileTestJava NO-SOURCE
> Task :buildSrc:buildext:jar
> Task :buildSrc:buildext:assemble
> Task :buildSrc:javacc:pluginUnderTestMetadata
> Task :buildSrc:javacc:testClasses UP-TO-DATE
> Task :buildSrc:buildext:compileTestKotlin NO-SOURCE
> Task :buildSrc:javacc:test NO-SOURCE
> Task :buildSrc:test NO-SOURCE
> Task :buildSrc:buildext:compileTestJava NO-SOURCE
> Task :buildSrc:check
> Task :buildSrc:build
> Task :buildSrc:buildext:pluginUnderTestMetadata
> Task :buildSrc:buildext:testClasses UP-TO-DATE
> Task :buildSrc:buildext:test NO-SOURCE
> Task :buildSrc:fmpp:validatePlugins
> Task :buildSrc:javacc:validatePlugins
> Task :buildSrc:fmpp:check
> Task :buildSrc:fmpp:build
> Task :buildSrc:javacc:check
> Task :buildSrc:javacc:build
> Task :buildSrc:buildext:validatePlugins
> Task :buildSrc:buildext:check
> Task :buildSrc:buildext:build

> Configure project :
Building Apache Calcite 1.35.0-SNAPSHOT

Build calcite FAILURE reason:  
  
Caused by: Please correct the following before proceeding with the release:
1) Property asfNexusUsername is not specified
2) Property asfNexusPassword is not specified

at 
com.github.vlsi.gradle.release.StageVoteReleasePlugin.runValidations(StageVoteReleasePlugin.kt:407)
at 
com.github.vlsi.gradle.release.StageVoteReleasePlugin.access$runValidations(StageVoteReleasePlugin.kt:63)
at 
com.github.vlsi.gradle.release.StageVoteReleasePlugin$configureRoot$11.execute(StageVoteReleasePlugin.kt:314)
at 
com.github.vlsi.gradle.release.StageVoteReleasePlugin$configureRoot$11.execute(StageVoteReleasePlugin.kt:63)
at 
org.gradle.configuration.internal.DefaultListenerBuildOperationDecorator$BuildOperationEmittingInvocationHandler$1.lambda$run$0(DefaultListenerBuildOperationDecorator.java:255)
at 
org.gradle.configuration.internal.DefaultUserCodeApplicationContext$CurrentApplication.reapply(DefaultUserCodeApplicationContext.java:98)
at 
org.gradle.configuration.internal.DefaultListenerBuildOperationDecorator$BuildOperationEmittingInvocationHandler$1.run(DefaultListenerBuildOperationDecorator.java:253)
at 
org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:29)
at 
org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:26)
at 
org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)
at 
org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)
at 
org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:157)
at 
org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)
at 
org.gradle.internal.operations.DefaultBuildOperationRunner.run(DefaultBuildOperationRunner.java:47)
at

Re: PR 3258 Review Request

2023-06-16 Thread Julian Hyde 
Nice work.

(The hardest thing we do, as software engineers, is to make our work easy for 
others to understand. The fact that several databases have functions called 
CONCAT, with subtly different behaviors, made this task particularly 
challenging. You produced a solution that makes the differences really clear.)

I left one comment on the PR but it’s really close.

Julian


> On Jun 15, 2023, at 8:18 AM, Zhe Hu  wrote:
> 
> Hi, community.
> I’ve submitted a PR for applying two different NULL semantics for CONCAT 
> function, because this function now returns NULL when any of the arguments is 
> NULL, however Postgresql and MSSQL have different behavior(they treat NULL as 
> empty string).
> BTW, CONCAT enabled in Oracle(we call it CONCAT2 in Calcite) has been 
> resolved in CALCITE-5745, if anyone needs to refer to.
> 
> 
> https://github.com/apache/calcite/pull/3258
> 
> 
> Best,
> ZheHu
> 
> 
>

OSS-Fuzz

2023-06-16 Thread Julian Hyde 
Someone from Google logged a case offering to add Calcite to the
OSS-Fuzz program. (I work for Google but was not aware that we were
being considered.)

https://issues.apache.org/jira/browse/CALCITE-5781

How do people feel about participating in this program?

I think that it could improve our security significantly, but it will
take work. The fuzzer might generate a lot of false negatives. It
might also generate quite a few genuine security issues that we will
need to respond to appropriately. As an all-volunteer project it might
put a strain on us.

Julian

Re: OSS-Fuzz

2023-06-16 Thread Michael Mior 
Thanks for sharing Julian!

Do we *need* to respond to security issues that are uncovered? I certainly
agree that we *should* if at all possible. But by choosing not to
participate, we would be choosing not to respond to *all* security issues
that might only be uncovered via fuzzing. It seems reasonable to me
(assuming any discovered vulnerabilities can be kept private), that we
should be free to ignore issues that are uncovered.

--
Michael Mior
mm...@apache.org


On Fri, Jun 16, 2023 at 2:31 PM Julian Hyde  wrote:

> Someone from Google logged a case offering to add Calcite to the
> OSS-Fuzz program. (I work for Google but was not aware that we were
> being considered.)
>
> https://issues.apache.org/jira/browse/CALCITE-5781
>
> How do people feel about participating in this program?
>
> I think that it could improve our security significantly, but it will
> take work. The fuzzer might generate a lot of false negatives. It
> might also generate quite a few genuine security issues that we will
> need to respond to appropriately. As an all-volunteer project it might
> put a strain on us.
>
> Julian
>

Jenkins build is back to normal : Calcite » Calcite-snapshots #490

2023-06-16 Thread Apache Jenkins Server 
See