Complex queries through custom entities is now in Preview

[SunandanGokhroo]

Hi Everyone,

Good day!

Complex queries through custom entities is moving into Preview effective today i.e June, 26, 2023 IST.
(Please have a look at the changelog entry for more details)

Looking forward to receiving you valuable feedback!

Thank you!

[clouless]

Since this is the first public topic outside the EAP, I will post my feedback here as well:

@SunandanGokhroo Here is some more feedback from my side:

(1) I tried different indexes, and wanted to use only partition (not range) => It seems I have to use one column as range and can then use different columns as partition. Forge lint throws errors when only using partition.

(2) The docs say “indexes cannot be updated or deleted”. Fine with me, but that really seems to mean, once you deployed an entity and an index, and want to change things, it is not possible.
Meaning, you have a load of unused entities and indexes.

Let’s say, I define an index named “permission-lookup-by-user-id”.

        indexes:
          - name: 'permission-lookup-by-user-id'
            range:
              - 'userId'

When I later want to add another column to that index, I CANNOT change the index, because I will get a deployment error. I need to do this:

        indexes:
          - name: 'permission-lookup-by-user-id'
            range:
              - 'userId'
          - name: 'permission-lookup-by-user-id-v2'
            range:
              - 'userId'
            partition:
              - 'foo'

I will very fast reach the only 7 indexes per app limit!

My main question is: When will update/delete index be implemented?

The other question is: Can I only use partition (without range)?

thanks

forge storage entities indexes list -e development
┌─────────────┬──────────────────────────────────┬──────────────┬────────────────────┬────────────────┐
│ Entity name │ Index name                       │ Index status │ Partition          │ Range          │
├─────────────┼──────────────────────────────────┼──────────────┼────────────────────┼────────────────┤
│ permission  │ permission-lookup-by-group-id    │ ACTIVE       │ None               │ groupId        │
├─────────────┼──────────────────────────────────┼──────────────┼────────────────────┼────────────────┤
│ permission  │ permission-lookup-by-user-id     │ ACTIVE       │ None               │ userId         │
├─────────────┼──────────────────────────────────┼──────────────┼────────────────────┼────────────────┤
│ permission  │ permission-lookup-by-field-id    │ ACTIVE       │ None               │ fieldId        │
├─────────────┼──────────────────────────────────┼──────────────┼────────────────────┼────────────────┤
│ permission  │ permission-lookup-by-group-id-v2 │ ACTIVE       │ fieldId, contextId │ groupId        │
├─────────────┼──────────────────────────────────┼──────────────┼────────────────────┼────────────────┤
│ permission  │ by-key (default)                 │ ACTIVE       │ None               │ key (data key) │
└─────────────┴──────────────────────────────────┴──────────────┴────────────────────┴────────────────┘

And currently there is only “storage indexes list” command. I really hope you will provide a way to manually delete indexes with “storage indexes delete FOO” or something in that way

[SunandanGokhroo]

Hi @clouless thank you for reaching out and sharing the feedback, we really appreciate it. Please allow me some time to discuss these and get back to you with an update.
Thank you!