# Neo4j-3.5 indexing improvement

**URL:** https://community.neo4j.com/t/neo4j-3-5-indexing-improvement/1098
**Category:** Cypher
**Created:** [September 5, 2018, 4:21pm UTC](https://community.neo4j.com/t/neo4j-3-5-indexing-improvement/1098 "2018-09-05T16:21:21Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![amad.fida](https://sea1.discourse-cdn.com/flex021/user_avatar/community.neo4j.com/amad.fida/32/308_2.png) [@amad.fida](https://community.neo4j.com/u/amad.fida)
#### Post date: [September 5, 2018, 4:21pm UTC](https://community.neo4j.com/t/neo4j-3-5-indexing-improvement/1098/1 "2018-09-05T16:21:21Z")

</div>

We noticed that there is a lot of work being done on improving indexing on current branch - Ww were wondering if there is any docs available on new native (gbtree) index and test some of issues with large string value (we have currently with native+lucene)?

---

<div class="post-metadata">

### Author: ![andrew\_bowman](https://sea1.discourse-cdn.com/flex021/user_avatar/community.neo4j.com/andrew_bowman/32/73_2.png) [@andrew\_bowman](https://community.neo4j.com/u/andrew_bowman)
#### Post date: [September 5, 2018, 5:59pm UTC](https://community.neo4j.com/t/neo4j-3-5-indexing-improvement/1098/2 "2018-09-05T17:59:26Z")

</div>

Hi there, there is [documentation on the behavior and limitations of the native string index here](https://neo4j.com/docs/operations-manual/current/performance/index-configuration/).

If your needs are such that you need to revert to the lucene string index, you can drop the current index and use a special procedure to force creation of the index using the older index provider:

`CALL db.createIndex(":Person(name)", "lucene+native-1.0"))`