AgentsforBedrockRuntime.Client.retrieve(**kwargs) -> Response 'metadata' lost 'x-amz-bedrock-kb-chunk-id'

[GxWwT]

Describe the bug

AgentsforBedrockRuntime.Client.retrieve(**kwargs) -> Response 'metadata' lost 'x-amz-bedrock-kb-chunk-id'.
'x-amz-bedrock-kb-chunk-id' is important since it is a good param to remove deduplicate chunks.

Expected Behavior

AgentsforBedrockRuntime.Client.retrieve(**kwargs) -> Response 'metadata' get beck 'x-amz-bedrock-kb-chunk-id'

Current Behavior

AgentsforBedrockRuntime.Client.retrieve(**kwargs) -> Response 'metadata' lost 'x-amz-bedrock-kb-chunk-id'

Reproduction Steps

AgentsforBedrockRuntime.Client.retrieve(**kwargs) -> Response 'metadata' lost 'x-amz-bedrock-kb-chunk-id'

Possible Solution

No response

Additional Information/Context

No response

SDK version used

1.35.12

Environment details (OS name and version, etc.)

1.35.12

[tim-finnigan]

Thanks for reaching out. Can you provide more details on this issue? Here are the Boto3 commands for AgentsforBedrockRuntime: https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/bedrock-agent-runtime.html. Specifically we'd like to understand what command(s) you're using and what you are trying to do.

Please note that running these commands involves calls to the upstream service APIs: https://docs.aws.amazon.com/bedrock/latest/APIReference/API_Operations_Agents_for_Amazon_Bedrock_Runtime.html, so any issues or feature requests for the API would need to get rerouted to the service team.

[GxWwT]

bedrock_agent_runtime_client = boto3.client(service_name="bedrock-agent-runtime", config=my_config)
response = bedrock_agent_runtime_client.retrieve(...)
Example:
{'ResponseMetadata': {'RequestId': '', 'HTTPStatusCode': 200, 'HTTPHeaders': {'date': '', 'content-type': 'application/json', 'content-length': '', 'connection': 'keep-alive', 'x-amzn-requestid': ''}, 'RetryAttempts': 0}, 'retrievalResults': [{'content': {'text': ''}, 'location': {'s3Location': {'uri': 's3://'}, 'type': 'S3'}, 'metadata': {'x-amz-bedrock-kb-source-uri': 's3://', 'x-amz-bedrock-kb-chunk-id': '1%3A0%3Ag', 'x-amz-bedrock-kb-data-source-id': ''}, 'score': 0.37288174},

Now, there is no "x-amz-bedrock-kb-chunk-id"

[GxWwT]

x-amz-bedrock-kb-chunk-id is important since there is no unique id to remove deduplicate chunks.

[tim-finnigan]

Thanks for following up. We would need to reach out to the Bedrock team regarding this issue, since running the retrieve command involves a call to the Retrieve API. Before doing that could you share your debug logs (with any sensitive info redacted) by adding boto3.set_stream_logger('') to your script? That will help with the investigation.

Also can you tell us if x-amz-bedrock-kb-chunk-id is now always missing when it was previously always present? Or is it now only sometimes in the response?

[GxWwT]

I guess x-amz-bedrock-kb-chunk-id missing or not depends on the Chunking strategy of Bedrock Knowledge Base.
If Chunking strategy is Hierarchical chunking or Semantic chunking, then missing.
If Chunking strategy is No chunking or fixed chunking , then not missing.

[tim-finnigan]

@GxWwT to be clear, the SDK returns the response from the Bedrock API. Are you asking for clarification on the behavior here? Please let me know if you have a specific question for the Bedrock team. If you are requesting that the documentation be clarified, please use the Provide feedback link at the bottom of the API documentation page, and any updates will be reflected in the SDK docs.

[github-actions]

Greetings! It looks like this issue hasn’t been active in longer than five days. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one.