# Index River Alternate

**URL:** <https://discuss.elastic.co/t/index-river-alternate/24148>\
**Category:** Elasticsearch\
**Created:** [June 23, 2015, 7:10am UTC](https://discuss.elastic.co/t/index-river-alternate/24148 "2015-06-23T07:10:12Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![ESUser10](https://avatars.discourse-cdn.com/v4/letter/e/f4b2a3/32.png) [@ESUser10](https://discuss.elastic.co/u/ESUser10)\
**Post date:** [June 23, 2015, 7:10am UTC](https://discuss.elastic.co/t/index-river-alternate/24148/1 "2015-06-23T07:10:13Z")

</div>

Hi. In Elasticsearch 1.6 River are deprecated. I use the FS-River Plugin in ES 1.3 to indexing a filesystem.  
The Docu for ES 1.6 write that use the Java API. But I do not know how can with this api to scan a file system and write the file Meta data to my index. Or give it in ES 1.6 a another way to Index a FileSystem like C:/\* ?  
Can anyone give an answer please.

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [June 23, 2015, 7:48am UTC](https://discuss.elastic.co/t/index-river-alternate/24148/2 "2015-06-23T07:48:26Z")

</div>

If you are a Java dev, you can look at the FSRiver source code and check how it scans the filesystem.

---

<div class="post-metadata">

**Author:** ![ESUser10](https://avatars.discourse-cdn.com/v4/letter/e/f4b2a3/32.png) [@ESUser10](https://discuss.elastic.co/u/ESUser10)\
**Post date:** [June 23, 2015, 7:59am UTC](https://discuss.elastic.co/t/index-river-alternate/24148/3 "2015-06-23T07:59:24Z")

</div>

Yes i am a Java Developer. But since ES 1.6 (Rivers are deprecated) a was find a way how scan files from a file URL.  
It is this a way for ES 1.6? :

1. create a Index with Mapping
2. Scan all files ( look at the FSRiver) and write the File Meta Data to my created index

Give it in the ES Java API a Method to get all files from a File URL?

Thanks

---

<div class="post-metadata">

**Author:** ![ESUser10](https://avatars.discourse-cdn.com/v4/letter/e/f4b2a3/32.png) [@ESUser10](https://discuss.elastic.co/u/ESUser10)\
**Post date:** [June 23, 2015, 10:28am UTC](https://discuss.elastic.co/t/index-river-alternate/24148/4 "2015-06-23T10:28:57Z")

</div>

It give in next Time a alternate to FSRiver in Elasticsearch \>1.5

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [June 23, 2015, 11:58am UTC](https://discuss.elastic.co/t/index-river-alternate/24148/5 "2015-06-23T11:58:54Z")

</div>

I said that your can reuse what this plugin does but outside the context of a river.

You can look at this method which basically does part of the crawling job: [https://github.com/dadoonet/fsriver/blob/master/src/main/java/fr/pilato/elasticsearch/river/fs/river/FsRiver.java#L518](https://github.com/dadoonet/fsriver/blob/master/src/main/java/fr/pilato/elasticsearch/river/fs/river/FsRiver.java#L518)

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [June 23, 2015, 12:00pm UTC](https://discuss.elastic.co/t/index-river-alternate/24148/6 "2015-06-23T12:00:25Z")

</div>

FSRiver 1.3.1 might work with es 1.5 or 1.6. Untested though.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 12:05am UTC](https://discuss.elastic.co/t/index-river-alternate/24148/7 "2017-07-06T00:05:55Z")

</div>


