[AUTOCUT] OS Distribution Build Failed for sql-3.0.0

[opensearch-ci-bot]

Received Error: Error building sql, retry with: ./build.sh manifests/3.0.0/opensearch-3.0.0.yml --component sql.
The distribution build for sql has failed.
Please see build log at https://build.ci.opensearch.org/job/distribution-build-opensearch/6445/consoleFull

[Yury-Fridlyand]

Again?

> Task :opensearch-sql-plugin:compileJava FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':opensearch-sql-plugin:compileJava'.
> Could not resolve all dependencies for configuration ':opensearch-sql-plugin:compileClasspath'.
   > Conflict(s) found for the following module(s):
       - com.fasterxml.jackson.dataformat:jackson-dataformat-smile between versions 2.14.0 and 2.13.4
       - com.fasterxml.jackson.dataformat:jackson-dataformat-yaml between versions 2.14.0 and 2.13.4
     Run with:
         --scan or
         :opensearch-sql-plugin:dependencyInsight --configuration compileClasspath --dependency com.fasterxml.jackson.dataformat:jackson-dataformat-smile
     to get more insight on how to solve the conflict.

[ohltyler]

@Yury-Fridlyand #1058 was only merged to 2.4 & 2.x branches - can you frontport to main? That should fix it.

[ohltyler]

Also, is there a reason this repo's default branch is 2.x? It's the only one in opensearch-project I see this way.

[Yury-Fridlyand]

Also, is there a reason this repo's default branch is 2.x? It's the only one in opensearch-project I see this way.

#692 (comment)
I think this approach reduces amount of actions and backports we need.

[ohltyler]

Also, is there a reason this repo's default branch is 2.x? It's the only one in opensearch-project I see this way.

#692 (comment) I think this approach reduces amount of actions and backports we need.

I feel this can cause confusion from contributors when this is the single repo with a different default branch. From my understanding all repos should be aligned with the core branching strategy.

Also the idea with having 3.0 as default, is to ensure that plugins are able to stay up-to-date with breaking changes in 3.0 such that there will be no big surprises when preparing for 3.0 release. Just my thoughts.

[penghuo]

Merge 2.x to main failed, #1063, pending on ML commons fix on 3.0.

  [2022-11-14 16:10:05] [autobuild] /home/runner/work/sql/sql/opensearch/src/main/java/org/opensearch/sql/opensearch/planner/physical/MLCommonsOperatorActions.java:248: error: cannot find symbol
  [2022-11-14 16:10:05] [autobuild]             .run(mlinput, arguments)
  [2022-11-14 16:10:05] [autobuild]             ^
  [2022-11-14 16:10:05] [autobuild]   symbol:   method run(MLInput,Map<String,Object>)

[jmazanec15]

@penghuo is there a tracking issue in ml-commons?

[ylwu-amzn]

We need to forward port changes in 2.x to main branch. Create an issue to track this opensearch-project/ml-commons#553

[penghuo]

Still pending on ML commons fix. #1063

[Yury-Fridlyand]

Can we close this? Build for 3.0.0 pass today: https://build.ci.opensearch.org/job/distribution-build-opensearch/6708/