Re: Unassigned issue IGNITE-12174

[j...@nschaefer.net]

Thank you for the reply.

Quoting Alexei Scherbakov <al...@gmail.com>:
> Lucene and spatial indexes do not support persistence.
> This is known limitation which would probably be addressed in the future
> releases.

I think this limitation should at least be mentioned in the  
documentation then:

https://apacheignite-sql.readme.io/docs/geospatial-support

It would be even better to handle this unsupported use case in the  
code as well instead of throwing a NullPointerException. I can add  
this check as improvement to the Ignite code if this is wanted and  
agreed. But I need a hint on what would be the right place to add this  
check in the code base.

Thanks,

Jan

Re: Unassigned issue IGNITE-12174

[Ivan Pavlukhin <vo...@gmail.com>]

Hi Jan,

You are right. I remember that we discussed to do similar for TEXT queries [1].

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

вт, 1 окт. 2019 г. в 12:07, <j...@nschaefer.net>:
>
> Thank you for the reply.
>
> Quoting Alexei Scherbakov <al...@gmail.com>:
> > Lucene and spatial indexes do not support persistence.
> > This is known limitation which would probably be addressed in the future
> > releases.
>
> I think this limitation should at least be mentioned in the
> documentation then:
>
> https://apacheignite-sql.readme.io/docs/geospatial-support
>
> It would be even better to handle this unsupported use case in the
> code as well instead of throwing a NullPointerException. I can add
> this check as improvement to the Ignite code if this is wanted and
> agreed. But I need a hint on what would be the right place to add this
> check in the code base.
>
> Thanks,
>
> Jan
>


-- 
Best regards,
Ivan Pavlukhin