The DIH is strictly tree-structured. Data flows down the tree. If the
first sibling is the root entity, nothing is used from the second
sibling. This configuration is something that it the DIH should fail.
On Thu, Mar 10, 2011 at 9:14 AM, Chantal Ackermann
wrote:
> Hi Gora,
>
> thanks for making
Hi Gora,
thanks for making me read this part of the documentation again!
This processor probably cannot do what I need out of the box but I will
try to extend it to allow specifying a regular expression in its "where"
attribute.
Thanks!
Chantal
On Thu, 2011-03-10 at 17:39 +0100, Gora Mohanty wro
Hi Stefan,
thanks for your time!
No, the second entity is not reusing values from the previous one. It
just provides more fields to it, and, of course the unique identifier -
which in case of the second entity is not unique:
and her
On Thu, Mar 10, 2011 at 8:42 PM, Chantal Ackermann
wrote:
[...]
> Is this supposed to work at all? I haven't found anything so far on the
> net but I could have used the wrong keywords for searching, of course.
>
> As answer to the maybe obvious question why I'm not using a subentity:
> I thought
Hi Chantal,
i'm not sure if i understood you correctly (if at all)? Two entities,
not arranged as sub-entitiy, but using values from the previous
entity? Could you paste your dataimport & the relevant part of the
logging-output?
Regards
Stefan
On Thu, Mar 10, 2011 at 4:12 PM, Chantal Ackermann
Dear all,
in DIH, is it possible to have two sibling entities where:
- the first one is the root entity that creates the documents by
iterating over a table that has one row per document.
- the second one is executed after the completion of the first entity
iteration, and it provides more data th
