I need a few pointers with some (no doubt) very basic questions:
Using the Java API the best approach seems to be using NodeBuilder,
and closing this node on shutdown. In a web application does shutdown
mean the shutdown of the web application (which means NodeBuilders
node is thread-safe) or does shutdown mean the end of the request-
response lifecycle? What is the best way to manage this.
I really like the multi-tenancy feature indicated in the product
docs. However, looking at the examples, the multitenancy would allow
for (simplified for clarity):
I have a basic object model design that follows the hierarchy of:
Account -> Profile -> Device
This means that an Account (tenant) has 1 or more Profiles which each
have 0 or more Devices.
If I wanted to be able to do a text search on, say, "Acme" and find
all devices where a field of a Device or a field of the Device's
Profile has the word "Acme" in it, how would I structure my indexes?
Looking at the examples I put above, tenant would be the account, but
would foo be 'profile' or 'device', or do I do both? ie /account1/
profile and account1/device? Probably too many questions and not
- Following on from 2, how would I structure the JSON that I submit
to index a set of Devices to satisfy such a search? Do I first index
the Profiles then index the Devices with the id of its Profile in its
document? But by doing that, I don't see that searching on Acme would
return only 'device' types, which is what I want.