Skip to content

Conversation

@ykmr1224
Copy link
Collaborator

Description

  • Separate build and validateAndBuild method in DataSourceMetadata to let internally build special DataSourceMetadata.
  • The validation doesn't allow datasource name starting from _(underscore)

Issues Resolved

n/a

Check List

  • New functionality includes testing.
    • All tests pass, including unit test, integration test and doctest
  • New functionality has been documented.
    • New functionality has javadoc added
    • New functionality has user manual doc added
  • Commits are signed per the DCO using --signoff

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.

@ykmr1224 ykmr1224 added backport 2.x maintenance Improves code quality, but not the product labels Jun 12, 2024
Signed-off-by: Tomoyuki Morita <moritato@amazon.com>
@noCharger
Copy link
Collaborator

noCharger commented Jun 12, 2024

Separate build and validateAndBuild method in DataSourceMetadata to let internally build special DataSourceMetadata.

Is it feasible to apply different set of validation rules on another DataSourceMetadata implementation? (With or without this PR)

@ykmr1224
Copy link
Collaborator Author

Separate build and validateAndBuild method in DataSourceMetadata to let internally build special DataSourceMetadata.

Is it feasible to apply different set of validation rules on another DataSourceMetadata implementation? (With or without this PR)

Any additional validation can be done when datasource is created.

@vamsimanohar
Copy link
Member

What is the use case that is driving this change?

@ykmr1224
Copy link
Collaborator Author

What is the use case that is driving this change?

When try to instantiate DataSourceMetadata with _xxxxx (starting from underscore), it was failing and we couldn't instantiate DataSourceMetadata with such special value.

@vamsimanohar
Copy link
Member

What is the use case that is driving this change?

When try to instantiate DataSourceMetadata with _xxxxx (starting from underscore), it was failing and we couldn't instantiate DataSourceMetadata with such special value.

Is this for testing?

@ykmr1224 ykmr1224 merged commit 7b40c2c into opensearch-project:main Jun 13, 2024
opensearch-trigger-bot bot pushed a commit that referenced this pull request Jun 13, 2024
Signed-off-by: Tomoyuki Morita <moritato@amazon.com>
(cherry picked from commit 7b40c2c)
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
ykmr1224 pushed a commit that referenced this pull request Jun 25, 2024
…) (#2752)

(cherry picked from commit 7b40c2c)

Signed-off-by: Tomoyuki Morita <moritato@amazon.com>
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>
jzonthemtn pushed a commit to jzonthemtn/sql that referenced this pull request Aug 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport 2.x maintenance Improves code quality, but not the product

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants