Run unknown dependency ingestion on bayesianApiFlow #200
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Currently, the unknown ingestion flow on the server backbone uses bayesianFlow. Bayesian Flow is used by the ingestion process as well. So, it is highly possible that unknown dependency ingestion gets delayed because it gets added to an already heavily populated queue.
Fixes # (issue)
To use the BayesianApiFlow that ensures that the unknown dependency ingestion is added to another dedicated queue for Api level ingestions. This will ensure faster ingestion.
Type of change