We have xindice 1.1.
I'm not really sure what you mean by value type, but I created the index
with the following command:
xindice add_indexer -c url -p "*...@id" -n idindex
After sending my original email I made some progress. If I create just
that index above the query for
"/DatabaseRecord[//tns:lizsno...@id='1234']]" works, but all queries for
"/DatabaseRecord[//lizsnodede...@id='1234']]" fail.
However, if I add a second index for "lizsnoded...@id" then both queries work.
Further testing shows that the first index speeds up the first query drastically and the
second index speeds up the second query drastically. So it appears this combination is
what I need.
But I don't understand why the first index a) doesn't speed up the second query
and b) breaks the second query altogether. I also do not understand why the
second query still works on my other server. I'm guessing that may be due to
the fact that I only have a few records total in that database since I wiped it.
Any insight you can provide would help me to feel more confident in the ability for Xindice to work in a production environment.
Thank you
Liz
Natalia Shilenkova wrote:
Liz,
What Xindice version do you use and what is the value type that you used for creating the index?
Natalia
On Jun 17, 2010, at 4:12 PM, Liz Glasser wrote:
Hopefully this won't be too hard to follow. Please let me know if I need to
clarify something.
I have two types of Nodes (let's call them LizsNode and LizsNodeDesc) that each
have an attribute named ID. LizsNode uses a namespace (tns).
I have had the LizsNode data around for months, but the LizNodeDesc are all new. I have
added an index defined as "*...@id" recently.
With the index defined, when use the xpath query "/DatabaseRecord[//tns:lizsno...@id='1234']]"
the node is returned correctly. But when I use the query
"/DatabaseRecord[//lizsnodede...@id='1234']]" 99.999% of the time nothing is returned.
Occasionally the right result is returned. Also if I query for /DatabaseRecord[//LizsNodeDesc]" all
those nodes are returned and I can see my ID is correct.
If I remove the index all queries return correctly, but its way too slow.
Also, I have one machine that this seemed to occur on but I deleted the entire
collection and the newly created one is fine. I cannot do this to my production
server however.
Any ideas what is causing this? I have confirmed the issue by querying via
commandline and via Java code.
Liz
