Replies: 1 comment
-
|
I noticed the PR 1965 was the one where the recursive The code does seem to work and also supports duplicate file names under different directory locations, so reverting to I've reverted that one change locally and ingestion is functioning in a test environment, but I haven't run a thorough test yet. I'm not sure if there was an architectural reason for removing the recursive capability. Could you shed some light on that? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I have a scenario where I am trying to ingest product documentation. I have the documentation stored in a folder tree for example
I originally moved the entire folder tree into the inputs folder assuming the tree would be ingested and the file_path would become metadata.
Unfortunately, it didn't seem to work and none of the files were ingested.
I couldn't find any documentation around how the bulk ingestion process works or if there is an alternate way of ingestion for an entire folder structure. Is there any guidance available?
Having the structure ingestion would be great, but I can understand if there arent many use cases for it and I can possibly use the breadcrumbs in the file instead for metadata.
But the other issue I have is that there are multiple files with the same name, but with different content but I have no way to of know of the conflict until after ingestion.
Is it possible to bypass the duplicate file name restriction globally?
Beta Was this translation helpful? Give feedback.
All reactions