0

I am writing a web application and one of the things it does it to create and populate Azurite tables. I can view these tables in Azurite Storage Explorer.

However, if I:

  1. Delete a table (in Azurite Storage Explorer) that has data
  2. Recreate that table

Then the table gets recreated, with no data, but with all the original columns.

For comparison, if I create a table that I've never created before, I just get PartitionKey and RowKey, which is what I would expect.

This happens even if I create and populate the table in code. This is becoming a real problem, since the process of development has caused me to remove columns and rename columns, etc. But when I view my tables in Azurite, all those old columns are still there. There just now populated by null.

Is there a way of resolving this, other than resetting, or doing something else that would involve a whole lot of extra work? Am I missing something?

3
  • The issue likely involves retaining original columns in an Azurite table despite deletion and recreation, potentially due to metadata not reloading. Solutions include restarting the active HMaster from Ambari UI or deleting orphan blob files using HDFS commands. Commented Oct 1, 2024 at 7:27
  • This issue is likely caused by how Azurite handles table metadata, particularly with columns (properties) from previously deleted tables being "remembered" even when you recreate them. Commented Oct 1, 2024 at 7:27
  • I'm not sure how either of these comments relate to my issue, other than simply restating my problem. How do I resolve the issue? And what on earth has Ambari got to do with anything? Commented Nov 27, 2024 at 13:05

0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.