Wonderful, thanks Nikolay!
--
Denis
On Fri, Apr 27, 2018 at 11:50 PM, Nikolay Izhikov
wrote:
> Hell, Denis.
>
> I've done review and merge yersteday.
>
> master commit - https://github.com/apache/ignite/commit/
> fcc4d4a357413eb4856ca5c72d301738568060e2
> 2.5 commit - https://github.com/apache/
Hell, Denis.
I've done review and merge yersteday.
master commit -
https://github.com/apache/ignite/commit/fcc4d4a357413eb4856ca5c72d301738568060e2
2.5 commit -
https://github.com/apache/ignite/commit/2679cc5a18eb00599c9f00b0f46dbcaa6352c0cb
The task is in resolved state.
В Пт, 27/04/2018 в 2
Akmal, Nikolay,
Do you have any progress on this? Let's finish with this ticket within 2.5
scope and merge it there.
--
Denis
On Thu, Apr 19, 2018 at 10:07 PM, Akmal Chaudhri <
akmal.chaud...@gridgain.com> wrote:
> Nikolay,
>
> Ok. I _think_ it should be better now, so we can try again.
>
> 1.
Nikolay,
Ok. I _think_ it should be better now, so we can try again.
1. I removed the 3 pull requests.
2. I renamed the Java code files with a "Java" prefix.
3. I created a test file for the Java code, using the existing test file
for the Scala code.
4. I updated the TestSuite with bullet #3 abov
Hello, Akmal.
1. As a first step. Let's combine all changes you want to merge into a single
pull request.
I suggest that your changes relates only to "examples" module.
2. So, when you will have one pull request, please, run "Examples" test suite
on Team City for your branch.
After that, attac
Nikolay,
The code is the same for the attached version to the ticket, as well as the
pull version. The tests are also the same as those provided for the Scala
DF examples. I have checked and they work correctly with the exception of
the path issue which I previously mentioned on the dev list.
I'm
Hello, Akmal.
I see 3 pull requests attached to the ticket [1], [2], [3].
I see 3 java files attached to the ticket, also.
Which changes you want to be reviewed and merge? Please, clarify.
Delete all unnecessary pull requests link from the ticket.
Add new examples to the tests so we can test it
If any community members have time, please review the code. Three Java
files are attached to the Jira ticket:
https://issues.apache.org/jira/browse/IGNITE-7909
The code should be functionally equivalent to the Scala Data Frames code
that was shipped in 2.4.
Data Frame documentation is here:
htt
Sincerely,
> > Dmitriy Pavlov
> >
> > -- Forwarded message -
> > From: Akmal Chaudhri (JIRA)
> > Date: вс, 11 мар. 2018 г. в 2:24
> > Subject: [jira] [Created] (IGNITE-7909) Java code
bject: [jira] [Created] (IGNITE-7909) Java code examples are needed for
> Spark Data Frames.
> To:
>
>
> Akmal Chaudhri created IGNITE-7909:
> --
>
> Summary: Java code examples are needed for Spark Data Frames.
>
for
Spark Data Frames.
To:
Akmal Chaudhri created IGNITE-7909:
--
Summary: Java code examples are needed for Spark Data Frames.
Key: IGNITE-7909
URL: https://issues.apache.org/jira/browse/IGNITE-7909
Akmal Chaudhri created IGNITE-7909:
--
Summary: Java code examples are needed for Spark Data Frames.
Key: IGNITE-7909
URL: https://issues.apache.org/jira/browse/IGNITE-7909
Project: Ignite
6/02/2018 в 07:16 +, Dmitry Pavlov пишет:
> > +1 for starting new topic from Nikolay when ' Community Meeting to
> > Introduce Ignite Spark Data Frames' is ready to be announced.
> >
> > пт, 16 февр. 2018 г. в 9:27, Denis Magda :
> >
> > > I&#x
Ok, Igniters.
I will do it in a few weeks.
I need time to prepare to the talk.
В Пт, 16/02/2018 в 07:16 +, Dmitry Pavlov пишет:
> +1 for starting new topic from Nikolay when ' Community Meeting to
> Introduce Ignite Spark Data Frames' is ready to be announced.
>
> пт
+1 for starting new topic from Nikolay when ' Community Meeting to
Introduce Ignite Spark Data Frames' is ready to be announced.
пт, 16 февр. 2018 г. в 9:27, Denis Magda :
> I'm in :)
>
> Nikolay, we can use my GoToMeeting account to host the webinar. To draw
> mor
I'm in :)
Nikolay, we can use my GoToMeeting account to host the webinar. To draw
more attention I would suggest starting a more specific thread titled like
"[RSVP] Community Meeting to Introduce Ignite Spark Data Frames". This
discussion sounds too generic, folks could
Dmitry, it's a great idea!
Nikolay, I also have the interest to get familiar with Spark Data
Frames integration.
I'd prefer webinar of the format similar to "Ignite Persistent Store
Walkthrough" by Denis Magda, which has been presented some times ago.
On Wed, Feb 14, 2018
I am definitely interested. Great idea!
On Wed, Feb 14, 2018 at 4:32 AM, Nikolay Izhikov
wrote:
> Hello, Dmitry.
>
> If other community member are also iterested in that kind of information I
> can try to do the talk.
>
> В Ср, 14/02/2018 в 10:49 +, Dmitry Pavlov пишет:
> > Hi Nikolay,
> >
>
Hello, Dmitry.
If other community member are also iterested in that kind of information I can
try to do the talk.
В Ср, 14/02/2018 в 10:49 +, Dmitry Pavlov пишет:
> Hi Nikolay,
>
> I've notices there are a number of very lively discussions on dev list about
> SparkDataFrames. But I, for ex
Hi Nikolay,
I've notices there are a number of very lively discussions on dev list
about SparkDataFrames. But I, for example, can't fully understand it
because it is not well-known code for me.
I suppose Ignite community has other members, which are not aware of recent
feature SparkDataFrame and
Agree, it is ok to merge, since we are waiting for the page replacement
(eviction) performance fix anyway.
Spark data frames is a long-awaited feature by our users, so it does make
sense to provide a complete support in 2.4.
D.
On Fri, Feb 9, 2018 at 2:55 PM, Denis Magda wrote:
> +1
>
ed.
>>> We're fixing final issues to provide stable and fast release.
>>> Merging something to 2.4 except blockers is not possible at this phase of
>>> release process.
>>>
>>> Hope, 2.5, with your changes, will be released soon :)
>>>
>>
> >
> > On Fri, Feb 9, 2018 at 7:19 AM, Nikolay Izhikov
> > wrote:
> >
> > > Hello, Igniters.
> > >
> > > Good news.
> > >
> > > IGNITE-7337 [1](Spark Data Frames: support saving a data frame in
> Ignite)
> > > are merged to master.
ng to 2.4 except blockers is not possible at this phase of
> release process.
>
> Hope, 2.5, with your changes, will be released soon :)
>
> On Fri, Feb 9, 2018 at 7:19 AM, Nikolay Izhikov
> wrote:
>
> > Hello, Igniters.
> >
> > Good news.
> >
> &
kolay Izhikov wrote:
> Hello, Igniters.
>
> Good news.
>
> IGNITE-7337 [1](Spark Data Frames: support saving a data frame in Ignite)
> are merged to master.
>
> For now we can both - read from and write to Ignite SQL table with Data
> Frame API.
> Big thanks to Valentin
Hello, Igniters.
Good news.
IGNITE-7337 [1](Spark Data Frames: support saving a data frame in Ignite) are
merged to master.
For now we can both - read from and write to Ignite SQL table with Data Frame
API.
Big thanks to Valentin Kulichenko for a quick review.
So it seems we can include this
Nikolay Izhikov created IGNITE-7655:
---
Summary: Spark Data Frames: saving data frames into Ignite needs
to be documented
Key: IGNITE-7655
URL: https://issues.apache.org/jira/browse/IGNITE-7655
nis
>
> > On Dec 29, 2017, at 1:22 PM, Valentin Kulichenko > k...@gmail.com> wrote:
> >
> > Igniters,
> >
> > Great news! We completed and merged first part of integration with
> > Spark data frames [1]. It contains implementation of Spark data
> &g
will keep in touch and thanks again for all the great work and help
> everyone.
>
> Revin
>
> From: Denis Magda
> Date: Thursday, January 4, 2018 at 12:34 PM
> To: Revin Chalil
> Cc: "dev@ignite.apache.org"
> Subject: Re: Spark data frames integration merg
Hello, guys.
Currently `getPreferredLocations` implemented in
`IgniteRDD -> IgniteAbstractRDD`.
But DataFrame implementation uses
`IgniteSQLDataFrameRDD -> IgniteSqlRDD -> IgniteAbstractRDD`
Where `->` is extension.
So, for now, getPreferredLocation doesn't implemented for a
IgniteDataFrame.
.
Revin
From: Denis Magda
Date: Thursday, January 4, 2018 at 12:34 PM
To: Revin Chalil
Cc: "dev@ignite.apache.org"
Subject: Re: Spark data frames integration merged
Revin,
As as side note, do you have a public article published or any other relevant
material that explains how Ignite
, advices and patience.
>
>Anton, thanks for ignite wisdom you share with me.
>
>Looking forward for next issues :)
>
>P.S Happy New Year for all Ignite community!
>
>В Пт, 29/12/2017 в 13:22 -0800, Valentin Kulichenko пишет:
>> Igniters,
>>
Revin,
I doubt IgniteRDD#getPrefferredLocations has any affect on data frames, but
this is an interesting point. Nikolay, as a developer of this
functionality, can you please comment on this?
-Val
On Wed, Jan 3, 2018 at 1:22 PM, Revin Chalil wrote:
> Thanks Val for the info on indexes with DF.
В Пт, 29/12/2017 в 13:22 -0800, Valentin Kulichenko пишет:
> Igniters,
>
> Great news! We completed and merged first part of integration with
> Spark data frames [1]. It contains implementation of Spark data
> source which allows to use DataFrame API
news! We completed and merged first part of integration with
> Spark data frames [1]. It contains implementation of Spark data
> source which allows to use DataFrame API to query Ignite data, as
> well as join it with other data frames originated from different
> sources.
>
>
first part of integration with Spark data
> frames [1]. It contains implementation of Spark data source which allows to
> use DataFrame API to query Ignite data, as well as join it with other data
> frames originated from different sources.
>
> Next planned steps are the followin
Denis Magda created IGNITE-7345:
---
Summary: Spark Data Frames and Ignite Documentation
Key: IGNITE-7345
URL: https://issues.apache.org/jira/browse/IGNITE-7345
Project: Ignite
Issue Type: Task
Igniters,
Great news! We completed and merged first part of integration with Spark
data frames [1]. It contains implementation of Spark data source which
allows to use DataFrame API to query Ignite data, as well as join it with
other data frames originated from different sources.
Next planned
Valentin Kulichenko created IGNITE-7337:
---
Summary: Spark Data Frames: support saving a data frame in Ignite
Key: IGNITE-7337
URL: https://issues.apache.org/jira/browse/IGNITE-7337
Project
39 matches
Mail list logo
