Allow View customization through @View annotations [DATACOUCH-16] about spring-data-couchbase HOT 4 CLOSED

Michael Nitschinger commented

Here is an explanation how I think this should work.

Currently, in the repository implementation we make use of the "all" view to identify all docs and also count them (so with an optional reduce). The first step is to make this customizable, for both the view and design doc name.

So in general we should have a @View annotation which has two properties "design" and "view".

Then, one should be able to

1. override and annotate the findAll and count methods like this

@Override
@View(design = "foo", view = "bar)
Iterable<T> findAll()

2. Once this is done, I'd like to expand that concept on "dynamic finders" but this is a separate ticket. In the first step we could have something like:

@View(design = "users", view =" by_username")
findByUsername

and when we get n1ql support this can be completely dynamic like in JPA

from spring-data-couchbase.

David Harrigan commented

Hi,

I've had a go at doing #1. Seems to work okay. I'm going to tidy up the code a bit then do a PR. Feedback welcome! :-)

-=david=-

from spring-data-couchbase.

David Harrigan commented

Hi,

Pull Request #12 created.

Feedback welcome!

-=david=-

from spring-data-couchbase.

David Harrigan commented

Hi,

New Pull Request based on feedback from Oliver and Michael:

#14

-=david=-

from spring-data-couchbase.