Would there be any performance issues if we there is same index name for
multiple(around 4-6) properties.
As user can provide option from any of the five options available for him,
i am planning to achieve this by have same index name.
Other way of doing this is, using Index for few and WHERE clause for few of
the other properties.
Had posted this query earlier too here for having same index name for two
properties.
This requirement has been increased to around 5 properties now...so
resposting this query again to know the others opinion on this.
Thanks,
Abdul
On Thu, Oct 4, 2012 at 9:10 PM, Abdul Azeez Shaik
<azeeztechni...@gmail.com>wrote:
> Would there be any performance issues if we there is same index name for
> multiple(around 4-6) properties.
> As user can provide option from any of the five options available for him,
> i am planning to achieve this by have same index name.
> Other way of doing this is, using Index for few and WHERE clause for few
> of the other properties.
<azeeztechni...@gmail.com> wrote:
> Had posted this query earlier too here for having same index name for two
> properties.
> This requirement has been increased to around 5 properties now...so
> resposting this query again to know the others opinion on this.
> Thanks,
> Abdul
> On Thu, Oct 4, 2012 at 9:10 PM, Abdul Azeez Shaik <azeeztechni...@gmail.com>
> wrote:
>> Dear all,
>> Would there be any performance issues if we there is same index name for
>> multiple(around 4-6) properties.
>> As user can provide option from any of the five options available for him,
>> i am planning to achieve this by have same index name.
>> Other way of doing this is, using Index for few and WHERE clause for few
>> of the other properties.
> On Thu, Oct 4, 2012 at 5:45 PM, Abdul Azeez Shaik
> <azeeztechni...@gmail.com> wrote:
> > Had posted this query earlier too here for having same index name for two
> > properties.
> > This requirement has been increased to around 5 properties now...so
> > resposting this query again to know the others opinion on this.
> > Thanks,
> > Abdul
> > On Thu, Oct 4, 2012 at 9:10 PM, Abdul Azeez Shaik <
> azeeztechni...@gmail.com>
> > wrote:
> >> Dear all,
> >> Would there be any performance issues if we there is same index name for
> >> multiple(around 4-6) properties.
> >> As user can provide option from any of the five options available for
> him,
> >> i am planning to achieve this by have same index name.
> >> Other way of doing this is, using Index for few and WHERE clause for few
> >> of the other properties.
I'm curious about compound or joining index functionality, also:
Can you have an index on age and a separate index on name, and search both
at the same time efficiently (from Cypher, for example)?
Or do they need to be in the same index, and Cypher queries are effectively
limited to a single index lookup (so for multiple fields, you must have a
compound index)?
I've found only limited examples in the docs, and my lucene index knowledge
is lacking.
> On Thu, Oct 4, 2012 at 5:45 PM, Abdul Azeez Shaik
> <azeeztechni...@gmail.com> wrote:
> > Had posted this query earlier too here for having same index name for two
> > properties.
> > This requirement has been increased to around 5 properties now...so
> > resposting this query again to know the others opinion on this.
> > Thanks,
> > Abdul
> > On Thu, Oct 4, 2012 at 9:10 PM, Abdul Azeez Shaik <
> azeeztechni...@gmail.com>
> > wrote:
> >> Dear all,
> >> Would there be any performance issues if we there is same index name for
> >> multiple(around 4-6) properties.
> >> As user can provide option from any of the five options available for
> him,
> >> i am planning to achieve this by have same index name.
> >> Other way of doing this is, using Index for few and WHERE clause for few
> >> of the other properties.
> I'm curious about compound or joining index functionality, also:
> Can you have an index on age and a separate index on name, and search both at the same time efficiently (from Cypher, for example)?
> Or do they need to be in the same index, and Cypher queries are effectively limited to a single index lookup (so for multiple fields, you must have a compound index)?
> I've found only limited examples in the docs, and my lucene index knowledge is lacking.
> Thanks,
> Wes
> On Thu, Oct 4, 2012 at 12:23 PM, Peter Neubauer <peter.neuba...@neotechnology.com> wrote:
> No,
> I think putting several properties in the same index should be ok.
> On Thu, Oct 4, 2012 at 5:45 PM, Abdul Azeez Shaik
> <azeeztechni...@gmail.com> wrote:
> > Had posted this query earlier too here for having same index name for two
> > properties.
> > This requirement has been increased to around 5 properties now...so
> > resposting this query again to know the others opinion on this.
> > Thanks,
> > Abdul
> > On Thu, Oct 4, 2012 at 9:10 PM, Abdul Azeez Shaik <azeeztechni...@gmail.com>
> > wrote:
> >> Dear all,
> >> Would there be any performance issues if we there is same index name for
> >> multiple(around 4-6) properties.
> >> As user can provide option from any of the five options available for him,
> >> i am planning to achieve this by have same index name.
> >> Other way of doing this is, using Index for few and WHERE clause for few
> >> of the other properties.
michael.hun...@neotechnology.com> wrote:
> For compound index queries they have to be in the same index, just then
> use the lucene key:value AND / OR key:value syntax for compound expressions.
> You can look them up in different indexes and compare the nodes for
> identity but that is a cross product over two sets and not what you want.
> HTH
> Michael
> Am 04.10.2012 um 19:26 schrieb Wes Freeman:
> I'm curious about compound or joining index functionality, also:
> Can you have an index on age and a separate index on name, and search both
> at the same time efficiently (from Cypher, for example)?
> Or do they need to be in the same index, and Cypher queries are
> effectively limited to a single index lookup (so for multiple fields, you
> must have a compound index)?
> I've found only limited examples in the docs, and my lucene index
> knowledge is lacking.
> Thanks,
> Wes
> On Thu, Oct 4, 2012 at 12:23 PM, Peter Neubauer <
> peter.neuba...@neotechnology.com> wrote:
>> No,
>> I think putting several properties in the same index should be ok.
>> On Thu, Oct 4, 2012 at 5:45 PM, Abdul Azeez Shaik
>> <azeeztechni...@gmail.com> wrote:
>> > Had posted this query earlier too here for having same index name for
>> two
>> > properties.
>> > This requirement has been increased to around 5 properties now...so
>> > resposting this query again to know the others opinion on this.
>> > Thanks,
>> > Abdul
>> > On Thu, Oct 4, 2012 at 9:10 PM, Abdul Azeez Shaik <
>> azeeztechni...@gmail.com>
>> > wrote:
>> >> Dear all,
>> >> Would there be any performance issues if we there is same index name
>> for
>> >> multiple(around 4-6) properties.
>> >> As user can provide option from any of the five options available for
>> him,
>> >> i am planning to achieve this by have same index name.
>> >> Other way of doing this is, using Index for few and WHERE clause for
>> few
>> >> of the other properties.
