You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Denis Magda (JIRA)" <ji...@apache.org> on 2018/01/23 20:44:00 UTC
[jira] [Updated] (IGNITE-7496) Review a SQL documentation
[ https://issues.apache.org/jira/browse/IGNITE-7496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Denis Magda updated IGNITE-7496:
--------------------------------
Fix Version/s: 2.4
> Review a SQL documentation
> ---------------------------
>
> Key: IGNITE-7496
> URL: https://issues.apache.org/jira/browse/IGNITE-7496
> Project: Ignite
> Issue Type: Bug
> Components: documentation
> Reporter: Sergey Puchnin
> Assignee: Denis Magda
> Priority: Minor
> Fix For: 2.4
>
>
> In a discussion on dev list
> http://apache-ignite-developers.2346864.n4.nabble.com/SparkDataFrame-Query-Optimization-Prototype-tt26249.html
> was noticed there are some gaps in SQL documentation.
> It's necessary to review it.
> I've added next system functions:
> CASEWHEN Function, CAST, CONVERT, TABLE
> And for my mind, next functions aren't applicable for Ignite:
> ARRAY_GET, ARRAY_LENGTH, ARRAY_CONTAINS, CSVREAD, CSVWRITE, DATABASE, DATABASE_PATH, DISK_SPACE_USED, FILE_READ, FILE_WRITE, LINK_SCHEMA, MEMORY_FREE, MEMORY_USED, LOCK_MODE, LOCK_TIMEOUT, READONLY, CURRVAL, AUTOCOMMIT, CANCEL_SESSION, IDENTITY, NEXTVAL, ROWNUM, SCHEMA, SCOPE_IDENTITY, SESSION_ID, SET, TRANSACTION_ID, TRUNCATE_VALUE, USER, H2VERSION
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)