Two folder entries for the same folder

[trorbyte]

I'm trying to figure out how the folder entries are represented, in order that I can traverse them via a UI.

I note that two folder entries are created per folder - one relative to its parent and one relative to itself. Is this intentional or a defect?

"hits": [
      {
        "_index": "timemachine",
        "_type": "folder",
        "_id": "ae8f8f73818eb5f2298ccaf92e70b3",
        "_score": 1.3530767,
        "_source": {
          "encoded": "8083584abf261c9cf4d6f7d62e184e",
          "root": "c79170dd1de552758f2fb3f363a44327",
          "virtual": "/DVDProjects",
          "real": "DVDProjects"
        }
      },
      {
        "_index": "timemachine",
        "_type": "folder",
        "_id": "8083584abf261c9cf4d6f7d62e184e",
        "_score": 0.99057835,
        "_source": {
          "encoded": "c79170dd1de552758f2fb3f363a44327",
          "root": "c79170dd1de552758f2fb3f363a44327",
          "virtual": "/",
          "real": "DVDProjects"
        }
      }, 

[dadoonet]

Might be a bug indeed.

[trorbyte]

I'm using 2.2 build against a 1.7.6 elastic stack

[dadoonet]

It's better if you can use the latest SNAPSHOT but I feel like this bug will still there

[trorbyte]

I thought you were dropping elastic 1x support post the 2.2 build?

[dadoonet]

It's not officially supported anymore but it still works with 1.7. My commit just removed integration tests: b8d5b46

[trorbyte]

ok I'll see if I get the same issue with SNAPSHOT

[trorbyte]

Only one folder at present - but the job is still running

[dadoonet]

Great. Please close the issue if at the end you don't see any duplicate anymore.

[dadoonet]

I'm closing but feel free to reopen or comment if this is happening again.