Performance issues if we have around 5 properties with same index name

[Abdul Azeez Shaik]

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.

Kindly suggest me the best design for this.

Thanks,

Abdul

[Abdul Azeez Shaik]

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

[Peter Neubauer]

No,
I think putting several properties in the same index should be ok.

Cheers,

/peter neubauer

G: neubauer.peter
S: peter.neubauer
P: +46 704 106975
L: http://www.linkedin.com/in/neubauer
T: @peterneubauer

Neo4j 1.8 GA - http://www.dzone.com/links/neo4j_18_release_fluent_graph_literacy.html


On Thu, Oct 4, 2012 at 5:45 PM, Abdul Azeez Shaik

<azeezte...@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 <azeezte...@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.
>>
>> Kindly suggest me the best design for this.
>>
>> Thanks,
>> Abdul
>>
>

> --
>
>

[Abdul Azeez Shaik]

Thanks for the prompt response Peter. Will go ahead with the implementation

--

[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

--

[Michael Hunger]

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

--
 
 

[Wes Freeman]

Got it, thanks.

Wes

--