Endpoint URL Mismatch in Astra DB Chat Memory Component

[aieventist]

I am using the Astra DB Chat Memory component, which automatically generates the following endpoint for my requests:

https://<database_id>-<region>.apps.astra.datastax.com/api/json/v1/namespaces/<namespace_id>/collections/<collection_id>
However, when checking the Astra DB Database documentation, the correct endpoint is:

https://<database_id>-<region>.apps.astra.datastax.com/rest/v2/namespaces/<namespace_id>/collections/<collection_id>
The difference lies in the URL path—/api/json/v1 vs /rest/v2.

I tried editing the component code to change api/json/v1 to rest/v2, but the issue persists. Does anyone know how to fix this and properly adjust the endpoint in the component code?

[dosubot[bot]]

Hey @aieventist! I'm here to help you with any bugs, questions, or contributions you have. Let's squash those bugs together!

To fix the endpoint URL mismatch in the Astra DB Chat Memory component, you need to adjust the api_endpoint input's default value from /api/json/v1 to /rest/v2. You can do this by modifying the value attribute of the SecretStrInput for api_endpoint in the component code:

SecretStrInput(
    name="api_endpoint",
    display_name="API Endpoint",
    info="API endpoint URL for the Astra DB service.",
    value="ASTRA_DB_API_ENDPOINT",  # Ensure this environment variable is set to the correct endpoint
    required=True,
)

Make sure that the environment variable ASTRA_DB_API_ENDPOINT is set to the correct endpoint URL, including the /rest/v2 path. If you are hardcoding the endpoint in the code, replace the value with the new endpoint URL directly ^[1].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[aieventist]

I’m trying to adjust the api_endpoint input's following URL:

https://<database_id>-<region>.apps.astra.datastax.com/rest/v2
However, when I check the output, the endpoint is being generated incorrectly as:
https://<database_id>-<region>.apps.astra.datastax.com/rest/v2/api/json/v1/namespaces/<namespace_id>/collections/<collection_id>

As you can see, the extra /api/json/v1 is appended automatically, which is not what I intended. How can I fix this issue and prevent the additional path from being added to the endpoint?

[dosubot[bot]]

To prevent the additional /api/json/v1 path from being appended to your endpoint, you need to locate where this path is being added in the code. It might be hardcoded or appended by a function responsible for constructing the endpoint URL.

1. Check the URL Construction Logic: Look for any function or method that constructs the endpoint URL. This could be similar to the getURL function in the frontend, which appends paths to a base URL ^[1]. If you find such a function, ensure it uses the correct base path (/rest/v2) without appending /api/json/v1.

2. Configuration Files: Verify if there are any configuration files or environment variables that might be influencing the endpoint URL construction. The BACKEND_URL environment variable or other settings in the .env.example file could be relevant ^[2].

3. Component Code: If the endpoint is being set in the component code, ensure that the api_endpoint input or any related configuration is correctly set to use /rest/v2 without additional paths. You might need to modify the code where the endpoint is defined or constructed.

By checking these areas, you should be able to identify and correct the source of the unwanted path addition.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}