Deleted document continues to get listed in Console but [DATACOUCH-48] about spring-data-couchbase

[spring-projects-issues]

Michael Nitschinger commented

Can you copy a code snippet that reproduces the issue here? Also, can you do a get() on the document and see if its actually deleted or not?

Which server version are you using?

[spring-projects-issues]

deepak vohra commented

The error level has reduced as the deleted IDs are not listed on re-testing but the count() method continues to return the document count before the delete for two consecutive runs of BlogPostService service application after the document IDs have been deleted. The count returned by the count() method is not in sync with the documents in the server.

long count = repository.count();
System.out.println("Number of blogposts: " + count);

Can you copy a code snippet that reproduces the issue here?
Same code example as in https://github.com/spring-projects/spring-data-couchbase

ApplicationContext context = new AnnotationConfigApplicationContext(ApplicationConfig.class);
BlogPostRepository repository = context.getBean(BlogPostRepository.class);

First, a minor correction: "bean" in the following statement should be replaced with "repository".
BlogPost post = bean.findOne("blogpost:my-id");

Add some blogposts to the "default" bucket.

Also, add a view "all" and a design document "blogpost".

Delete all with deleteAll().
repository.deleteAll();

Also, can you do a get() on the document and see if its actually deleted or not?
The repository.findOne on a deleted document ID returns a NullPointerException in the next run of the BlogPostService service application.

Which server version are you using?
64-bit Windows 2.1.1 Release Community Edition

[spring-projects-issues]

Michael Nitschinger commented

Jeah, that's kind of expected! It uses Stale = Update_After for the view queries (the other options would be stale=true or stale=false). I'll plan to have a param in the @View annotation where you can override this default.

Cheers,
Michael

[spring-projects-issues]

deepak vohra commented

The setStale(Stale stale) is set to Stale.FALSE

[spring-projects-issues]

Michael Nitschinger commented

How? Currently, you can't change the query params for a repository query, that way its always update_after.
Also note that writes are async and need some time to be persisted to disk and updated in the indexer

[spring-projects-issues]

Michael Nitschinger commented

so while this is expected behaviour, can you send me the stack trace of that NPE? If that NPE originates in the module, then we need to fix it with something proper

[spring-projects-issues]

Michael Nitschinger commented

This is expected behavior with views until we add the features where you can specify stale=false