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

Update SQL plugin documentation #830

Closed
wants to merge 3 commits into from
Closed

Update SQL plugin documentation #830

wants to merge 3 commits into from

Conversation

Yury-Fridlyand
Copy link
Contributor

Signed-off-by: Yury Fridlyand [email protected]

Description

Update SQL plugin documentation.

Issues Resolved

  • Update all SQL plugin information
  • Update list of SQL and PPL functions
  • Add relevancy search (full-text search) functions:
    • Most of them are already released in 2.1.0
    • query_string and match_phrase_prefix would be released in 2.2.0
  • [FEATURE]: Add PPL functions section #442 - PPL language block moved from observability plugin to SQL plugin, because it is provided by the SQL plugin.
  • Update website cross-links

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.

@Yury-Fridlyand
Copy link
Contributor Author

@Naarcha-AWS, do you want me to rebase and squash? This will fix the DCO failure as well, I think.

@Naarcha-AWS
Copy link
Collaborator

@Yury-Fridlyand: Please do!

Update SQL plugin relevance functions documentation.

Co-authored-by: MaxKsyunz <[email protected]>
Signed-off-by: Yury Fridlyand <[email protected]>
@Yury-Fridlyand
Copy link
Contributor Author

@Naarcha-AWS, ready for review, thanks!

1. Save the sample [accounts test data](https://github.com/opensearch-project/sql/blob/main/doctest/test_data/accounts.json) file.

1. Index the sample data.
1. Run the CLI tool. If you cluster runs with default security settings, use following command line:
Copy link
Contributor

Choose a reason for hiding this comment

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

"If your cluster runs with the default security settings, use the following command:"

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thank you, fixed in d5e9d0d.

Signed-off-by: Yury Fridlyand <[email protected]>
@@ -10,7 +10,7 @@ has_toc: false

ML Commons for OpenSearch eases the development of machine learning features by providing a set of common machine learning (ML) algorithms through transport and REST API calls. Those calls choose the right nodes and resources for each ML request and monitors ML tasks to ensure uptime. This allows you to leverage existing open-source ML algorithms and reduce the effort required to develop new ML features.

Interaction with the ML Commons plugin occurs through either the [REST API]({{site.url}}{{site.baseurl}}/ml-commons-plugin/api) or [AD]({{site.url}}{{site.baseurl}}/observability-plugin/ppl/commands#ad) and [kmeans]({{site.url}}{{site.baseurl}}/observability-plugin/ppl/commands#kmeans) Piped Processing Language (PPL) commands.
Interaction with the ML Commons plugin occurs through either the [REST API]({{site.url}}{{site.baseurl}}/ml-commons-plugin/api) or [AD]({{site.url}}{{site.baseurl}}/search-plugins/sql/ppl/functions#ad) and [kmeans]({{site.url}}{{site.baseurl}}/search-plugins/sql/ppl/functions#kmeans) Piped Processing Language (PPL) commands.
Copy link
Member

Choose a reason for hiding this comment

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

i think i brought this up previously but couldn't remember the conclusion. SQL is under search category and PPL is under observability category because they have different use cases from user's perspective. is there a reason to move PPL out of observability?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I agree with you -- the use cases are different. I moved to SQL, because it is implemented by SQL plugin. I'm welcome for proposals and ready to move it back.

Copy link
Member

Choose a reason for hiding this comment

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

got it. I don't have a strong opinion on this, i think it's ok if no objections

@@ -1,76 +1,17 @@
---
layout: default
title: SQL
title: SQL Plugin - SQL & PPL
Copy link
Member

Choose a reason for hiding this comment

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

i don't see other plugin titles having Plugin in them, should this just say SQL & PPL?

title: Commands
parent: Piped processing language
nav_order: 4
title: Functions
Copy link
Member

Choose a reason for hiding this comment

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

the content in this file are mostly commands instead of functions?

@@ -1,7 +1,7 @@
---
layout: default
title: Functions
Copy link
Member

Choose a reason for hiding this comment

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

i see there are sql/sql/functions, sql/ppl/functions (those are actually commands), sql/functions.

SQL language supports all SQL plugin functions

PPL supports all SQL functions

sql/functions are referred as "SQL functions" or "SQL plugin functions", but then there are also SQL specific functions (sql/sql/functions). seems a bit confusing, should sql/functions be referred as maybe SQL plugin common (or shared) functions?

@Yury-Fridlyand
Copy link
Contributor Author

@Naarcha-AWS,
Do you have any news for me so far?

@Yury-Fridlyand
Copy link
Contributor Author

Dear @hdhalter,
May I ask you to have a look on this PR?

@Naarcha-AWS Naarcha-AWS added 1 - Backlog Issue: The issue is unassigned or assigned but not started v2.1.0 v2.2.0 labels Aug 25, 2022
@Naarcha-AWS Naarcha-AWS added this to the 2022-Q3 milestone Aug 25, 2022
@Naarcha-AWS
Copy link
Collaborator

@Yury-Fridlyand: Are you if someone from the Docs team takes this PR over and adds edits and redirects?

@Yury-Fridlyand
Copy link
Contributor Author

@Yury-Fridlyand: Are you if someone from the Docs team takes this PR over and adds edits and redirects?

For sure, do whatever you need.

@Naarcha-AWS Naarcha-AWS added backport 2.1 PR: Backport label for 2.1 backport 2.2 PR: Backport label for 2.2 and removed v2.1.0 v2.2.0 labels Aug 25, 2022
@Naarcha-AWS
Copy link
Collaborator

@Yury-Fridlyand: Closing this in favor of #1111

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 - Backlog Issue: The issue is unassigned or assigned but not started backport 2.1 PR: Backport label for 2.1 backport 2.2 PR: Backport label for 2.2
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants