Databases
StackOverflow2013
Postsdbo
POError loading custom synonym file in Elasticsearch
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POError loading custom synonym file in Elasticsearch
    primarykey
    data
    text
    <p>I am using Rails, Tire and Elasticsearch on EC2 single server setup, no sharding or replication (this is the Jenkins CI Server). With a custom initializer as such:</p> <pre><code>analysis: filter: name_synonyms: type: synonym synonyms_path: &lt;%= Rails.root.join("config", "synonyms", "name_synonyms.txt") %&gt; </code></pre> <p>This file runs thru Erubis and the synonyms path is converted to something like this: </p> <pre><code>/root/workspace/project-project-0f317744a1870b4baf61bbaeb390ebe1/config/synonyms/term_synonyms.txt </code></pre> <p>When I list the files in the sever I see the following: </p> <pre><code>root@ip-XX-XXX-XX-XXX:~/workspace/project-project-0f317744a1870b4baf61bbaeb390ebe1/config/synonyms# ls -la total 20 drwxr-xr-x 2 root root 4096 Feb 11 18:25 . drwxr-xr-x 7 root root 4096 Feb 11 18:25 .. -rw-r--r-- 1 root root 3117 Feb 11 18:25 location_synonyms.txt -rw-r--r-- 1 root root 3999 Feb 11 18:25 name_synonyms.txt -rw-r--r-- 1 root root 2144 Feb 11 18:25 term_synonyms.txt </code></pre> <p>Which is exactly I am expecting, however I see the following error when running <code>rake spec</code></p> <pre><code>500 : {"error":"IndexCreationException[[test_facilities] failed to create index]; nested: FailedToResolveConfigException[Failed to resolve config path [/root/workspace/project-project-0f317744a1870b4baf61bbaeb390ebe1/config/synonyms/term_synonyms.txt], tried file path [/root/workspace/project-project-0f317744a1870b4baf61bbaeb390ebe1/config/synonyms/term_synonyms.txt], path file [/etc/elasticsearch/root/workspace/project-project-0f317744a1870b4baf61bbaeb390ebe1/config/synonyms/term_synonyms.txt], and classpath]; ","status":500} </code></pre> <p>It seems to me Elasticsearch is not capable of loading the files although the path is correct, could be a load order issue, I am really not too sure. </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USbrupm
    1. USbrupm
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. POError loading custom synonym file in Elasticsearch
      1. USAdit Saxena
      1. VTFavorite
    2. VO
      singulars
      1. POError loading custom synonym file in Elasticsearch
      1. This table or related slice is empty.
      1. VTUpMod
    1. COHow many nodes do you have in your cluster? Does this file exist on all nodes?
      singulars
      1. POError loading custom synonym file in Elasticsearch
      1. USimotov
    2. COThis is a single EC2 instance. It's the CI instance running Jenkins. So it should technically only know about itself. @imotov
      singulars
      1. POError loading custom synonym file in Elasticsearch
      1. USbrupm
    3. CO+1 same error here
      singulars
      1. POError loading custom synonym file in Elasticsearch
      1. USAdit Saxena
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload