[hibernate-dev] [HSEARCH] Question on TikaBridge

[Emmanuel Bernard]

Hardy,

Today the actual bridge fails during set() if the object passed is not of a specified subset of types (Blob, etc).
This means the failure happens at the first indexing usage.

Is that ok / preferable if I do these type checking at the bridge creation time - in the BridgeProvider. The only thing I cannot handle here is if the user declares the return type as Object and the runtime type happens to be an acceptable type.

It seems like a small flexibility loss and we would gain clearer error messages: if something is annotated @TikaBridge and we don’t support the type we will fail fast.

Can i make that change?