Hey everyone, We want to use the JDBC Grpc Client that was introduced in 1.4.0, but getting error building from maven:

Failed to collect dependencies at org.apache.pinot:pinot-jdbc-client:jar:1.4.0:
Failed to read artifact descriptor for org.apache.pinot:pinot-jdbc-client:jar:1.4.0: The following artifacts could not be resolved: org.apache.pinot:pinot:pom:1.4.0 (absent)

Checking in Maven Central, pinot-1.4.0 doesn't seem to be there. Are their plans for pushing the remaining 1.4.0 jars to Maven Central? Are we missing something else?

@Qiaochu Liu was this step missed in the 1.4.0 release process? I don't see many of the JARs for 1.4.0 on Maven central, for instance - https://mvnrepository.com/artifact/org.apache.pinot/pinot-common (https://apache-pinot.slack.com/archives/CDRCA57FC/p1759662537526619) cc - @Mayank

i followed this step: https://cwiki.apache.org/confluence/display/PINOT/Creating+an+Apache+Release#CreatinganApacheRelease-MavenConfigurationSetup it mentioned the artifacts are published to maven central staging repo. let me check with @Xiang Fu and @Mayank on what's missed here

Not that I'm aware of, @Abhishek Sharma do you happen to know since you were the last release manager?

correct, the maven publish was succeed

Publish the maven artifacts. Log in to Nexus, select the staging repository (orgapachepinot-<number>) and click Release button. Several hours later, the new version should show up at https://repo.maven.apache.org/maven2/org/apache/pinot

This step?

this step was completed successfully as well. i observed some artifact has been updated the timestamp. while some are not https://repo.maven.apache.org/maven2/org/apache/pinot/

Hm I guess we might need to try re-running?

For me, this step passed without any issues. Please check that all the required jar are there in

pinot-distribution

target folder before uploading.

thank you, let me check

I saw libs are partially published. Some modules are missing for 1.4.0

gotcha, thanks. should i republish with the staging steps first.

yes

i think this issue has been resolved, thanks @Xiang Fu @Yash Mayya @Abhishek Sharma for help!

👍