Probably not. If the includePaths doesn’t work, you’ll get an exception on startup.
Keep in mind that your using ReindexOnUpdate.SHALLOW means the document for ObjectA/ObjectB won’t be updated when the name of ObjectC changes, and the document for ObjectA won’t be updated when ObjectB#objectc changes, so it could lead to out-of-sync indexes and thus problems such as this.
If that’s not your problem, I will need a more complete reproducer to help. See here for templates to get you started.
is the solution to remove ReindexOnUpdate.SHALLOW from objectA and to add @IndexingDependency(reindexOnUpdate = ReindexOnUpdate.SHALLOW) on objectB from property objecta ? I tried everything and my problem remains !
If you want changes to ObjectC to trigger reindexing of ObjectB (and by extension, of ObjectA), Hibernate Search needs a way to retrieve the ObjectB corresponding to a given ObjectC. So if that’s the problem, then yes, you need to remove ReindexOnUpdate.SHALLOW, and introduce ObjectC#objectB to model the inverse side of the association ObjectB#objectC. It’s all explained in details in the documentation: Hibernate Search 6.1.8.Final: Reference Documentation
If that’s not your problem, then as I said above, I need a reproducer to help you. And by that I mean an actual project that compiles and a test that shows the problem, so I can debug it: