Thanks for the reply, Apos. Seeing as how this test is in flux I won't worry too much about it now. FWIW, I could do inclusive or exclusive ranges with Lucene.
-Scott On Aug 17, 2013, at 9:52 PM, Apostolis Giannakidis <ap.giannaki...@gmail.com> wrote: > Hello Scott, > > The issue that you just spotted is the same issue that I also > coincidentally spotted a week ago. > Keith Turner first identified the issue and documented it in Jira. Please > see GORA-66. > https://issues.apache.org/jira/browse/GORA-66 > > This is also a blocking issue for me, as it does not allow me to complete > the implementation of deleteByQuery(). Personally, I @Ignored this test > case until GORA-66 is resolved. I saw that the same was done in Accumulo > datastore. > > I hope this helps, > Apos > > > > On Sat, Aug 17, 2013 at 8:11 PM, Scott Stults < > sstu...@opensourceconnections.com> wrote: > >> All, >> >> I'm having a little trouble getting my head around deleteByQuery(). The >> javadoc in the interface indicates that any object that matches the query >> should get deleted. The unit test >> DataStoreTestUtil.testDeleteByQueryFields() expects the object to still >> exist with the queried-for fields cleared. To me it seems like the test is >> for an update, rather than a delete. >> >> Are my semantics all mixed up? >> >> >> Thanks, >> -Scott >>
