You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I was inspired by your article on processing Common Crawl data (https://quickwit.io/blog/commoncrawl) and I'm working on a similar, smaller-scale project.
I'm having trouble with quickwit index ingest directly from my S3-compatible object store due to its instability. The import process often fails and causes data duplication upon retry.
Is it possible to generate the index and data files locally first and then upload them to the S3 store? This would help me avoid the ingestion issues.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I was inspired by your article on processing Common Crawl data (
https://quickwit.io/blog/commoncrawl
) and I'm working on a similar, smaller-scale project.I'm having trouble with
quickwit index ingest
directly from my S3-compatible object store due to its instability. The import process often fails and causes data duplication upon retry.Is it possible to generate the index and data files locally first and then upload them to the S3 store? This would help me avoid the ingestion issues.
Beta Was this translation helpful? Give feedback.
All reactions