ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nikolay Izhikov <nizhikov....@gmail.com>
Subject Re: [SparkDataFrame] Query Optimization. Prototype
Date Tue, 23 Jan 2018 08:39:23 GMT
Serge, thank you!
Vladimir, guys, can you take a look at another questions:


    * Can I know scale and precision of DECIMAL column?
      Example - [3]

    * Ignite have some limitation for a *distributed* join. For example, we can execute join
only for indexed columns. Example - [4].
        * Do we have documentation for all limitations of distributed join implementation?
        * How can I know whether concrete syntactically correct SQL query with join can be
executed by Ignite or not?




[3] https://gist.github.com/nizhikov/2d67ed68afd473d7251dab7d79135513
[4] https://gist.github.com/nizhikov/a4389fd78636869dd38c13920b5baf2b

В Вт, 23/01/2018 в 01:05 -0700, Serge Puchnin пишет:
> yes, the Cust function is supporting both Ignite and H2.
> 
> I've updated the documentation for next system functions:
> CASEWHEN Function, CAST, CONVERT, TABLE
> 
> https://apacheignite-sql.readme.io/docs/system-functions
> 
> 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
> 
> Also an issue was created for review current documentation:
> https://issues.apache.org/jira/browse/IGNITE-7496
> 
> --
> BR,
> Serge
> 
> 
> 
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Mime
View raw message