[v3.0.0] Remove SparkSQL support

[ykmr1224]

Description

• Remove SparkSQL support for v3.0.0
• Removed spark module. A few classes are used by async-query-core and those are moved.

Related Issues

Resolves #3286

Check List

• New functionality includes testing.
• New functionality has been documented.
• New functionality has javadoc added.
• New functionality has a user manual doc added.
• API changes companion pull request created.
• Commits are signed per the DCO using --signoff.
• Public documentation issue/PR created.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[noCharger]

@penghuo mentioned to keep spark module. Is there any necessity to remove?

[ykmr1224]

@penghuo mentioned to keep spark module. Is there any necessity to remove?

Once removed the SparkSQL support, the remaining classes are used only by async-query-core. I didn't see necessity to keep this module.
@penghuo Can you give your thoughts?

[penghuo]

@penghuo mentioned to keep spark module. Is there any necessity to remove?

Once removed the SparkSQL support, the remaining classes are used only by async-query-core. I didn't see necessity to keep this module. @penghuo Can you give your thoughts?

the remaining classes are used only by async-query-core?

the remaining classes means classed in Spark module? If yes, remove SparkSQL module will impact async-query?

[ykmr1224]

the remaining classes means classed in Spark module? If yes, remove SparkSQL module will impact async-query?

Yes, remaining classes in spark module.
Following classes were dependency from async-query-core module, and I moved them from spark module to async-query-core in this PR.

• SparkSqlFunctionResponseHandle
• DefaultSparkSqlFunctionResponseHandle
• SparkDataType
• SparkExprValue

[penghuo]

Thx!

[dai-chen]

Thanks for the changes!

[y3n11]

Hi OpenSearch team,

I would like to better understand the implications of the removal of the SparkSQL connector. We are currently using OpenSearch along with PySpark in a production application, querying data with the library "opensearch-spark-30_2.12-1.3.0.jar" and spark.read.

Can we still use this approach with OpenSearch 3.0.0, or will we need to make changes?

Thank you in advance! @ykmr1224

[noCharger]

Hi OpenSearch team,

I would like to better understand the implications of the removal of the SparkSQL connector. We are currently using OpenSearch along with PySpark in a production application, querying data with the library "opensearch-spark-30_2.12-1.3.0.jar" and spark.read.

Can we still use this approach with OpenSearch 3.0.0, or will we need to make changes?

Thank you in advance! @ykmr1224

opensearch-spark-30_2.12-1.3.0.jar is maintained by a different repo: https://github.com/opensearch-project/opensearch-hadoop. I would suggest ask there.