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

First update does not appear before being processed #542

Closed
curquiza opened this issue Mar 25, 2020 · 7 comments
Closed

First update does not appear before being processed #542

curquiza opened this issue Mar 25, 2020 · 7 comments
Labels
bug Something isn't working as expected good first issue Good for newcomers

Comments

@curquiza
Copy link
Member

curquiza commented Mar 25, 2020

I tried to add 19000 documents in one go (our movies dataset). It worked and was processed in 10-15 seconds.

However, during this 10-15 seconds, if I try to get the updates list, I get an empty list. Then, after this time, the update appears with the status processed (without passing by enqueued).

Then, I re-tried the same push in the same index, and I get the updates list. This time, I get immediately the update with the status enqueued, and then, after 0-15 seconds, the status passes to processed.

Seems like there is an issue for the first update.

Version

MeiliSearch v0.9.0

Edit

Just found out that the update does not appear with the global route GET indexes/:index_uid/updates but it does with the routes GET indexes/:index_uid/updates/:updateId !

@curquiza curquiza changed the title First updated does not appear before being processed First update does not appear before being processed Mar 25, 2020
@qdequele qdequele assigned qdequele and unassigned qdequele Mar 25, 2020
@Kerollmops Kerollmops added bug Something isn't working as expected good first issue Good for newcomers labels Mar 25, 2020
@sgummaluri
Copy link
Contributor

Hi, there!
Can I go ahead pick this up?
PS: this would be my first every open source contribution :)

@Kerollmops
Copy link
Member

Hey @sgummaluri,

Yes, go on, but be carreful I marked this issue as a good-first-issue but it doesn't mean it is an easy one :)

@sgummaluri
Copy link
Contributor

Hey @Kerollmops,

Fair enough. How do you suggest I get started with this?

@Kerollmops
Copy link
Member

It would be good if you launch the MeiliSearch server with the RUST_LOG=debug environnement variable, this way MeiliSearch will display more things when indexing documents. Once done, create an index and send the 19000 movies in it (you can find those in the dataset folder of the repository) and try to reproduce the bug.

@Kerollmops
Copy link
Member

Hey @sgummaluri,

It would be easier to have a direct conversation than using Github, you are welcome to our https://slack.meilisearch.com.

@sgummaluri
Copy link
Contributor

Hi @Kerollmops ,
Issued a PR #587 that fixes this! Do let me know if there's anything else that needs to be done on this :)

Kerollmops added a commit that referenced this issue Apr 5, 2020
…ter_indexing

Fix for 'Update Status after the first update comes up to be empty (#542)'
@Kerollmops
Copy link
Member

Closed by #587

bors bot added a commit that referenced this issue Jan 16, 2023
542: Refactor matching word r=Kerollmops a=ManyTheFish

Simplify MatchingWords API


Co-authored-by: ManyTheFish <many@meilisearch.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working as expected good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

4 participants