.. _2024-01-16-catalog_key-discrepancies_release:

=================================================================================
2024-01-16 - catalog_key discrepancies
=================================================================================

Release
==================
*Status: Available*

*Type: Bug-Squash*

*Date: 2024-01-16*

Problem
==================
Currently there is a mixture of uuid() and hash(table_id) being used to create new catalog_key(s) when tiles are created

The catalog_key needs to be uniquely associated to the table_id which is the physical key of the table, catalog_key is the logical key we pass in the gui, but its really just a hash version of table_id.

Solution
==================
When we create a tile from the gui, we set the catalog_key to be the hash of the physical table_id, this prevents duplicate tiles being created with different catalog_keys (which is what was happening)

Leverage the Magic
====================================
A small tweak to the catalog endpoint to hash the table_id and persist it as the catalog_key

Last Refreshed
===========================
*Doc Refreshed: 2024-03-02*