Skip to content
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

AmazonBedrock Generator: no IDs in meta anymore in 2.0 #1276

Open
lambda-science opened this issue Jan 6, 2025 · 0 comments
Open

AmazonBedrock Generator: no IDs in meta anymore in 2.0 #1276

lambda-science opened this issue Jan 6, 2025 · 0 comments
Labels

Comments

@lambda-science
Copy link
Contributor

Describe the bug
2.0 Implementation of Amazon Bedrock Cat Generator removed the "ids" for the metadata of a replies from a generator. This was important for my app, is that something forgotten during implementation of the converse API or a change in Amazon own API (anwer)?

Before (<2.0):

        "meta": {
          "id": "msg_bdrk_018ZjKrcZ586g92r7dmLkCGx",
          "stop_sequence": null,
          "model": "claude-3-haiku-20240307",
          "usage": {
            "prompt_tokens": 12618,
            "completion_tokens": 231
          },
          "index": null,
          "finish_reason": null
        }

After (>=2.0):

        "meta": {
          "model": "anthropic.claude-3-haiku-20240307-v1:0",
          "index": 0,
          "finish_reason": "end_turn",
          "usage": {
            "prompt_tokens": 6026,
            "completion_tokens": 280,
            "total_tokens": 6306
          }

To Reproduce
Will maybe make snippet for it

Describe your environment (please complete the following information):

  • OS: [e.g. iOS]: Linux
  • Haystack version: 2.8
  • Integration version: 2.1.0
@lambda-science lambda-science added the bug Something isn't working label Jan 6, 2025
@julian-risch julian-risch added the P2 label Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants