[jira] [Created] (IGNITE-7909) Java code examples are needed for Spark Data Frames.

2018-03-10 Thread Akmal Chaudhri (JIRA)
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
  Issue Type: Improvement
  Components: spark
Affects Versions: 2.5
Reporter: Akmal Chaudhri
Assignee: Akmal Chaudhri
 Attachments: JavaIgniteCatalogExample.java, 
JavaIgniteDataFrameExample.java, JavaIgniteDataFrameWriteExample.java

Existing Scala code examples have been developed to illustrate Ignite support 
for Spark Data Frames. But Java code examples are also required. Some Java code 
has already been developed but requires further testing.



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


[GitHub] ignite pull request #3619: IGNITE-7654 Add processing for JTS Geometry

2018-03-10 Thread ivandasch
GitHub user ivandasch opened a pull request:

https://github.com/apache/ignite/pull/3619

IGNITE-7654 Add processing for JTS Geometry 

Now geometry deserializes to WKT.  Also, add Spatial JDBC Example

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ivandasch/ignite ignite-7654

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/3619.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3619


commit abb0cf03df0da97efa0701ddbaa3eb4a43b8dac0
Author: Ivan 
Date:   2018-03-10T19:38:51Z

IGNITE-7654 Add processing for jts Geometry in jdbc processor, now
geometry deserializes to WKT. Also, add Spatial JDBC Example




---


Re: [VOTE] Apache Ignite 2.4.0 RC1

2018-03-10 Thread Nikolay Izhikov
+1 (binding)

Build from source: OKStart couple of local nodes with default config - OK.

В Сб, 10/03/2018 в 11:19 +0300, Alexey Goncharuk пишет:
> +1 (binding)
> 
> Build from source: OK
> Start nodes with persistence, couple of BLT changes: OK
> 
> Ssserj, as for the persistence issue you are talking about - you are
> hitting the issue [1] which is almost finished, but did not make it to the
> 2.4 release. As the affects version is 2.1, this is not a regression, so I
> do not think this issue is a blocker for the release.
> 
> --AG
> 
> [1] https://issues.apache.org/jira/browse/IGNITE-5874
> 
> 2018-03-09 12:42 GMT+03:00 ssserj :
> 
> > +1 (in doubt)
> > But...
> > The persistent storage has bug! It can be reproduced by use case:
> > - persistent storage enabled
> > - cache store created with CreateExpirePolice for T-days
> > - outdated entities has been evicted to HDD
> > 
> > Details
> > http://apache-ignite-users.70518.x6.nabble.com/And-again-
> > Failed-to-get-page-IO-instance-page-content-is-corrupted-td20095.html
> > 
> > 
> > 
> > --
> > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> > 

signature.asc
Description: This is a digitally signed message part


Re: [VOTE] Apache Ignite 2.4.0 RC1

2018-03-10 Thread Alexey Goncharuk
+1 (binding)

Build from source: OK
Start nodes with persistence, couple of BLT changes: OK

Ssserj, as for the persistence issue you are talking about - you are
hitting the issue [1] which is almost finished, but did not make it to the
2.4 release. As the affects version is 2.1, this is not a regression, so I
do not think this issue is a blocker for the release.

--AG

[1] https://issues.apache.org/jira/browse/IGNITE-5874

2018-03-09 12:42 GMT+03:00 ssserj :

> +1 (in doubt)
> But...
> The persistent storage has bug! It can be reproduced by use case:
> - persistent storage enabled
> - cache store created with CreateExpirePolice for T-days
> - outdated entities has been evicted to HDD
>
> Details
> http://apache-ignite-users.70518.x6.nabble.com/And-again-
> Failed-to-get-page-IO-instance-page-content-is-corrupted-td20095.html
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>


Re: Data eviction/expiration from Ignite persistence

2018-03-10 Thread Alexey Goncharuk
The ticket [1] is in patch available state looks good, the only thing left
there is to transfer old entries to new storage. I hope Andrey will have
time to finish this soon, so we can target the fix for 2.5.

[1] https://issues.apache.org/jira/browse/IGNITE-5874

2018-03-09 22:51 GMT+03:00 Denis Magda :

> Val,
>
> I'd like to hear Alexey G. opinion on this? Alex, please chime in.
>
> In general, the more deployments the persistence will get the more demand
> we will see for that capability. Personally, I'd create a ticket for now
> and put it off to our backlog.
>
> --
> Denis
>
>
> On Fri, Mar 9, 2018 at 9:34 AM, Dmitriy Setrakyan 
> wrote:
>
> > On Fri, Mar 9, 2018 at 3:43 AM, Dmitry Pavlov 
> > wrote:
> >
> > > As far as I know there is no plans. Denis please correct me if I'm
> wrong.
> > >
> > > But users found these or similar bugs, it seems we need to support PDS
> > and
> > > TTL.
> > >
> >
> > We should either support it or throw a clear  exception on startup
> clearly
> > stating that it is not. I suppose, it should be the latter for now.
> > Dmitriy, any chance you can file a ticket for it?
> >
>