Usually customer always can use `LIMIT` clause for the same function, but sometimes application needs separate option by some reasons: 1. Various JDBC-based database viewers (like DataGrip) use that option (defined in standard [JDBC Statement](https://docs.oracle.com/javase/8/docs/api/java/sql/Statement.html#setMaxRows-int-)) to prevent OOM during client query execution 2. Emulation of TableService's old behavior to support smooth switching to QueryService without OOM risks. Original issue https://github.com/ydb-platform/ydb-java-sdk/issues/533 3. Special case with 0 to get result set meta without receiving any data. It required by tools with custom query processing like Apache Spark
Usually customer always can use
LIMITclause for the same function, but sometimes application needs separate option by some reasons: