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 docs for 0.7 #4402

Merged
merged 2 commits into from
Jan 17, 2024
Merged

Update docs for 0.7 #4402

merged 2 commits into from
Jan 17, 2024

Conversation

fmassot
Copy link
Contributor

@fmassot fmassot commented Jan 16, 2024

@fmassot fmassot force-pushed the fmassot/update-docs-0.7 branch from 646c3c3 to 324b25d Compare January 17, 2024 00:06
@fmassot fmassot force-pushed the fmassot/update-docs-0.7 branch from 324b25d to 20b6afa Compare January 17, 2024 00:08
@fmassot fmassot requested a review from trinity-1686a January 17, 2024 00:12
Copy link
Contributor

@trinity-1686a trinity-1686a left a comment

Choose a reason for hiding this comment

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

we add a bunch of fastfields that we don't need, but can be convenient for our users if they query these index by themselves. We should document the minimum index config that works with Quickwit, so that one can replace the default config with that minimum config, and save on fastfield (and possibly indexing and doc_store) size, if they don't plan on doing anything fancy.

(this is a suggestion for future doc, not a change request for this PR)

@fmassot
Copy link
Contributor Author

fmassot commented Jan 17, 2024

Yes, you are referring to the Jaeger usage. We could add an "optimization" section to put this type of information.

@fmassot fmassot merged commit 170eead into main Jan 17, 2024
4 checks passed
@fmassot fmassot deleted the fmassot/update-docs-0.7 branch January 17, 2024 21:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants