Is it technically possible to name an index or a type with a URI string (containing dots, slashes, colons, ...)?
I have tried to do some curl stuff with an URL like http://localhost:9200/<urlencoded_index_uri>/<urlencoded_type_uri>/... but it didn't seem to work very well.
Are there technical issues with this kind of naming? Or is it possible to name indices and types with URIs? In that case, what would a sample Elasticsearch URL look like?
Index names must be lowercase and must not contain characters that are
problematic in file names, because they are used as directory name.
Type names are not used in the file system but to conform with index names,
they are also restricted.
I also use URIs in Elasticsearch. You can use them as field names and field
values. In field values, they can be used for linking data.
But i recommend to build URIs dynamically in the middleware where
addressing is implemented, so you can move or reassign URIs more easily,
just by changing a global config without the need to reindex or reset alias.
Is it technically possible to name an index or a type with a URI string (containing dots, slashes, colons, ...)?
I have tried to do some curl stuff with an URL like http://localhost:9200/<urlencoded_index_uri>/<urlencoded_type_uri>/... but it didn't seem to work very well.
Are there technical issues with this kind of naming? Or is it possible to name indices and types with URIs? In that case, what would a sample Elasticsearch URL look like?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.