Unassigned issue IGNITE-12174

[j...@nschaefer.net]

Hi,

I have opened a bug issue some time ago about a NullPointerException  
thrown if geospatial indexing is used together with durable memory:

https://issues.apache.org/jira/browse/IGNITE-12174

Even though I provided a minimal reproducing code example the issue  
was not assigned or reviewed to confirm whether we have a bug here or  
whether I did something wrong putting together my Ignite config.

I tried to find the root cause by myself but got lost in the Ignite  
code base that is still mostly unknown to me. ;-)

Can you please tell me what I can do to get the bug reviewed/confirmed/fixed?

The bug could also be relevant for the upcoming 2.8 release.

Thank you very much,

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

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

[Alexei Scherbakov <al...@gmail.com>]

Hi Jan.

Lucene and spatial indexes do not support persistence.
This is known limitation which would probably be addressed in the future
releases.

пн, 30 сент. 2019 г. в 13:23, <j...@nschaefer.net>:

> Hi,
>
> I have opened a bug issue some time ago about a NullPointerException
> thrown if geospatial indexing is used together with durable memory:
>
> https://issues.apache.org/jira/browse/IGNITE-12174
>
> Even though I provided a minimal reproducing code example the issue
> was not assigned or reviewed to confirm whether we have a bug here or
> whether I did something wrong putting together my Ignite config.
>
> I tried to find the root cause by myself but got lost in the Ignite
> code base that is still mostly unknown to me. ;-)
>
> Can you please tell me what I can do to get the bug
> reviewed/confirmed/fixed?
>
> The bug could also be relevant for the upcoming 2.8 release.
>
> Thank you very much,
>
> Jan
>
>

-- 

Best regards,
Alexei Scherbakov