What's Changed

1. RESTful Endpoint Names and Swagger Grouping We have made significant changes to our endpoint naming conventions, following RESTful principles. Additionally, we have organized the endpoints into logical sections within our Swagger documentation for easier navigation and understanding.

2. MongoDB Collection Name Changes We have updated the names of several MongoDB collections. Here are the collection name changes:

• nl_query_response :arrow_right: nl_query_responses
• nl_question :arrow_right: nl_questions
• database_connection :arrow_right: database_connections
• table_schema_detail :arrow_right: table_descriptions

3. Migration to db_connection_id for MongoDB Collections Previously, we used a db_alias field to relate MongoDB collections. In this release, we have transitioned to using a new field called db_connection_id to establish relationships between collections.

4. Renamed Core Methods for Code Clarity To improve the clarity of our codebase, we have renamed several core methods.

5. Migration Script from v0.0.1 to v0.0.2 We understand the importance of a smooth transition between versions. This script performs the following actions:

• Adds the db_connection_id relation for all MongoDB collections.
• Renames all MongoDB collection names to align with the new naming conventions.
• Deletes the Vector store data (Pinecone or Chroma) and utilizes the golden_records collection to upload the data seamlessly.

To execute the script just run this command docker-compose exec app python3 -m dataherald.scripts.migrate_v001_to_v002

New Contributors

• @rmaroun https://github.com/Dataherald/dataherald/pull/133/files https://github.com/Dataherald/dataherald/pull/129/files
• @ishaan-jaff https://github.com/Dataherald/dataherald/pull/154
• @amoffat https://github.com/Dataherald/dataherald/issues/119
• @manugarri https://github.com/Dataherald/dataherald/issues/120
• @massivefermion https://github.com/Dataherald/dataherald/issues/127