# \[ANN\] Filesystem River for Elasticsearch 0.0.1 **URL:** \ **Category:** Elasticsearch\ **Created:** [June 19, 2012, 9:39pm UTC](https://discuss.elastic.co/t/ann-filesystem-river-for-elasticsearch-0-0-1/8160 "2012-06-19T21:39:42Z")\ **Posts on this page:** 6\ **Page:** 1
**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 19, 2012, 9:39pm UTC](https://discuss.elastic.co/t/ann-filesystem-river-for-elasticsearch-0-0-1/8160/1 "2012-06-19T21:39:42Z")
Hey All, I have just released the very first version of a new river : Filesystem river. This river helps to scan and index files from your local dir. Index is done through the excellent mapper-attachment plugin. It's the first release of this plugin, so use it with caution ! If you want to use it in a multi node context, you will have to share a network dir with the same mount point name on each server. Main site is here : [http://www.pilato.fr/fsriver/](http://www.pilato.fr/fsriver/) [http://www.pilato.fr/fsriver/](http://www.pilato.fr/fsriver/) Github here : [https://github.com/dadoonet/fsriver](https://github.com/dadoonet/fsriver) > **[dadoonet/fscrawler](https://github.com/dadoonet/fscrawler)** > > fscrawler - Elasticsearch File System Crawler (FS Crawler) It's not pushed at this time in OSS Sonatype maven repo as a jar, but you can use it as a plugin. See README on github : [https://github.com/dadoonet/fsriver/blob/master/README.textile](https://github.com/dadoonet/fsriver/blob/master/README.textile) [https://github.com/dadoonet/fsriver/blob/master/README.textile](https://github.com/dadoonet/fsriver/blob/master/README.textile) BTW, for this first version, I embedded the mapper attachment in the fsriver. It could be a bad idea. Is there any way when we define a plugin to check that another plugin (aka dependency) is already loaded in ES ? If so, I could remove the mapper attachment and only check when FSRiver starts that the mapper plugin is installed. Comments, Issues, Pull requests are welcome as usual. Hope this could help David. ---
**Author:** ![Amy](https://avatars.discourse-cdn.com/v4/letter/a/4da419/32.png) [@Amy](https://discuss.elastic.co/u/Amy)\ **Post date:** [November 16, 2012, 10:14am UTC](https://discuss.elastic.co/t/ann-filesystem-river-for-elasticsearch-0-0-1/8160/2 "2012-11-16T10:14:25Z")
I've installed the plugin. I'm trying to index my json documents directly from the filesystem using this river. The file metadata is uploaded to elasticsearch, but it doesn't upload the content, or it uploads it with an unreadable encoding. How do I use the fsriver to upload json document content? -- ---
**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:** [November 16, 2012, 11:44am UTC](https://discuss.elastic.co/t/ann-filesystem-river-for-elasticsearch-0-0-1/8160/3 "2012-11-16T11:44:00Z")
Did you follow the latest instructions? WARNING: starting from 0.0.3, you need to have the Attachment Plugin. It's not included anymore in the distribution. -- David 😉 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 16 nov. 2012 à 11:14, Amy [amyblarney@gmail.com](mailto:amyblarney@gmail.com) a écrit : > ## I've installed the plugin. I'm trying to index my json documents directly from the filesystem using this river. The file metadata is uploaded to elasticsearch, but it doesn't upload the content, or it uploads it with an unreadable encoding. How do I use the fsriver to upload json document content? -- ---
**Author:** ![Amy](https://avatars.discourse-cdn.com/v4/letter/a/4da419/32.png) [@Amy](https://discuss.elastic.co/u/Amy)\ **Post date:** [November 16, 2012, 12:03pm UTC](https://discuss.elastic.co/t/ann-filesystem-river-for-elasticsearch-0-0-1/8160/4 "2012-11-16T12:03:44Z")
Yes, I installed 0.0.2, but then just in case I installed the attachment plugin. The files content are added to the index as a string and encoded as base64. On Friday, November 16, 2012 11:44:11 AM UTC, David Pilato wrote: > Did you follow the latest instructions? > > _WARNING_: starting from 0.0.3, you need to have the Attachment Plugin[https://github.com/elasticsearch/elasticsearch-mapper-attachments](https://github.com/elasticsearch/elasticsearch-mapper-attachments). > It's not included anymore in the distribution. > > -- > David 😉 > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs > > Le 16 nov. 2012 à 11:14, Amy \<[amybl...@gmail.com](mailto:amybl...@gmail.com) \\> a écrit : > > I've installed the plugin. I'm trying to index my json documents directly > from the filesystem using this river. The file metadata is uploaded to > elasticsearch, but it doesn't upload the content, or it uploads it with an > unreadable encoding. How do I use the fsriver to upload json document > content? > > -- -- ---
**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:** [November 16, 2012, 3:57pm UTC](https://discuss.elastic.co/t/ann-filesystem-river-for-elasticsearch-0-0-1/8160/5 "2012-11-16T15:57:20Z")
Could you send me more details about your setup? Are you running on Windows, Linux, Mac? Is there any special encoding? How did you create your index, your river ? Can you send your query? Can you send also one document (direct mail me) ? Il will try to index it on my side. Thanks -- David 😉 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 16 nov. 2012 à 13:03, Amy [amyblarney@gmail.com](mailto:amyblarney@gmail.com) a écrit : > Yes, I installed 0.0.2, but then just in case I installed the attachment plugin. The files content are added to the index as a string and encoded as base64. > > On Friday, November 16, 2012 11:44:11 AM UTC, David Pilato wrote: > Did you follow the latest instructions? > > WARNING: starting from 0.0.3, you need to have the Attachment Plugin. It's not included anymore in the distribution. > > -- > David 😉 > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs > > Le 16 nov. 2012 à 11:14, Amy [amybl...@gmail.com](mailto:amybl...@gmail.com) a écrit : > > > ## I've installed the plugin. I'm trying to index my json documents directly from the filesystem using this river. The file metadata is uploaded to elasticsearch, but it doesn't upload the content, or it uploads it with an unreadable encoding. How do I use the fsriver to upload json document content? > > -- -- ---
**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, 3:03am UTC](https://discuss.elastic.co/t/ann-filesystem-river-for-elasticsearch-0-0-1/8160/6 "2017-07-06T03:03:57Z")