Calcite guava #342
Open
Calcite guava #342
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…syncPreviewSiteRepo' Upgrade vlsi-release-plugins to version 1.74 which has a workaround for this error that comes from the upgrade to Gradle 7.0
Jacques' description of breaking changes is rather too long for the release notes, so I added it to the news item, and referenced it from the release notes. Make other fixes to the release notes, such as the poorly escaped '<>' in one commit message. Add permanent anchors (qualified by release name) to the release notes, so that #fixes for one release doesn't become that. Prepare for next development iteration by changing version in gradle.properties. Close apache#2584
Solve by documenting the `Pasf.git.pushRepositoryProvider=GITBOX` flag. Without the flag, the `prepareVote` task pulls from `github.com`, which no longer allows password-based authentication. Add some sample git reports reports, run using `sqlsh`.
Also remove superseded rule configuration interfaces
…te (part 2) This commit is part 2 of 2, after release 1.28, and removes APIs marked 'deprecated to be removed before 1.29'. The 'operands' field is now an immutable list (that may contain null values). If a user calls setOperand, a new list is created. Therefore operands do not need to be cloned when the call is cloned. The 'expanded' field has been removed, because it is typically false. There is a sub-class where isExpanded() returns true.
1. Replace slf4j-log4j12 dependency (using Log4j 1.x) with log4j-slf4j-impl (using Log4j 2.x) when possible. Cannot remove Log4j 1.x from Pig/Piglet modules due to compilation dependency of the latter directly to log4j. 2. Use XML syntax instead of property syntax for Log4j configuration. A Log4j configuration is hierarchical by nature so formats with natural support for nesting (such as XML) are easier to use. 3. Exclude slf4j-log4j12 when it comes transitively from other dependencies. It gets in conflict with log4j-slf4j-impl and it may also appear transitively in projects using Calcite. 4. Add log4j-slf4j-impl in modules (kafka, mongodb, plus, example) to silence error messages due to missing logger implementation. 5. Always use testRuntimeOnly annotation for dependencies on SLF4J logger implementation. Calcite shouldn't enforce a specific logger implementation so they should never appear as compile or runtime dependencies. A concrete implementation is only needed when we want to log messages for testing purposes. 6. Bump Cassandra version to 3.11.3 to use Log4j2 in tests. Previous versions did not allow the use of any custom logger implementation (only logback). This was resolved CASSANDRA-13396 so now we can use Log4j2 as the rest of the tests. 7. Unify display pattern in elasticsearch log4j2.xml with the rest of tests. 8. Add/Modify Log4j2 configuration (log4j2-test.xml) to silence errors and not display logging messages in tests. Instead of globally turning off logs, specific logger entries were set in the configuration files: (i) to avoid hiding by accident important problems; (ii) to faciliate switching log levels during debugging in the future. Close apache#2587
…ct data type for top aggregate calls (Taras Ledkov) Close apache#2560
…H for BigQuery dialect
* Changing RelMetadataQueryBase.map generic from Table<Object, List, Object> to Table<Object, Object, Object> to support more efficient cache keys. * Adding regression test generated RelMetdata code. * Adding api status internal to DescriptiveCacheKey. * Splitting code generation out of JaninoRelMetadataHandler to RelMetadataHandlerGenerator. * Moving DispatchGenerator to be packaged scoped. * In DispatchGenerator, sorting RelNode class by name so the dispatch orders is repeatable. Close apache#2585
…to latest 4.x * Updated Cassandra from 3.11.2 to 4.0.1 * Updated Datastax Driver from 3.6.0 to 4.13.0 * Updated cassandra-unit from 3.5.0.1 to 4.3.1.0 * Cassandra tests are: - now compatible with Guava >= 25 but are not anymore compatible with Guava < 20 - still incompatible with Eclipse OpenJ9 (due to Cassandra) - still incompatible with JDK11+ (due to cassandra-unit)
It resolves some of Gradle 7 warnings, and it hides some stacktraces (e.g. code style violations, compilation failure)
Gradle 7.3 is the first release with the official support of Java 17 See https://docs.gradle.org/7.3/release-notes.html
…o Values, and gives incorrect results
…ustomized JsonBuilder
- Introduce a new `decimal` type in the CSV file format for more accurate representation of decimal data. - Implement the `decimal` SQL type using the BigDecimal JAVA type.
…wrong result while EnumerableIntersect is followed by EnumerableLimit
Unfortunately, the button loses committer info as follows (it uses GitHub noreply for committer): commit a8e50734e0460e506f1762fbe0f628bcb444b8f5 Author: Denys Kuzmenko <[email protected]> AuthorDate: Tue Nov 30 10:09:06 2021 +0200 Commit: GitHub <[email protected]> CommitDate: Tue Nov 30 09:09:06 2021 +0100
…ion when externalizing Exchange operator from JSON
…eldTrimmer to align with the community
… use of dynamic parameter exception
…avoid incorrect null vs true/false comparisons
…l for replacing cc
support ifnull
support ifnull
…is non-numeric Close apache#3038 Co-authored-by: Bruce Irschick <[email protected]>
KE-11534 Upgrade Calcite to 1.30 and adapt it for Kylin
Co-authored-by: David Handermann <[email protected]> (cherry picked from commit ba80b91)
KE-11534 [Follow up]Remove the if operator check
KE-11534 [Follow up]IF and IFNULL do not fold as constants
…ions when it fails (apache#345)
…ptimization errors (apache#346)
|
This pull request has been marked as stale due to 30 days of inactivity. It will be closed in 90 days if no further activity occurs. If you think that’s incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the PR at any time and @mention a reviewer or discuss it on the [email protected] list. Thank you for your contributions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.