-
Notifications
You must be signed in to change notification settings - Fork 507
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
Additions to data source acceleration #8759
Conversation
Signed-off-by: Liz Snyder <[email protected]>
Thank you for submitting your PR. The PR states are In progress (or Draft) -> Tech review -> Doc review -> Editorial review -> Merged. Before you submit your PR for doc review, make sure the content is technically accurate. If you need help finding a tech reviewer, tag a maintainer. When you're ready for doc review, tag the assignee of this PR. The doc reviewer may push edits to the PR directly or leave comments and editorial suggestions for you to address (let us know in a comment if you have a preference). The doc reviewer will arrange for an editorial review. |
@vagimeli you can also reach out to @Naarcha-AWS if you have questions, he has context on this. |
Assigning @Naarcha-AWS because he's familiar with this change. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few small changes, otherwise LGTM.
Co-authored-by: Naarcha-AWS <[email protected]> Signed-off-by: Liz Snyder <[email protected]>
Co-authored-by: Naarcha-AWS <[email protected]> Signed-off-by: Liz Snyder <[email protected]>
Co-authored-by: Naarcha-AWS <[email protected]> Signed-off-by: Liz Snyder <[email protected]>
Signed-off-by: Liz Snyder <[email protected]>
Implemented all of @Naarcha-AWS's comments. |
Signed-off-by: Liz Snyder <[email protected]>
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-2.15 2.15
# Navigate to the new working tree
pushd ../.worktrees/backport-2.15
# Create a new branch
git switch --create backport/backport-8759-to-2.15
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 03c8b18678250befa073744fd9ce5af52be09c63
# Push it to GitHub
git push --set-upstream origin backport/backport-8759-to-2.15
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-2.15 Then, create a pull request where the |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-2.16 2.16
# Navigate to the new working tree
pushd ../.worktrees/backport-2.16
# Create a new branch
git switch --create backport/backport-8759-to-2.16
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 03c8b18678250befa073744fd9ce5af52be09c63
# Push it to GitHub
git push --set-upstream origin backport/backport-8759-to-2.16
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-2.16 Then, create a pull request where the |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-2.17 2.17
# Navigate to the new working tree
pushd ../.worktrees/backport-2.17
# Create a new branch
git switch --create backport/backport-8759-to-2.17
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 03c8b18678250befa073744fd9ce5af52be09c63
# Push it to GitHub
git push --set-upstream origin backport/backport-8759-to-2.17
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-2.17 Then, create a pull request where the |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-2.18 2.18
# Navigate to the new working tree
pushd ../.worktrees/backport-2.18
# Create a new branch
git switch --create backport/backport-8759-to-2.18
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 03c8b18678250befa073744fd9ce5af52be09c63
# Push it to GitHub
git push --set-upstream origin backport/backport-8759-to-2.18
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-2.18 Then, create a pull request where the |
* Additions to data source acceleration Signed-off-by: Liz Snyder <[email protected]> * Update _dashboards/management/accelerate-external-data.md Co-authored-by: Naarcha-AWS <[email protected]> Signed-off-by: Liz Snyder <[email protected]> * Update _dashboards/management/accelerate-external-data.md Co-authored-by: Naarcha-AWS <[email protected]> Signed-off-by: Liz Snyder <[email protected]> * Update _dashboards/management/accelerate-external-data.md Co-authored-by: Naarcha-AWS <[email protected]> Signed-off-by: Liz Snyder <[email protected]> * Implement feedback Signed-off-by: Liz Snyder <[email protected]> * Update required ruby version Signed-off-by: Liz Snyder <[email protected]> --------- Signed-off-by: Liz Snyder <[email protected]> Co-authored-by: kolchfa-aws <[email protected]> Co-authored-by: Naarcha-AWS <[email protected]> Signed-off-by: Eric Pugh <[email protected]>
Description
I'm updating this topic to include some functionality that must have been added by the dev team. I'm also porting over some SQL query examples from the service docs: https://docs.aws.amazon.com/opensearch-service/latest/developerguide/direct-query-s3-configure-accelerate.html
They belong in the open source docs, and we plan to remove them from the AWS docs.
Issues Resolved
N/A
Version
All
Frontend features
N/A
Checklist
For more information on following Developer Certificate of Origin and signing off your commits, please check here.