Hello,

I am using the new experimental feature annotation @Tikabridge.

I have an entity (parent) which can contains multiple childs. These childs are annotated in the parent entity with @IndexedEmbedded.

Also, the childs contains a String reference to a file, annotated with : @Column(name="DOC_PATH"),@Field and @TikaBridge. The reference to the parent is annotated with @ContainedIn.

When I index the parent entities (and the embedded childs), it works fine and I can search Lucene with Luke and find the indexed documents.
Although, when I try to search the parent entity with search it throws an exception. here is my code :

Query parentQuery= IInQB.keyword().
onField("reference").
andField("childs.docPath").
andField("numero").
matching(s.toLowerCase()).createQuery();

The execution throws this exception :
"org.hibernate.search.SearchException: FieldBridge class org.hibernate.search.bridge.builtin.TikaBridge does not have a objectToString method: field childs.docPath in Parent

How can I solve this problem?

Thanks!

Hi,
I'm not sure: assuming your mapping and property names are correct I would expect that to work, but I couldn't find a unit test to verify this case. Could you open a JIRA issue please [1] ? Even if it's not a bug I think we would need to add such a test. Would you like to contribute a test? I can provide you some pointers for that.

1 - https://hibernate.onjira.com/browse/HSEARCH

I have tried with a simpler model with no success.
My mapping and property names seems correct.

I can contribute with a test but have no idea where to start, so pointers are welcome!

Hi,
the most important step is to open an issue on JIRA to track the problem, where you can describe how to reproduce it, and maybe paste a nicely formatted stack trace.

Then if you want to contribute a unit test that's even better (but we still need a JIRA to not forget about it); we wrote some guidelines here:
https://community.jboss.org/wiki/ContributingToHibernateSearch

The best way to get an idea of how a test could be organized is by looking in the source code: each module has several tests and make use of helpers and utilities we wrote to simplify testing code.