Re: [geomesa-users] Geomesa is not returning Entire WW data.

[Emilio Lahr-Vivaz <elahrvivaz@xxxxxxxx>]

    Hello,
    
    Interesting, I would expect unhandled exceptions in the executor
    service to at least be logged or dumped to stderr. We could catch
    exceptions and re-throw them back to the main thread (killing the
    whole scan), or just log them. Which do you think would be
    preferable?
    
    Thanks,
    
    Emilio

On 5/29/20 3:41 AM, Amit Srivastava wrote:

Hi Emilio,

It looks like we found the issue behind the partial response from Geomesa. I added multiple logs in geomesa code and found at the time of  CallTimeoutException over here [1], this [2] ExecutorService is swallowing the exception since the code is not checking exception for future. Any suggestions?

[1] https://github.com/locationtech/geomesa/blob/master/geomesa-index-api/src/main/scala/org/locationtech/geomesa/index/utils/AbstractBatchScan.scala#L144

[2] https://github.com/locationtech/geomesa/blob/master/geomesa-index-api/src/main/scala/org/locationtech/geomesa/index/utils/AbstractBatchScan.scala#L62

On Wed, Feb 26, 2020 at 10:07 AM Emilio Lahr-Vivaz <elahrvivaz@xxxxxxxx> wrote:

It depends on the indices you've created for your data. Since the primary z3 index has a date prefix, if you specify a one-sided date query like below, then it has to scan all date prefixes that come before that date. You could mitigate this by adding a geometry only index (i.e. z2) or by specifying a start date in your filter.

Thanks,

Emilio

Regards,

Amit Kumar Srivastava