Overview | Package | Class | Use | Tree | Deprecated | Index | Help
PREV NEXT | FRAMES NO FRAMES

## Uses of Interface
org.neo4j.index.IndexHits

Packages that use IndexHits
org.neo4j.index | Provides indexing capabilities to the Neo4j graph.
org.neo4j.index.lucene | An indexing implementation using Apache Lucene as backend.
org.neo4j.remote | A tool for introspecting a running Neo4j Graph Database instance from a different process.

Uses of IndexHits in org.neo4j.index

Methods in org.neo4j.index that return IndexHits
`IndexHits<Node>` | `IndexService.getNodes(String key, Object value)` Returns all nodes indexed with `key` and `value`.
`IndexHits<Node>` | `Index.getNodesFor(Object indexKey)` Deprecated. Returns nodes indexed with `indexKey`

Uses of IndexHits in org.neo4j.index.lucene

Methods in org.neo4j.index.lucene that return IndexHits
`IndexHits<Long>` | `LuceneIndexBatchInserter.getNodes(String key, Object value)` Queries the lucene index for hits given the `key` and `value` .
`IndexHits<Node>` | `LuceneFulltextQueryIndexService.getNodes(String key, Object value)` Here the `value` is treated as a lucene query, http://lucene.apache.org/java/2_9_1/queryparsersyntax.html So if you've indexed node (1) with value "Andy Wachowski" and node (2) with "Larry Wachowski" you can expect this behaviour if you query for: "andy" --> (1) "Andy" --> (1) "wachowski" --> (1), (2) "+wachow* +larry" --> (2) "andy AND larry" --> "andy OR larry" --> (1), (2) "larry Wachowski" --> (1), (2) The default AND/OR behaviour can be changed by overriding `LuceneFulltextQueryIndexService.getDefaultQueryOperator(String, Object)`.
`IndexHits<Long>` | `LuceneIndexBatchInserterImpl.getNodes(String key, Object value)`
`IndexHits<Node>` | `LuceneReadOnlyIndexService.getNodes(String key, Object value)`
`IndexHits<Node>` | `LuceneIndexService.getNodes(String key, Object value)` Returns all nodes indexed with `key` and `value`.
`IndexHits<Node>` | `LuceneFulltextIndexService.getNodes(String key, Object value)` Since this is a "fulltext" index it changes the contract of this method slightly.
`protected IndexHits<Node>` | `LuceneIndexService.getNodes(String key, Object value, Object matching, org.apache.lucene.search.Sort sortingOrNull)` Just like `LuceneIndexService.getNodes(String, Object)`, but with sorted result.
`IndexHits<Node>` | `LuceneReadOnlyIndexService.getNodes(String key, Object value, org.apache.lucene.search.Sort sortingOrNull)` Just like `LuceneReadOnlyIndexService.getNodes(String, Object)`, but with sorted result.
`IndexHits<Node>` | `LuceneIndexService.getNodes(String key, Object value, org.apache.lucene.search.Sort sortingOrNull)` Returns hits from the index (see `LuceneIndexService.getNodes(String, Object)`).
`IndexHits<Node>` | `LuceneIndexService.getNodesExactMatch(String key, Object value)` A method for calling `LuceneIndexService.getNodes(String, Object)` using exact matching.
`IndexHits<Node>` | `LuceneFulltextIndexService.getNodesExactMatch(String key, Object value)` Does a `LuceneFulltextIndexService.getNodes(String, Object)` using exact matching, so that it for this call behaves like `LuceneIndexService`.

Uses of IndexHits in org.neo4j.remote

Methods in org.neo4j.remote that return IndexHits
`IndexHits<Node>` | `RemoteIndexService.getNodes(String key, Object value)`

Overview | Package | Class | Use | Tree | Deprecated | Index | Help
PREV NEXT | FRAMES NO FRAMES

Copyright © 2010 Neo4j. All Rights Reserved.