It seems so.
On Thu, Dec 10, 2015 at 2:06 PM, Bogdan Marinescu <
bogdan.marine...@awinta.com> wrote:
> So you mean to write my own script update processor which would do that ?
>
>
>
> On 12/10/2015 11:51 AM, Mikhail Khludnev wrote:
>
>> On Thu, Dec 10, 2015 at 1:26 PM, Bogdan Marinescu <
>> bogd
So you mean to write my own script update processor which would do that ?
On 12/10/2015 11:51 AM, Mikhail Khludnev wrote:
On Thu, Dec 10, 2015 at 1:26 PM, Bogdan Marinescu <
bogdan.marine...@awinta.com> wrote:
Problem is I was manually exporting data from a database and converting it
into sol
On Thu, Dec 10, 2015 at 1:26 PM, Bogdan Marinescu <
bogdan.marine...@awinta.com> wrote:
> Problem is I was manually exporting data from a database and converting it
> into sol'r docs and writing it to sol'r. No checks were performed if the
> converted doc had children or not so I can't really tell
Problem is I was manually exporting data from a database and converting
it into sol'r docs and writing it to sol'r. No checks were performed if
the converted doc had children or not so I can't really tell if I was
doing it in this order or reversed (first the parent and child and then
only the
On Thu, Dec 10, 2015 at 12:38 PM, Bogdan Marinescu <
bogdan.marine...@awinta.com> wrote:
> I'm interested in the workaround.
If you add the childless document first and afterwards the child, then
> sol'r should append the child to the already existing document (or rather
> delete the existing on
I've already implemented something similar to what you've said. Setting
the _root_ into the document and for safety double checking that I don't
have the same ID twice.
I'm interested in the workaround.
Thanks
On 12/10/2015 10:24 AM, Mikhail Khludnev wrote:
I want to fix it in scope of https
I want to fix it in scope of https://issues.apache.org/jira/browse/SOLR-5211
and hope it will be released in 5.5.
It will *copy* $UniqueKey into "_root_" aways (regardless of having a
child).
Thus we will have $UniqueKey really unique. Overriding update will work.
But deleteByID won't work out-of-t
Any suggestions about this ?
On 12/04/2015 08:26 AM, Bogdan Marinescu wrote:
Hi Mikhail,
I would expect the same behaviour as for a database. Meaning if I have
a field declared as an uniqueKey, then there should only be one
document with that key, regardless if it has a child or not.
If you
Hi Mikhail,
I would expect the same behaviour as for a database. Meaning if I have a
field declared as an uniqueKey, then there should only be one document
with that key, regardless if it has a child or not.
If you add the childless document first and afterwards the child, then
sol'r should
Hello Bogdan,
You described how it works now. That's how it was implemented. And I can
explain why it was done so.
Could you please describe the expected behavior for you?
Notice, I want to enforce nested (block) behavior always in scope of
https://issues.apache.org/jira/browse/SOLR-5211. So, the
Hi,
I have a problem with nested docs. If I create a document with id: 1 and
fieldA:sometext and then add it to sol'r, I get one doc in sol'r.
Afterwards if I add a child/nested doc to this document I additionally
get a _root_:1 to the document but the problem is I now have two
documents wit
11 matches
Mail list logo
