Open ankravch opened 3 years ago
I'm not sure, but it makes sense to me that ANALYZE would only analyse a normal SQL table, i.e. persistent. The error message is a bit funny though.
I am following MonetDB tutorial at https://www.monetdb.org/Documentation/ServerAdministration/DistributedQueryProcessing/DataPartitioning. And at the very bottom it says "To prepare these statistics, the user has to run the ANALYZE command over a MERGE TABLE".
The analyze command throws error for merge tables for a long time (I found doing this as back as Mar2018 release). Also the error message has been the same before my changes (why is it funny?). This can be either a documentation mistake, because the analyze command should be applied to the children tables, or we can add support for merge tables, by applying it recursively.
The error message is not straightforward, requires a second thought.
I was also thinking that translate an ANALYZE
Describe the bug ANALYZE on merge table throws 'MERGE TABLE is not persistent'
To Reproduce
Expected behavior
Software versions