> On 7 Feb 2017, at 11:17, Gunnar Morling wrote:
>
> Emmanuel,
>
> In your PoC, how would a complete tree-like structure be traversed?
> It's not clear to me, who is driving StructureTraverser, i.e. which
> component will call processSubstructureInContainer() et al. when
> traversing an entire
This conversation is starting to get a bit complex, so I'll try to organize
my answers:
# Applying the same solution to HV and HSearch
@Emmanuel: right, I didn't see you were also talking about HV. I was only
considering the HSearch case.
I think I agree with you both, HV and HSearch are a bit d
Emmanuel,
In your PoC, how would a complete tree-like structure be traversed?
It's not clear to me, who is driving StructureTraverser, i.e. which
component will call processSubstructureInContainer() et al. when
traversing an entire tree.
@Yoann, maybe you can add a usage example similar to Emmanu
Your prototype is very Hibernate Search tainted. I wonder how or whether we
want it reusable across Hibernate Validator, Search and possibly more.
Have you captured somewhere the discussion about the new document builder so I
could get a better grip of what’s at bay?
Would this reverse of logic
Hi,
Did the same this week-end, and adapted your work to match the bigger
picture of what we discussed on Friday.
Basically the "StructureTraverser" is now called "ValueProcessor", because
it's not responsible for exposing the internals of a structure anymore, but
only to process a structure accor
I took the flight home to play with free form and specifically how we would
retrieve data from the free form structure.
By free-form I mean non POJO but they will have schema (not expressed here).
https://github.com/emmanuelbernard/hibernate-search/commit/0bd3fbab137bdad81bfa5b9934063792a050f537
