Thanks for your fast response. I've created
https://issues.apache.org/jira/browse/CALCITE-6394 to discuss about that.
Gonzalo,
I think the implementation is fairly straightforward. You’d write a new
implementation of RelWriter.
But, as Alessandro says, the specification is the hard part. What *exactly*
would you want instead of $0? (Those fields have names, and most of the time
they are the same as the user
Hi Gonzalo,
what would you expect when $i points to a complex expression from the input
relation(s)?
It's easier to brainstorm around a concrete running example, would you have
one to share? (existing vs sought behavior)
Best regards,
Alessandro
On Tue, 30 Apr 2024 at 12:39, Gonzalo Ortiz
Hi community,
I'm trying to improve explain plans in Apache Pinot and one of the main
complaints of our customers is how difficult it is to read the explain
plans having to transform the synthetic input names into the corresponding
logical field.
Is there a way to improve that? Ideally these
Cancel this thread, due to CALCITE-6385[1] issue in the build.
Thanks to Stamatis for highlighting this.
Will start another vote once the issue will be fixed and merged.
[1] https://issues.apache.org/jira/browse/CALCITE-6385
--
Best regards,
Sergey
ITE-6385 and
> produce a new RC.
>
> Best,
> Ruben
>
>
> On Wed, Apr 24, 2024 at 12:50 PM Sergey Nuyanzin
> wrote:
>
> > Thanks Stamatis for signalling this issue
> >
> > I think we need to put Blocker priority on this jira issue
> > (CALCITE-6385[1]
I think Stamatis is right. We should cancel this vote, fix CALCITE-6385 and
produce a new RC.
Best,
Ruben
On Wed, Apr 24, 2024 at 12:50 PM Sergey Nuyanzin
wrote:
> Thanks Stamatis for signalling this issue
>
> I think we need to put Blocker priority on this jira issue
> (CA
Thanks Stamatis for signalling this issue
I think we need to put Blocker priority on this jira issue
(CALCITE-6385[1]) if we consider it as a no go for the release (please
correct me if I'm wrong)
[1] https://issues.apache.org/jira/browse/CALCITE-6385
On Wed, Apr 24, 2024 at 11:59 AM Stamatis
Ubuntu 20.04.6 LTS, jdk1.8.0_261, Gradle wrapper, Gradle 7.6.1
* Checked signatures and checksums OK
* Checked diff between repo and artifacts OK
* Went over release note OK (Left comments in the PR)
* Checked README, NOTICE, LICENSE OK
* All source files have ASF headers OK (raised [1
+1 (binding)
- Checked signature and checksum (OK)
- Checked LICENSE and Copyright year (OK)
- Checked there are no unexpected binary files (OK)
- Build and test from source (testContributorsFileIsSorted and
testMailmapFile in LintTest failed due to not in git repo)
- Reviewed release note, left
Thanks Sergey for preparing this release.
Just a minor clarification: the email subject says "release candidate 1",
but we are actually voting rc0.
- Release notes: ok (with some minor comments that I have left in the PR)
- Checksum: ok
- Signature: ok
- Diff source release and git repo
Thanks for being RM for this release, Sergey!
My vote is: +1 (binding)
- Verified GPG signature - OK
- Verified SHA512 - OK
- Diffed source release and git repository - OK
- Checked release notes on tag
(https://github.com/apache/calcite/blob/calcite-1.37.0-rc0/site/_docs/history.md)
- OK
: "gradle build"
(requires an appropriate Gradle/JDK installation)
Please vote on releasing this package as Apache Calcite 1.37.0.
The vote is open for the next 72 hours and passes if a majority of at
least three +1 PMC votes are cast.
[ ] +1 Release this package as Apache Calcite 1.37.0
[ ]
Sergey Nuyanzin created CALCITE-6378:
Summary: Since docker 26.x pushing and pulling with image manifest
v2 schema 1 is disabled by default
Key: CALCITE-6378
URL: https://issues.apache.org/jira/browse/CALCITE
Thanks to everyone who has tested the release candidate and given
their comments and votes.
The tally is as follows.
3 binding +1s:
Benchao Li
Francis Chuang
Stamatis Zampetakis
1 non-binding +1s:
Istvan Toth
No 0s or -1s.
Therefore I am delighted to announce that the proposal to release
Ubuntu 20.04.6 LTS, jdk1.8.0_261, Gradle wrapper, Gradle 8.1.1
* Checked signatures and checksums OK
* Checked diff between repo and artifacts OK
* Went over release note OK (Minor comments at the end)
* Checked README, NOTICE, LICENSE OK ([1, 2, 3, 4] should be ported to Avatica)
* All
+1(binding)
- Verified checksum and signature (OK)
- Gone through release note (OK)
- Diffed source release with git repo (OK)
- Checked files in Nexus (OK)
- Compile and test sources with JDK8 (OK)
Noted that the tag link
(https://gitbox.apache.org/repos/asf?p=calcite-avatica.git;a=tag;h=refs
+1 (non binding)
Thanks for making the JDK8 build painless.
On Wed, Nov 29, 2023 at 1:21 AM Francis Chuang
wrote:
> Hi all,
>
> I have created a build for Apache Calcite Avatica 1.24.0, release
> candidate 1.
>
> Thanks to everyone who has contributed to this release
Hi all,
I have created a build for Apache Calcite Avatica 1.24.0, release
candidate 1.
Thanks to everyone who has contributed to this release.
You can read the release notes here:
https://github.com/apache/calcite-avatica/blob/avatica-1.24.0-rc1/site/_docs/history.md
The commit to be voted
LakeShen created CALCITE-5994:
-
Summary: When a sort's input max row cnt is 1,remove the redundant
sort
Key: CALCITE-5994
URL: https://issues.apache.org/jira/browse/CALCITE-5994
Project: Calcite
Julian Hyde created CALCITE-5802:
Summary: In RelBuilder add method aggregateExtended, to allow
aggregating complex expressions such as "1 + SUM(x + 2)"
Key: CALCITE-5802
URL: https://issues.apach
Benchao Li created CALCITE-5717:
---
Summary: Prune Project's input if project has no InputRef and the
input has 1 row
Key: CALCITE-5717
URL: https://issues.apache.org/jira/browse/CALCITE-5717
Project
asdfgh19 created CALCITE-5462:
-
Summary: unknown type -1 and unknown type -4 for mysql json and
blob columns
Key: CALCITE-5462
URL: https://issues.apache.org/jira/browse/CALCITE-5462
Project: Calcite
ite community,
>
> I'm trying to validate a SQL like the one below.
>
> SELECT user_id, COUNT(1) cnt FROM schema.table_name GROUP BY 1;
>
> It looks like in the default configuration, GROUP BY 1 is not considered
> valid. It complains user_id is not being grouped.
>
>
Hi Calcite community,
I'm trying to validate a SQL like the one below.
SELECT user_id, COUNT(1) cnt FROM schema.table_name GROUP BY 1;
It looks like in the default configuration, GROUP BY 1 is not considered
valid. It complains user_id is not being grouped.
Is there a quick configuration
Sergey Nuyanzin created CALCITE-5380:
Summary: CompositeSingleOperandTypeChecker fails with index (1)
must be less than size (1)
Key: CALCITE-5380
URL: https://issues.apache.org/jira/browse/CALCITE-5380
Aleksey Plekhanov created CALCITE-5288:
--
Summary: Expression '(a > 1 and a < 3) or (a > 2 and a < 4)'
cannot be simplified to 'SEARCH(a, Sarg[(1..4)])'
Key: CALCITE-5288
URL: https://issues.apa
I had to skip RC2 because of some changes to history.md (while the rc2 tag
was already created on gitbox).
The vote for RC3 has been sent.
On Fri, Jul 29, 2022 at 1:14 PM Andrei Sereda wrote:
> Hello,
>
> Due to checksum mismatches, voting for RC1 is cancelled.
>
> I will se
Hello,
Due to checksum mismatches, voting for RC1 is cancelled.
I will send another vote for RC2 shortly.
Regards,
Andrei.
Apologies for taking your time. I will create RC2 shortly.
Please consider the vote for RC1 cancelled.
On Fri, Jul 29, 2022 at 11:09 AM Ruben Q L wrote:
> I concur, there seems to be an issue with the checksum (I get the same
> result as Stamatis).
> Other checks ok.
>
&
I concur, there seems to be an issue with the checksum (I get the same
result as Stamatis).
Other checks ok.
-1 (binding)
On Fri, Jul 29, 2022 at 9:58 AM Stamatis Zampetakis
wrote:
> Ubuntu 20.04.4 LTS, jdk1.8.0_261, Gradle wrapper, Gradle 7.4.2
>
> * Checked checksums KO
>
Ubuntu 20.04.4 LTS, jdk1.8.0_261, Gradle wrapper, Gradle 7.4.2
* Checked checksums KO
* Went over release note OK (left minor comments in the draft PR)
$ sha512sum -c apache-calcite-1.31.0-src.tar.gz.sha512
apache-calcite-1.31.0-src.tar.gz: FAILED
sha512sum: WARNING: 1 computed checksum did
Hi all,
I have created a build for Apache Calcite 1.31.0, release
candidate 1.
Thanks to everyone who has contributed to this release.
You can read the release notes here:
https://github.com/apache/calcite/blob/calcite-1.31.0-rc1/site/_docs/history.md
The commit to be voted upon:
https
Benchao Li created CALCITE-5169:
---
Summary: 'xx < 1 OR xx > 1' cannot be simplified to 'xx <> 1'
Key: CALCITE-5169
URL: https://issues.apache.org/jira/browse/CALCITE-5169
Project: Calcite
honghui.Liu created CALCITE-5158:
Summary: count(1) with subquery count(distinct) gives wrong
results with hive.optimize.distinct.rewrite=true and cbo on
Key: CALCITE-5158
URL: https://issues.apache.org/jira
MC decided
>> to drop support for maintenance branches and focused on releasing
>> exclusively from master.
>>
>> This mail is related to the discussion about the release cadence [1] since
>> it would certainly help making Hive releases more regular. I decide
f the project if the PMC decided
> to drop support for maintenance branches and focused on releasing
> exclusively from master.
>
> This mail is related to the discussion about the release cadence [1] since
> it would certainly help making Hive releases more regular. I decided to
> s
branches for Hive.
I think it would be to the best interest of the project if the PMC decided
to drop support for maintenance branches and focused on releasing
exclusively from master.
This mail is related to the discussion about the release cadence [1] since
it would certainly help making Hive releases
Hi, Followers.
Thanks for the feedback. Yes, I have a misunderstanding about this.
when I try to simplify "a<>1 and a = 2 [a is nullable]":
checkSimplify3_(
and(ne(vInt(0), literal(1)),
eq(vInt(0), literal(2))),
ickets that I
>> had
>> > resolved (the fact that the commit which resolved the issue does not
>> belong
>> > to any repository any more). As Stamatis suggests, I think we should
>> put on
>> > hold the RC process until we figure out what happened
Due to the broken history problem, let's cancel this vote.
Thanks to all who have voted in this thread.
Best,
Liya Fan
think we should put
> on
> > hold the RC process until we figure out what happened and how to handle
> the
> > situation.
> >
> > Best,
> > Ruben
> >
> >
> > On Wed, Mar 9, 2022 at 10:13 AM Stamatis Zampetakis
&g
e the
> situation.
>
> Best,
> Ruben
>
>
> On Wed, Mar 9, 2022 at 10:13 AM Stamatis Zampetakis
> wrote:
>
>> Thanks for preparing the RC Liya!
>>
>> The repository seems to be in some weird state (see [1]) so I don't feel
>&g
til we figure out what happened and how to handle the
situation.
Best,
Ruben
On Wed, Mar 9, 2022 at 10:13 AM Stamatis Zampetakis
wrote:
> Thanks for preparing the RC Liya!
>
> The repository seems to be in some weird state (see [1]) so I don't feel
> comfortable getting a release o
Thanks for preparing the RC Liya!
The repository seems to be in some weird state (see [1]) so I don't feel
comfortable getting a release out till we understand what exactly has
happened.
Let's continue the discussion under the respective thread.
-1 (binding)
Stamatis
[1] https
+1 (non binding)
Run all tests of HerdDB, all tests are passing without any code
change. (https://github.com/diennea/herddb/pull/779)
I would like to note that previous tests of HerdDB did not pass with
1.29.0 (and we were stuck to 1.28.0). With 1.29.0 tests on Github
actions hang during some
Hi Xiong,
Thanks for your feedback. I will change the logs in a follow up MR.
Best,
Liya Fan
xiong duan 于2022年3月7日周一 15:30写道：
> Hi, Liya Fan.Thanks for your work. +1.
> Just a little problem:
> I noticed the Bug-fixes logs all started with FixI think maybe we
> should s
Hi, Liya Fan.Thanks for your work. +1.
Just a little problem:
I noticed the Bug-fixes logs all started with FixI think maybe we
should stay the same as JIRA summary or PR commit?
Fan Liya 于2022年3月7日周一 14:55写道：
> Hi all,
>
> I have created a build for Apache Calcite 1.30.0
Hi all,
I have created a build for Apache Calcite 1.30.0, release
candidate 1.
Thanks to everyone who has contributed to this release.
You can read the release notes here:
https://github.com/apache/calcite/blob/calcite-1.30.0-rc1/site/_docs/history.md
The commit to be voted upon:
https
Li wrote:
>
> Hi xiong,
>
> For the simplification result below:
> # "a <> 1 or a = 1 [a is nullable]"
> 1. UNKNOWN AS UNKNOWN: OR(IS NOT NULL(a), null)
> 2. UNKNOWN AS TRUE: TRUE
> 3. UNKNOWN AS FALSE: IS NOT NULL(a)
>
> # "a<>1 and a =
Hi xiong,
For the simplification result below:
# "a <> 1 or a = 1 [a is nullable]"
1. UNKNOWN AS UNKNOWN: OR(IS NOT NULL(a), null)
2. UNKNOWN AS TRUE: TRUE
3. UNKNOWN AS FALSE: IS NOT NULL(a)
# "a<>1 and a = 2 [a is nullable]"
1. UNKNOWN AS UNKNOWN: =(a, '2')
Hi followers.
When I learned how to simplify the Rexnode in Calcite. I meet a problem
and need some help.
For example:
When we simplify "a <> 1 or a = 1 [a is nullable]", (the result is
different according to how to treat the UNKNOW value) :
checkSimplify3_(or(ne(vI
zhangquan created CALCITE-5018:
--
Summary: org.apache.calcite.sql.parser.SqlParseException: Lexical
error at line 1, column 8. Encountered: "`" (96), after : ""
Key: CALCITE-5018
URL: https://is
Stamatis Zampetakis created CALCITE-4862:
Summary: Remove slf4j-log4j12 dependency using unsupported Log4j
1.x version
Key: CALCITE-4862
URL: https://issues.apache.org/jira/browse/CALCITE-4862
Stamatis Zampetakis created CALCITE-4858:
Summary: Use Log4j2 instead of unsupported Log4j (1.x) in tests
Key: CALCITE-4858
URL: https://issues.apache.org/jira/browse/CALCITE-4858
Project
Sorry about the chaos in the codes. I re-submit the code part.
```
// create schema for tables
SchemaPlus rootSchema = Frameworks.createRootSchema(true);
rootSchema.add("USERS", new AbstractTable() { //note: add a table
@Override
public RelDataType getRowType(final RelDataTypeFactory typeFactory)
I am getting start of Calcite. I want to translate a `SqlNode` to `RelNode`,
but fails due to assertion error of type mismatch:
```
ref:
CHAR(1) NOT NULL
input:
CHAR(1) NOT NULL
```
The code is simple:
```
private static final String sql = "select u.name as user_name\n" +
"
gument about it
in this thread. If and when there is a definitive statement from legal
bannining minified javascript, let us know.
Julian
On Sat, May 22, 2021 at 1:53 PM Vladimir Sitnikov
wrote:
>
> Here's a clarification from Roy:
> https://issues.apache.org/jira/browse/LEGAL-570?f
gt;
> The tally is as follows.
>
> 3 binding +1s:
> Francis Chuang
> Julian Hyde
> Stamatis Zampetakis
>
> 1 binding -1:
> Vladimir Sitnikov
>
> 1 non-binding +1s:
> Alessandro Solimando
>
> Therefore, I am delighted to announce that the proposal to release
> A
Thanks to everyone who has tested the release candidate and given their
comments and votes.
The tally is as follows.
3 binding +1s:
Francis Chuang
Julian Hyde
Stamatis Zampetakis
1 binding -1:
Vladimir Sitnikov
1 non-binding +1s:
Alessandro Solimando
Therefore, I am delighted to announce
.
Thanks a lot for pushing this Francis!
+1 (binding)
> diff -qr . ~/Projects/Apache/calcite-avatica
Only in /home/stamatis/Projects/Apache/calcite-avatica: .editorconfig
Only in /home/stamatis/Projects/Apache/calcite-avatica: .git
Only in /home/stamatis/Projects/Apache/calcite-avatica/gradle: wrap
You’re right. I did not intend to mis-state policy.
> On May 14, 2021, at 1:53 AM, Vladimir Sitnikov
> wrote:
>
> Julian>The vote passes if the number of +1 votes exceeds the number of -1
> votes by 3 or more.
>
> Julian, please check the regular rules:
> https://w
021, at 1:34 AM, Alessandro Solimando
> wrote:
>
> Hi Julian,
> I have copied both "gradlew" and the needed files under "gradle" directory
> from the local git repository to the unpacked directory extracted from the
> artifact downloaded from
> https://d
Julian>The vote passes if the number of +1 votes exceeds the number of -1
votes by 3 or more.
Julian, please check the regular rules:
https://www.apache.org/legal/release-policy.html#release-approval
I do not think we customized the release voting rules for Caclite.
Vladimir
(See
> https://issues.apache.org/jira/browse/CALCITE-4575 <
> https://issues.apache.org/jira/browse/CALCITE-4575>.)
>
> Julian
>
>
> > On May 12, 2021, at 3:00 AM, Alessandro Solimando <
> alessandro.solima...@gmail.com> wrote:
> >
> > Hi,
>
Let’s not have a discussion on the vote thread. Feel free to start a new
thread, or continue an existing discussion thread.
To re-state the rules. Every PMC member has a binding vote. The vote passes if
the number of +1 votes exceeds the number of -1 votes by 3 or more.
Vladimir is entitled
mpiled code from source releases and move on.
>the discussion in LEGAL-570 [1], suggests that images, PDFs and
>minified javascript is allowed
AFAIK, the LEGAL team is Justin Mclean and Roman Shaposhnik.
I do not see where they suggest that minified javascript is allowed in
source releases.
Hey Vladimir,
Thanks for taking the time to look at the release.
For 1), the discussion in LEGAL-570 [1], suggests that images, PDFs and
minified javascript is allowed in the source distribution as they are
classified as resources and not code. I am not a Java programmer, but I
can
Francis,
Thanks for preparing the release.
My vote is
[x] -1 Do not release this package because...
1) apache-calcite-avatica-1.18.0-src.tar.gz contains compiled code,
and it is forbidden to release compiled code in source packages.
site/js/html5shiv.min.js
site/js/respond.min.js
2) apache
lessandro Solimando
> wrote:
>
> Hi,
>
> +1 (non-binding) after verifying the release as follows.
>
> 1) Checksum: OK
>
> 2) Signature: OK
>
> 3) Running tests:
>
> -
>
> “./gradlew build -Prelease -PskipSign”: OK (see JVM, OS and gradle
> det
+1 (binding)
Checked hashes & signature. Compiled & ran tests on Linux / JDK 8, JDK
11, OpenJDK 15 / Gradle 6.8.1. Checked LICENSE, NOTICE. Ran rat.
Checked build instructions. Checked that contents of tar.gz match git
commit (except for gradle wrapper, licenses, fonts).
Thank you,
Hi all,
I have created a build for Apache Calcite Avatica 1.18.0, release
candidate 1.
Thanks to everyone who has contributed to this release.
You can read the release notes here:
https://github.com/apache/calcite-avatica/blob/avatica-1.18.0-rc1/site/_docs/history.md
The commit to be voted
Liya Fan created CALCITE-4582:
-
Summary: The distinct row count and population size should be 1
for deduced constant columns
Key: CALCITE-4582
URL: https://issues.apache.org/jira/browse/CALCITE-4582
Hi,you Zhuang I find clacite have SqlIfFunction,but it don't accomplish.
you Zhuang 于2021年2月21日周日 上午2:39写道：
> when does calcite support count(if(a=1, 1, null)) syntax ? spark, hive,
> clickhouse, impala, presto support the syntax for a long time.
>
Liya Fan created CALCITE-4511:
-
Summary: The number of distinct values for constant columns should
be 1
Key: CALCITE-4511
URL: https://issues.apache.org/jira/browse/CALCITE-4511
Project: Calcite
IF was added in https://issues.apache.org/jira/browse/CALCITE-3731 and
will be part of 1.27 release. IF is a dialect-specific function,
enabled in bigquery, hive and spark function tables.
There are several other ways you can achieve the same effect:
* COUNT(*) FILTER (WHERE a = 1)
* COUNT(CASE
when does calcite support count(if(a=1, 1, null)) syntax ? spark, hive,
clickhouse, impala, presto support the syntax for a long time.
Julian Hyde created CALCITE-4449:
Summary: When converting Sarg 'x IS NULL OR x NOT IN (1, 2)',
generate better SQL
Key: CALCITE-4449
URL: https://issues.apache.org/jira/browse/CALCITE-4449
Project
the doc of oracle[ref1]:
> >
> > The expr in the GROUPING function must match one of the expressions in
> the
> > GROUP BY clause. The function returns a value of 1 if the value of expr
> in
> > the row is a null representing the set of all values. Otherwise, it
> ret
Tao Tao wrote:
>
> Hi Julian
> I see, thanks, maybe use grouping id is better? Cuz seems not every engine
> has this grouping behavior, in the doc of oracle[ref1]:
>
> The expr in the GROUPING function must match one of the expressions in the
> GROUP BY clause. The funct
Hi Julian
I see, thanks, maybe use grouping id is better? Cuz seems not every engine
has this grouping behavior, in the doc of oracle[ref1]:
The expr in the GROUPING function must match one of the expressions in the
GROUP BY clause. The function returns a value of 1 if the value of expr
gt; After AggregateExpandDistinctAggregatesRule, I got a plan like this:
> The $10 in the project node is $g=[GROUPING($0, $1, $2, $3, $4, $5, $6,
> $7, $8)]) and we can see it is compared with value 1/2/3, but I check the
> def of grouping(), both pg and oracle, the value of grouping is 0
Hi
After AggregateExpandDistinctAggregatesRule, I got a plan like this:
The $10 in the project node is $g=[GROUPING($0, $1, $2, $3, $4, $5, $6,
$7, $8)]) and we can see it is compared with value 1/2/3, but I check the
def of grouping(), both pg and oracle, the value of grouping is 0 or 1
Caizhi Weng created CALCITE-4365:
Summary: SEARCHes in ANDs and ORs cannot be simplified if the
complexity of its SARG can actually be reduced to 1
Key: CALCITE-4365
URL: https://issues.apache.org/jira/browse
Danny Chen created CALCITE-4364:
---
Summary: "a in (1, 2) and a = 1" should be simplified to "a=1"
Key: CALCITE-4364
URL: https://issues.apache.org/jira/browse/CALCITE-4364
Ruben Q L created CALCITE-4258:
--
Summary: SqlToRelConverter: SELECT 1 IS [NOT] DISTINCT FROM NULL
fails with AssertionError
Key: CALCITE-4258
URL: https://issues.apache.org/jira/browse/CALCITE-4258
Haisheng,
Thanks for the release announcement yesterday:
https://lists.apache.org/thread.html/r555d7f90568ef199c65dfddcf58b14076ac803c0dca64d945d75ba69%40%3Cannounce.apache.org%3E.
Can you also send it to dev@?
Thank you for getting those 6 PRs into master (3985, 3988, 3910, 3999,
3478, 3950).
Now it is back to normal:
https://repo1.maven.org/maven2/org/apache/calcite/calcite-core/1.23.0/
On 2020/05/26 14:00:50, Haisheng Yuan wrote:
> Hi Enrico,
>
> Thanks for reporting the issue.
>
> I have created a JIRA ticket:
> https://issues.apache.org/jira/browse/INFRA-20326
>
> Thanks,
>
Hi Enrico,
Thanks for reporting the issue.
I have created a JIRA ticket:
https://issues.apache.org/jira/browse/INFRA-20326
Thanks,
Haisheng
On 2020/05/26 09:20:14, Enrico Olivelli wrote:
> Vladimir o Haisheng
> could you please open a ticket to INFRA ?
> I can do it myself, with your
Vladimir o Haisheng
could you please open a ticket to INFRA ?
I can do it myself, with your permission (I am not in Calcite
PMC/committers group)
Otherwise it is not possible to use Calcite 1.23.0 from downstream projects
Enrico
Il giorno mar 26 mag 2020 alle ore 10:34 Vladimir Sitnikov <
ASF releases are shared with repository.apache.org:
https://repository.apache.org/service/local/repositories/releases/content/org/apache/calcite/calcite-core/1.23.0/calcite-core-1.23.0.pom
It might be there are issues with ASF Nexus and Sonatype Nexus sync.
Vladimir
Haisheng
I still can't see Calcite 1.23.0 on Maven Central
https://search.maven.org/search?q=a:calcite-core
did the release procedure complete successfully?
Enrico
Il giorno dom 24 mag 2020 alle ore 14:35 JiaTao Tao ha
scritto:
> Vote: +1 (non-binding)
>
> CALCITE-38
Vote: +1 (non-binding)
CALCITE-3819 <https://issues.apache.org/jira/browse/CALCITE-3819> really
helps infinite planning in our use case. And I'm looking forward
to CALCITE-3997.
---
Environment: Mac-OS
JDK version: 1.8.0_212
Build with tests: OK
Regards!
Aron Tao
Vladimir Sitnikov 于2
>Looks like it is expected:
>https://github.com/gradle/gradle/issues/9758
It is not expected.
The way to fix it is to apply the following patch:
--- a/buildSrc/build.gradle.kts
+++ b/buildSrc/build.gradle.kts
@@ -19,7 +19,6 @@ import com.github.vlsi.gradle.properties.dsl.props
import
> * the first line printed by gradle is ':jar: No valid plugin
> descriptors were found in META-INF/gradle-plugins'; I don't know
> whether this is bad, but it looks bad
Looks like it is expected:
https://github.com/gradle/gradle/issues/9758
On 2020/05/21 18:41:41, Julian Hyde wro
Hi Vladimir,
Thanks for your explanation.
And thanks a lot for providing such an amazing release tool for us!
Cheers,
Haisheng
On 2020/05/23 16:28:52, Vladimir Sitnikov wrote:
> >But it said build successful. Is there anything I can do for the 404 Not
> Found error?
>
> It means "staging
>But it said build successful. Is there anything I can do for the 404 Not
Found error?
It means "staging repository no longer exists as it has just been released".
I've raised https://github.com/gradle-nexus/publish-plugin/issues/29 to
heal that.
However, gradle-nexus/publish-plugin is not yet
Hi,
I had the following error when executing the command:
./gradlew publishDist -Prc=1 -Pasf
> Task :releaseRepository
Initialized stagingRepositoryId orgapachecalcite-1089 for repository nexus
<==---> 50% EXECUTING [1m 17s]
GET request failed. 404: Not Found, body: [er
Thanks to everyone who has tested the release candidate and given
their comments and votes.
The tally is as follows.
5 binding +1s:
Haisheng, Francis, Danny, Julian Hyde, Laurent
5 non-binding +1s:
Anton, Enrico, Feng Zhu, Xing Jin, Forward Xu
1 non-binding +0s:
Ruben Q L
Therefore I am
My intent was not to cause sadness, sorry about that.
I should have elaborated a bit more why I don't think Github is that much
of an issue:
- LICENSE file at the root of the project is the source of truth, not
Github mention. It is a nice to have the correct license for Github for
sure, but it
1 - 100 of 305 matches
Mail list logo
