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

Make ingest V2 the default ingest #5279

Open
fmassot opened this issue Jul 31, 2024 · 2 comments
Open

Make ingest V2 the default ingest #5279

fmassot opened this issue Jul 31, 2024 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@fmassot
Copy link
Contributor

fmassot commented Jul 31, 2024

We will ship the ingest V2 for 0.9. It should be activated by default. I suggest making it the default now on the main branch.

@fmassot fmassot added the enhancement New feature or request label Jul 31, 2024
@rdettai
Copy link
Contributor

rdettai commented Aug 23, 2024

Should we add #4438 to the 0.9 milestone if ingest V2 becomes the default?

@rdettai
Copy link
Contributor

rdettai commented Sep 5, 2024

@fmassot just to be sure, in 0.9 we would activate it but leave it as a separate endpoint? any idea what the endpoint semantics would be? do we want to stay with {index_id}/ingest-v2?

@guilload guilload moved this from Ready to be picked to In progress in Quickwit 0.9 Jan 2, 2025
@guilload guilload assigned guilload and unassigned rdettai Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: In progress
Development

No branches or pull requests

3 participants