You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Taras Ledkov (JIRA)" <ji...@apache.org> on 2019/03/01 11:39:00 UTC

[jira] [Comment Edited] (IGNITE-7664) SQL: throw sane exception on unsupported SQL statements

    [ https://issues.apache.org/jira/browse/IGNITE-7664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16781594#comment-16781594 ] 

Taras Ledkov edited comment on IGNITE-7664 at 3/1/19 11:38 AM:
---------------------------------------------------------------

A bit about rows output behavior.
- TOP == LIMIT == FETCH
- but I guess OFFSET semantic is ambiguous (or hard to implement)  for Ignite and the most distributes cases.


was (Author: tledkov-gridgain):
A bit about rows output behavior.
- TOP == LIMIT == FETCH
- but I guess OFFSET semantic is ambiguous for Ignite and the most distributes cases.

> SQL: throw sane exception on unsupported SQL statements
> -------------------------------------------------------
>
>                 Key: IGNITE-7664
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7664
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Alexander Paschenko
>            Assignee: Taras Ledkov
>            Priority: Major
>              Labels: sql-stability
>             Fix For: 2.8
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Inspired by this SO issue:
> [https://stackoverflow.com/questions/48708238/ignite-database-create-schema-assertionerror]
> We should handle unsupported stuff more gracefully both in core code and drivers.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)