- Newest
- Most votes
- Most comments
Prior to deploying an action group, would you suggest any changes to the parsing/chunking strategy?
I'm currently using a DEFAULT parsing strategy and FIXED-SIZED chunking.
My questions will involve quering data across time horizon (ie last year, last 3 months, etc.) for transaction sizes/names, etc.
Thanks
I think your issue comes from how Bedrock Knowledge base is used for you ruse-case. There is no information on the parsing and chunking strategy used. To check different results, try to access the knowledge base and disable Generate responses option. Int he configuration, change the source chunks by increasing that number so it returns more results from the VDB to be processed by the LLM.
Once you enable Generate responses again, the LLM you choose will try to generate an answer based on the sources. There is a possibility that there is more transactions not included in the chunks returned.
If you have transaction table saved somewhere that can support querying it, then try using Bedrock Agent with an action group to run the query for you against the table and return all matches.
When I increase the chunks, is there a way to save the configuration? I've found that increasing the chunk size does help retrieve more, but there's no save button (or something similar). see screenshot for reference.
Thanks
Relevant content
- Accepted Answerasked 10 months ago
- asked 4 months ago
- asked 5 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 4 months ago
- How do I troubleshoot permission errors that I get when I create a knowledge base in Amazon Bedrock?AWS OFFICIALUpdated 2 months ago
Embedding is not always the best method for large, highly structured data, especially when precise querying, aggregation, or detailed record retrieval is needed. Complex queries, such as "Find all transactions over $500 on weekends," are difficult to perform directly on embeddings. They are optimized for capturing semantic meaning and not numerical relevance. I will say run few tests and change the parameters and see if you get better outcome. This is general guidance and your use-case might find the outcome of the Knowledge base sufficient. If you find this information helpful, please accept the answer.