Re: Spark+Ignite SQL syntax proposal

2017-10-08 Thread Nikolay Izhikov
Hello, Ray. I think it can be done as a second step. After DataFrame for a current Spark release would be merged. Thoughts? 07.10.2017 16:42, Ray пишет: Hi Nikolay, Could you also implement the DataFrame support for spark-2.10 module? There's some legacy spark users still using Spark 1.6, the

Re: Spark+Ignite SQL syntax proposal

2017-10-07 Thread Ray
Hi Nikolay, Could you also implement the DataFrame support for spark-2.10 module? There's some legacy spark users still using Spark 1.6, they need the DataFrame features too. Thanks -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: Spark+Ignite SQL syntax proposal

2017-10-07 Thread Ray
Hi Nikolay, Could you also implement the DataFrame support for spark-2.10 module? There's still some legacy users who still uses spark 1.6, they need DataFrame feature too. Thanks -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: Spark+Ignite SQL syntax proposal

2017-10-05 Thread Николай Ижиков
Ok. Got it. Will remove key value support from catalog. 6 окт. 2017 г. 6:34 AM пользователь "Denis Magda" написал: > I tend to agree with Val that key-value support seems excessive. My > suggestion is to consider Ignite as a SQL database for this specific > integration implementing only relevant

Re: Spark+Ignite SQL syntax proposal

2017-10-05 Thread Denis Magda
I tend to agree with Val that key-value support seems excessive. My suggestion is to consider Ignite as a SQL database for this specific integration implementing only relevant functionality. — Denis > On Oct 5, 2017, at 5:41 PM, Valentin Kulichenko > wrote: > > Nikolay, > > I don't think we

Re: Spark+Ignite SQL syntax proposal

2017-10-05 Thread Valentin Kulichenko
Nikolay, I don't think we need this, especially with this kind of syntax which is very confusing. Main use case for data frames is SQL, so let's concentrate on it. We should use Ignite's SQL engine capabilities as much as possible. If we see other use cases down the road, we can always support the

Re: Spark+Ignite SQL syntax proposal

2017-10-05 Thread Николай Ижиков
Hello, Valentin. I implemented the ability to make Spark SQL Queries for both: 1. Ignite SQL Table. Internally table described by QueryEntity with meta information about data. 2. Key-Value cache - regular Ignite cache without meta information about stored data. In the second case, we have to k

Re: Spark+Ignite SQL syntax proposal

2017-10-05 Thread Valentin Kulichenko
Nikolay, I don't understand. Why do we require to provide key and value types in SQL? What is the issue you're trying to solve with this syntax? -Val On Thu, Oct 5, 2017 at 7:05 AM, Николай Ижиков wrote: > Hello, guys. > > I’m working on IGNITE-3084 [1] “Spark Data Frames Support in Apache Ign

Spark+Ignite SQL syntax proposal

2017-10-05 Thread Николай Ижиков
Hello, guys. I’m working on IGNITE-3084 [1] “Spark Data Frames Support in Apache Ignite” and have a proposal to discuss. I want to provide a consistent way to query Ignite key-value caches from Spark SQL engine. To implement it I have to determine java class for the key and value. It required fo