Improve Fetch-From-Type Warning in Log

[gramian]

ArcadeDB Version 25.1.1

Currently a repeated fetch from a non-indexed type causes a log entry like:

Attempt to scan type '%s' of total size %s %d times. This operation is very expensive, consider using an index

see: https://github.com/ArcadeData/arcadedb/blob/main/engine/src/main/java/com/arcadedb/query/sql/executor/FetchFromTypeExecutionStep.java#L117 .
This is a very useful help for a database designer, but it could still be improved by adding:

• the to-be-fetched property or bucket name. (This makes only sense if a bucket name is available and not only a number)
• the name of the database in which the to-be-fetched type is.

[lvca]

What do you mean with "the to-be-fetched property or bucket name. (This makes only sense if a bucket name is available and not only a number)"?

[gramian]

I did not check what "bucketName" holds. A readable name, ie property name or user-assigned bucket name would work.

[gramian]

I should further clarify: if a type has many properties and some properties maybe even manually named buckets, then it is very tedious to test which property or bucket causes this warning. So naming the responsible property or bucket would be most helpful.

[gramian]

LGTM.

@lvca WRT my earlier comments: I misunderstood how FetchFromTypeExecutionStep works. I know now that the property triggering the fetch is not known to this class.