Filter query/scan results about scanamo HOT 9 CLOSED

No, there isn't. At present you'd need to filter the results that were returned from a query/scan after the query to Dynamo.

I'd welcome a contribution which added support, but it's not something I'm actively working on.

from scanamo.

I was able to filter by exposing QueryRequest. If you want to filter, you provide your own QueryRequest else a new one is created, as usual. @philwills would you entertain a PR for this approach?

from scanamo.

@timchan-lumoslabs my current thinking is largely towards exposing the underlying driver classes less, so it's probably not the direction I'd want to take.

If I were to try and attempt something for this, I'd be looking to see if I could do something similar to how queries/scans can be limited https://github.com/guardian/scanamo/blob/master/src/main/scala/com/gu/scanamo/Table.scala#L198

from scanamo.

@philwills I am interested to see how to fix this issue but I am not sure to understand your proposal.
Do you mean adding a dynamo operator like filter so that you could write something like this ?

index.query('key -> "k1" and 'range >= 100 and filter('foo beginsWith "bar"))

from scanamo.

@ayoub-benali I was thinking more something like index.filter('foo beginsWith "bar").x.query('key -> "k1" and 'range >= 100), but I like you're suggested approach better, as filtering feels pretty tightly related to the querying.

from scanamo.

@philwills Could you give some pointer where to start implementing something like that ?
For example would DynamoKeyCondition.scala be good start ?

Seems like we should add case class like FieldCondition there and handle it later

from scanamo.

Yes, you'll need that, plus I think QueryableKeyCondition and the syntax implicits inhttps://github.com/guardian/scanamo/blob/master/src/main/scala/com/gu/scanamo/package.scala#L8

from scanamo.

I guess this issue can safely closed now that #102 is merged

from scanamo.

This is supported as of 0.9.3

from scanamo.