Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add langType to FlintStatement model #664

Merged
merged 1 commit into from
Sep 14, 2024

Conversation

noCharger
Copy link
Collaborator

Description

Add langType to FlintStatement model

Issues Resolved

N/A

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.

query,
"",
queryId,
LangType.SQL,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not a big concern but I feel like hard coded SQL isn't ideal. In principle our batch FlintJob could run even if provided with a PPL query.
However, if the language type isn't passed from async-query-core to the spark job by setting the spark conf, then really there's no way to get this lang type dynamically.

I know that our async-query-core use case always use FlintJob for Flint extension SQL queries only, so this could be fine

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Exactly, FlintJob is only used for SQL use case hense langType not passed to parameter https://github.com/opensearch-project/sql/blob/25064688db2d08e61579aaf7d21ff440c67605a4/async-query-core/src/main/java/org/opensearch/sql/spark/data/constants/SparkConstants.java#L88-L89. With warmpool the FlintStatement should come from async-query-core statement model.

@noCharger noCharger self-assigned this Sep 14, 2024
@noCharger noCharger merged commit 7a4c206 into opensearch-project:main Sep 14, 2024
6 checks passed
opensearch-trigger-bot bot pushed a commit that referenced this pull request Sep 14, 2024
Signed-off-by: Louis Chu <[email protected]>
(cherry picked from commit 7a4c206)
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
opensearch-trigger-bot bot pushed a commit that referenced this pull request Sep 14, 2024
Signed-off-by: Louis Chu <[email protected]>
(cherry picked from commit 7a4c206)
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
noCharger pushed a commit that referenced this pull request Sep 15, 2024
(cherry picked from commit 7a4c206)

Signed-off-by: Louis Chu <[email protected]>
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
noCharger pushed a commit that referenced this pull request Sep 16, 2024
(cherry picked from commit 7a4c206)

Signed-off-by: Louis Chu <[email protected]>
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants