Add blog post "A deep dive into faster semantic sparse retrieval in OpenSearch 2.12"

[zhichao-aws]

Description

Add blog post A deep dive into faster semantic sparse retrieval in OpenSearch 2.12

Issues Resolved

#2792

Check List

• 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 BSD-3-Clause License.

[natebower]

@zhichao-aws Please see my comments and changes and let me know if you have any questions. Thanks for putting this together!

@pajuric Because this was so rough and not totally ready for editorial review (it looks like others may still be providing feedback), I had to guess at a lot of revisions/articles/etc. and am not confident in the quality of this post, even with my edits committed. I think I was able to improve it quite a bit, but I'm certain there are still errors present throughout. I would strongly recommend that this be reviewed by a technical writer and re-edited by me prior to publication. Thanks!

[zhichao-aws]

Hi @natebower, I just modified the blog post according to the comments.

I had to guess at a lot of revisions/articles/etc. and am not confident in the quality of this post, even with my edits committed. I think I was able to improve it quite a bit, but I'm certain there are still errors present throughout. I would strongly recommend that this be reviewed by a technical writer and re-edited by me prior to publication. Thanks!

The blog post has gone through several turns of reviews and approved by PM and SDM, I believe we won't conduct major changes to the blog content. For the concerns on "quality", could you please help clarify whether the concerns are for the content perspective or other perspectives like wordings, grammars etc?

[natebower]

Hi @natebower, I just modified the blog post according to the comments.

I had to guess at a lot of revisions/articles/etc. and am not confident in the quality of this post, even with my edits committed. I think I was able to improve it quite a bit, but I'm certain there are still errors present throughout. I would strongly recommend that this be reviewed by a technical writer and re-edited by me prior to publication. Thanks!

The blog post has gone through several turns of reviews and approved by PM and SDM, I believe we won't conduct major changes to the blog content. For the concerns on "quality", could you please help clarify whether the concerns are for the content perspective or other perspectives like wordings, grammars etc?

My understanding is that @kolchfa-aws was initially asked to support this blog post, given that she wrote the documentation for the feature/functionality, so I’d like for her to review this prior to a second editorial review by me to ensure both quality/accuracy of the content and alignment of messaging between the documentation and the blog post. Thanks!

[natebower]

@kolchfa-aws Thanks so much for your work on this 😄. Please see my comments and changes and push to @pajuric when complete. Thanks!

[kolchfa-aws]

@natebower Thank you for reviewing! I addressed all your comments. @zhichao-aws If you want to read it over one more time, please do. Otherwise, this blog is ready. cc @pajuric

[pajuric]

@nateynateynate @krisfreedain - The blog is ready to push live. With Kris and Nate Boot out of office, are you able to help get this live @kolchfa-aws @natebower, please.

[natebower]

LGTM