This is not at all correct. SQL has well defined semantics that are standardized around the relational model and ACID guarantees. A nosql datastore is one that intentionally makes tradeoffs that force it to deviate from that model. The name makes sense if you understand that SQL was the first broadly adopted language that targeted the relational model.
I'm not very familiar with the systems you mention other than Presto. But if they do not provide relational guarantees then even if they have SQL-like syntax the semantics are sufficiently different for them to not be implementing a true SQL. Hence, nosql.