-
Notifications
You must be signed in to change notification settings - Fork 299
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
[Bug] SQL failing to save when too many tags with the same key are present (list/content too big for the key) #527
Comments
FYI @kbeaugrand if you have a chance to look into it - thanks |
Will take a look soon. |
kbeaugrand
added a commit
to kbeaugrand/kernel-memory
that referenced
this issue
Jun 1, 2024
kbeaugrand
added a commit
to kbeaugrand/kernel-memory
that referenced
this issue
Jun 1, 2024
kbeaugrand
added a commit
to kbeaugrand/kernel-memory
that referenced
this issue
Jun 1, 2024
kbeaugrand
added a commit
to kbeaugrand/kernel-memory
that referenced
this issue
Jun 1, 2024
kbeaugrand
added a commit
to kbeaugrand/kernel-memory
that referenced
this issue
Jun 1, 2024
kbeaugrand
added a commit
to kbeaugrand/kernel-memory
that referenced
this issue
Jun 1, 2024
kbeaugrand
added a commit
to kbeaugrand/kernel-memory
that referenced
this issue
Jun 1, 2024
kbeaugrand
added a commit
to kbeaugrand/kernel-memory
that referenced
this issue
Jun 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Context / Scenario
We are ingesting Documents to KM, we store them to SQL -> SQL content is displayed in UI for users.
In case our Document has too many Keywords (too many tags with the same key), SQL fails on save_records with confusing error: JSON text is not properly formatted. Unexpected character '"' is found at position 245. (always around this 250 position mark)
If all Keywords are batched by 10, eg keys are Keyword1, Keyword2, ... it works, but separating is not really a valid option for us.
example code that results in stuck document:
in KM, this flow is used:
ConfigureIngestionMemoryDb ->
What happened?
SQL should process it properly without crash. (when omitting SQL, KM is able to properly store the tags in search service without crashing)
Importance
a fix would make my life easier
Platform, Language, Versions
C#, Azure SQL Instance, version: Microsoft.KernelMemory.MemoryDb.SQLServer and Core - 0.61.240524.1
Relevant log output
The text was updated successfully, but these errors were encountered: