Improvements to Administering Collections #2720
Replies: 9 comments 22 replies
-
|
We were planning to add error log information on the index response model object if available. Editing indexes and attribute hasn't been a priority so far, but definitely something we can look into. |
Beta Was this translation helpful? Give feedback.
-
|
Another thing I'd like to bring up is the requirement to have an exact matching index for an API call with queries. Suppose I have an app that lists shirts and I want to let users filter by type, color, and/or size. I would need to create 6 indexes to cover all the combinations of filters they would provide. N! indexes would be annoying to create. |
Beta Was this translation helpful? Give feedback.
-
|
There is no straightforward way to update an existing attribute, imagine a case you want to change the attribute type from a string to an email type. Currently, you will have to delete the attribute and recreate it with the preferred type. My fear is what if this is in production and you happened to delete that attribute will the values assigned to the attribute be deleted as well? |
Beta Was this translation helpful? Give feedback.
-
|
Guys we are running an Appwrite solution in production - seeing the updating of attributes just hanging here, with the How is this not one of the top priorities? There isn't even an officially supported to way to circumvent this issue. Not being able to edit an attribute is something that is a non-negotiable for a production solution. We have for example a situation where a FK should now be I want to clarify, I'm very grateful for Appwrite as it saved a lot of time in getting a solution up and running. |
Beta Was this translation helpful? Give feedback.
-
|
For anyone on hold with this, waiting for a solution from appwrite team, I am scripting attribute update in this way (using Python SDK). It lacks any control about data integrity, data type (eg: should check if old attr is the same type of new attr)...and results check. |
Beta Was this translation helpful? Give feedback.
-
|
Adding my comment here. |
Beta Was this translation helpful? Give feedback.
-
|
bump ... any progess on this? |
Beta Was this translation helpful? Give feedback.
-
|
Closing since, as of 1.3, indexes are no longer required and there have been improvements to updating attributes. |
Beta Was this translation helpful? Give feedback.
-
Me too |
Beta Was this translation helpful? Give feedback.


Uh oh!
There was an error while loading. Please reload this page.
-
The database changes as part of 0.12 have been great and I definitely see a lot of flexibility and potential with the new queries. One thing that has become much more burdensome has been managing collections.
One hurdle is with creating indexes (and sometimes attributes). If an index or attribute fails to create successfully, there's no information provided via the UI about what was wrong. You would have to look at the appwrite-worker-database logs to see what's wrong. This is going to be a major problem for cloud if people don't have access to the docker logs.
Another big challenge is that attributes (and indexes) can't be modified. Instead, they must be deleted and recreated. This is a huge problem for apps in production with a large amount of data because it would be really difficult to try and export all the data, delete the attribute, create a new attribute, and reimport all the data while trying to reduce downtime.
Are there any plans to address these?
Beta Was this translation helpful? Give feedback.
All reactions