Skip to content

Instantly share code, notes, and snippets.

@medcl
Created March 24, 2012 16:33
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save medcl/2184894 to your computer and use it in GitHub Desktop.
Save medcl/2184894 to your computer and use it in GitHub Desktop.
{
"took": 26,
"timed_out": false,
"_shards": {
"total": 2,
"successful": 2,
"failed": 0
},
"hits": {
"total": 206,
"max_score": 1,
"hits": [
{
"_index": "elasticsearch_resources",
"_type": "site_en",
"_id": "404_template",
"_score": 1,
"_source": {
"category": "elasticsearch.org",
"snippet": " default Well, That about Wraps It Up for This Page 404p. `I refuse to prove that I exist,' says Page, `for proof denies faith, and without faith I am nothing.'p. `But,' says Man, `The Babel fish is a dead giveaway, isn't it? It could not have evolved by chance. It proves you exist, and so therefore",
"title": "Well, That about Wraps It Up for This Page",
"url": "/404_template.html",
"timestamp": "2012-03-20 16:34:58",
"content": " default Well, That about Wraps It Up for This Page 404p. `I refuse to prove that I exist,' says Page, `for proof denies faith, and without faith I am nothing.'p. `But,' says Man, `The Babel fish is a dead giveaway, isn't it? It could not have evolved by chance. It proves you exist, and so therefore, by your own arguments, you don't. QED.'p. `Oh dear,' says Page, `I hadn't thought of that,' and promptly disappears in a puff of logic.",
"tag": "404"
}
},
{
"_index": "elasticsearch_resources",
"_type": "site_en",
"_id": "guide_appendix_clients",
"_score": 1,
"_source": {
"category": "elasticsearch.org",
"snippet": " guide Clients & Integrations guideh1. Clients* \"ElasticSearch.pm\":http://github.com/clintongormley/ElasticSearch.pm: Perl client.* \"pyes\":http://github.com/aparo/pyes: Python client.* \"pyelasticsearch\":http://github.com/rhec/pyelasticsearch: Python client.* \"emelasticsearch\":http://github.com/ichve",
"title": "Clients & Integrations",
"url": "/guide/appendix/clients.html",
"timestamp": "2012-03-20 16:34:58",
"content": " guide Clients & Integrations guideh1. Clients* \"ElasticSearch.pm\":http://github.com/clintongormley/ElasticSearch.pm: Perl client.* \"pyes\":http://github.com/aparo/pyes: Python client.* \"pyelasticsearch\":http://github.com/rhec/pyelasticsearch: Python client.* \"emelasticsearch\":http://github.com/ichverstehe/emelasticsearch: elasticsearch library for eventmachine.* \"rubberband\":http://github.com/grantr/rubberband: Ruby client.* \"ruby_elasticsearch\":http://github.com/adrpac/elasticsearch: Ruby client.* \"slingshot\":https://github.com/karmi/slingshot/: Ruby API & DSL.* \"erlastic_search\":http://github.com/tsloughter/erlastic_search: Erlang client.* \"Elastica\":http://github.com/ruflin/Elastica: PHP client.* \"elasitcsearch\":http://github.com/nervetattoo/elasticsearch PHP client.* \"NEST\":https://github.com/Mpdreamz/NEST: .NET client.* \"ElasticSearch.NET\":https://github.com/medcl/ElasticSearch.Net: .NET client.h2. Integrations* \"Grails\":http://grails.org/plugin/elasticsearch: ElasticSearch Grails plugin.* \"escargot\":https://github.com/angelf/escargot: ElasticSearch connector for Rails (WIP).* \"catalyst\":http://www.catalystframework.org/calendar/2010/2: ElasticSearch and Catalyst integration.* \"djangoelasticsearch\":http://github.com/aparo/djangoelasticsearch: Django ElasticSearch Backend.* \"elasticflume\":http://github.com/tallpsmith/elasticflume: \"Flume\":http://github.com/cloudera/flume sink implementation.* \"Terrastore Search\":http://code.google.com/p/terrastore/wiki/Search_Integration: \"Terrastore\":http://code.google.com/p/terrastore/ integration module with elasticsearch.* \"Wonderdog\":https://github.com/infochimps/wonderdog: Hadoop bulk loader into elasticsearch.h2. Front Ends* \"elasticsearchhead\":https://github.com/mobz/elasticsearchhead: A web front end for an elastic search cluster.h2. Githubp. Github is a place where a lot of development is done around *elasticsearch*, here is a simple search for \"repos\":https://github.com/search?q=elasticsearch&type=Repositories.",
"tag": "guide"
}
},
{
"_index": "elasticsearch_resources",
"_type": "site_en",
"_id": "guide_index",
"_score": 1,
"_source": {
"category": "elasticsearch.org",
"snippet": " default Guide guide Introduction Concepts Reference Setup API Query Mapping Modules Index Modules River Java API Groovy API Appendix Clients & In",
"title": "Guide",
"url": "/guide/index.html",
"timestamp": "2012-03-20 16:34:58",
"content": " default Guide guide Introduction Concepts Reference Setup API Query Mapping Modules Index Modules River Java API Groovy API Appendix Clients & Integrations Building from Source ",
"tag": "guide"
}
},
{
"_index": "elasticsearch_resources",
"_type": "site_en",
"_id": "guide_reference_api_admin-cluster-hea",
"_score": 1,
"_source": {
"category": "elasticsearch.org",
"snippet": " guide Cluster Health API guidep. The cluster health API allows to get a very simple status on the health of the cluster.$ curl XGET 'http://localhost:9200/_cluster/health'p. The API can also be executed against one or more indices to get just the specified indices health:$ curl XGET 'http://localho",
"title": "Cluster Health API",
"url": "/guide/reference/api/admin-cluster-health.html",
"timestamp": "2012-03-20 16:34:58",
"content": " guide Cluster Health API guidep. The cluster health API allows to get a very simple status on the health of the cluster.$ curl XGET 'http://localhost:9200/_cluster/health'p. The API can also be executed against one or more indices to get just the specified indices health:$ curl XGET 'http://localhost:9200/_cluster/health/test1,test2'p. The cluster health is status is: @green@, @yellow@ or @red@. On the shard level, a @red@ status indicates that the specific shard is not allocated in the cluster, @yellow@ means that the primary shard is allocated but replicas are not, and @green@ means that all shards are allocated. The index level status is controlled by the worst shard status. The cluster status is controlled by the worst index status.p. One of the main benefits of the API is the ability to wait until the cluster reaches a certain health level. For example, the following Will wait till the cluster reaches the @green@ level for 50 seconds (if it reaches the @green@ status beforehand, it will return):$ curl XGET 'http://localhost:9200/_cluster/health?wait_for_status=green&timeout=50s'h1. Request Parametersp. The cluster health API accepts the following request parameters:|_. Name |_. Description ||level|Can be one of @cluster@, @indices@ or @shards@. Controls the details level of the health information returned. Defaults to @cluster@.||wait_for_status|One of @green@, @yellow@ or @red@. Will wait (until the timeout provided) until the status of the cluster changes to the one provided. By default, will not wait for any status.||wait_for_relocating_shards|A number controlling to how many relocating shards to wait for. Usually will be @0@ to indicate to wait till all relocation have happened. Defaults to not to wait.||wait_for_nodes|The request waits until the specified number @N@ of nodes is available. It also accepts @&gt=N@, @N@ and @$ curl XGET 'http://localhost:9200/_cluster/health/twitter?level=shards'",
"tag": "guide"
}
},
{
"_index": "elasticsearch_resources",
"_type": "site_en",
"_id": "guide_reference_api_admin-cluster-nodes-info",
"_score": 1,
"_source": {
"category": "elasticsearch.org",
"snippet": " guide Nodes Info API guidep. The cluster nodes info API allows to retrieve one or more (or all) of the cluster nodes information.$ curl XGET 'http://localhost:9200/_cluster/nodes'$ curl XGET 'http://localhost:9200/_cluster/nodes/nodeId1,nodeId2'p. The first command retrieves information of all the ",
"title": "Nodes Info API",
"url": "/guide/reference/api/admin-cluster-nodes-info.html",
"timestamp": "2012-03-20 16:34:58",
"content": " guide Nodes Info API guidep. The cluster nodes info API allows to retrieve one or more (or all) of the cluster nodes information.$ curl XGET 'http://localhost:9200/_cluster/nodes'$ curl XGET 'http://localhost:9200/_cluster/nodes/nodeId1,nodeId2'p. The first command retrieves information of all the nodes in the cluster. The second commands selectively retrieves nodes information of only @nodeId1@ and @nodeId2@.",
"tag": "guide"
}
},
{
"_index": "elasticsearch_resources",
"_type": "site_en",
"_id": "guide_reference_api_admin-cluster-nodes-shutdown",
"_score": 1,
"_source": {
"category": "elasticsearch.org",
"snippet": " guide Nodes Shutdown API guidep. The nodes shutdown API allows to shutdown one or more (or all) nodes in the cluster. Here is an example of shutting the @_local@ node the request is directed to:$ curl XPOST 'http://localhost:9200/_cluster/nodes/_local/_shutdown'p. Specific node(s) can be shutdown a",
"title": "Nodes Shutdown API",
"url": "/guide/reference/api/admin-cluster-nodes-shutdown.html",
"timestamp": "2012-03-20 16:34:58",
"content": " guide Nodes Shutdown API guidep. The nodes shutdown API allows to shutdown one or more (or all) nodes in the cluster. Here is an example of shutting the @_local@ node the request is directed to:$ curl XPOST 'http://localhost:9200/_cluster/nodes/_local/_shutdown'p. Specific node(s) can be shutdown as well using their respective node ids:$ curl XPOST 'http://localhost:9200/_cluster/nodes/nodeId1,nodeId2/_shutdown'p. The master (of the cluster) can also be shutdown using:$ curl XPOST 'http://localhost:9200/_cluster/nodes/_master/_shutdown'p. Finally, all nodes can be shutdown using one of the options below:$ curl XPOST 'http://localhost:9200/_shutdown'$ curl XPOST 'http://localhost:9200/_cluster/nodes/_shutdown'$ curl XPOST 'http://localhost:9200/_cluster/nodes/_all/_shutdown'h1. Delayp. By default, the shutdown will be executed after a 1 seconds delay (@1s@). The delay can be customized by setting the @delay@ parameter in a time value format. For example:$ curl XPOST 'http://localhost:9200/_cluster/nodes/_local/_shutdown?delay=10s'",
"tag": "guide"
}
},
{
"_index": "elasticsearch_resources",
"_type": "site_en",
"_id": "guide_reference_api_admin-indices-create-index",
"_score": 1,
"_source": {
"category": "elasticsearch.org",
"snippet": " guide Create Index API guidep. The create index API allows to instantiate an index. ElasticSearch provides support for multiple indices, including executing operations across several indices. Each index created can have specific settings associated with it.$ curl XPUT 'http://localhost:9200/twitter",
"title": "Create Index API",
"url": "/guide/reference/api/admin-indices-create-index.html",
"timestamp": "2012-03-20 16:34:58",
"content": " guide Create Index API guidep. The create index API allows to instantiate an index. ElasticSearch provides support for multiple indices, including executing operations across several indices. Each index created can have specific settings associated with it.$ curl XPUT 'http://localhost:9200/twitter/'$ curl XPUT 'http://localhost:9200/twitter/' d 'index : number_of_shards : 3 number_of_replicas : 2'p. The above second example curl shows how an index called @twitter@ can be created with specific settings for it using \"YAML\":http://www.yaml.org. In this case, creating an index with 3 shards, each with 2 replicas. The index settings can also defined with \"JSON\":http://www.json.org:$ curl XPUT 'http://localhost:9200/twitter/' d \\'{ settings : { index : { number_of_shards : 3, number_of_replicas : 2 } }}'or more simplified$ curl XPUT 'http://localhost:9200/twitter/' d \\'{ settings : { number_of_shards : 3, number_of_replicas : 2 }}'_Note you do not have to explicitly specify @index@ section inside @settings@ section._h1. Mappingsp. The create index API allows to provide a set of one or more mappings:curl XPOST localhost:9200/test d '{ \"settings\" : { \"number_of_shards\" : 1 }, \"mappings\" : { \"type1\" : { \"_source\" : { \"enabled\" : false }, \"properties\" : { \"field1\" : { \"type\" : \"string\", \"index\" : \"not_analyzed\" } } } }}'h1. Index Settingsp. For more information regarding all the different index level settings that can be set when creating an index, please check the \"index modules\":/guide/reference/index_modules section.",
"tag": "guide"
}
},
{
"_index": "elasticsearch_resources",
"_type": "site_en",
"_id": "guide_reference_api_admin-indices-gateway-snapsho",
"_score": 1,
"_source": {
"category": "elasticsearch.org",
"snippet": " guide Gateway Snapshot API guidep. The gateway snapshot API allows to explicitly perform a snapshot through the gateway of one or more indices (backup them). By default, each index gateway periodically snapshot changes, though it can be disabled and be controlled completely through this API.p. Note",
"title": "Gateway Snapshot API",
"url": "/guide/reference/api/admin-indices-gateway-snapshot.html",
"timestamp": "2012-03-20 16:34:58",
"content": " guide Gateway Snapshot API guidep. The gateway snapshot API allows to explicitly perform a snapshot through the gateway of one or more indices (backup them). By default, each index gateway periodically snapshot changes, though it can be disabled and be controlled completely through this API.p. Note, this API only applies when using shared storage gateway implementation, and does not apply when using the (default) local gateway.$ curl XPOST 'http://localhost:9200/twitter/_gateway/snapshot'h1. Multi Indexp. The gateway snapshot API can be applied to more than one index with a single call, or even on @_all@ the indices.$ curl XPOST 'http://localhost:9200/kimchy,elasticsearch/_gateway/snapshot'$ curl XPOST 'http://localhost:9200/_gateway/snapshot'",
"tag": "guide"
}
},
{
"_index": "elasticsearch_resources",
"_type": "site_en",
"_id": "guide_reference_api_admin-indices-get-mapping",
"_score": 1,
"_source": {
"category": "elasticsearch.org",
"snippet": " guide Get Mapping API guidep. The get mapping API allows to retrieve mapping definition of index or index/type.$ curl XGET 'http://localhost:9200/twitter/tweet/_mapping'h1. Multiple Indices and Typesp. The get mapping API can be used to get more than one index or type mapping with a single call. Ge",
"title": "Get Mapping API",
"url": "/guide/reference/api/admin-indices-get-mapping.html",
"timestamp": "2012-03-20 16:34:58",
"content": " guide Get Mapping API guidep. The get mapping API allows to retrieve mapping definition of index or index/type.$ curl XGET 'http://localhost:9200/twitter/tweet/_mapping'h1. Multiple Indices and Typesp. The get mapping API can be used to get more than one index or type mapping with a single call. General usage of the API follows the following syntax: @host:port/{index}/{type}/_mapping@ where both @{index}@ and @{type}@ can stand for commaseparated list of names. To get mappings for all indices you can use @_all@ for @{index}@. The following are some examples:$ curl XGET 'http://localhost:9200/twitter,kimchy/_mapping'$ curl XGET 'http://localhost:9200/_all/tweet,book/_mapping'p. If you want to get mappings of all indices and types then the following two examples are equivalent:$ curl XGET 'http://localhost:9200/_all/_mapping'$ curl XGET 'http://localhost:9200/_mapping'",
"tag": "guide"
}
},
{
"_index": "elasticsearch_resources",
"_type": "site_en",
"_id": "guide_reference_api_admin-indices-open-close",
"_score": 1,
"_source": {
"category": "elasticsearch.org",
"snippet": " guide Open / Close Index API guidep. The open and close index APIs allow to close an index, and later on opening it. A closed index has almost no overhead on the cluster (except for maintaining its metadata), and is blocked for read/write operations. A closed index can be opened which will then go ",
"title": "Open / Close Index API",
"url": "/guide/reference/api/admin-indices-open-close.html",
"timestamp": "2012-03-20 16:34:58",
"content": " guide Open / Close Index API guidep. The open and close index APIs allow to close an index, and later on opening it. A closed index has almost no overhead on the cluster (except for maintaining its metadata), and is blocked for read/write operations. A closed index can be opened which will then go through the normal recovery process.p. The REST endpoint is @/{index}/_close@ and @/{index}/_open@. For example:curl XPOST 'localhost:9200/my_index/_close'curl XPOST 'localhost:9200/my_index/_open'",
"tag": "guide"
}
}
]
},
"carrot2": {
"clusters": [
{
"documents": [
{
"_index": "elasticsearch_resources",
"_type": "site_en",
"_id": "guide_appendix_clients",
"_title": "Clients & Integrations",
"_summary": " guide Clients & Integrations guideh1. Clients* \"ElasticSearch.pm\":http://github.com/clintongormley/ElasticSearch.pm: Perl client.* \"pyes\":http://github.com/aparo/pyes: Python client.* \"pyelasticsearch\":http://github.com/rhec/pyelasticsearch: Python client.* \"emelasticsearch\":http://github.com/ichve",
"_url": "/guide/appendix/clients.html"
},
{
"_index": "elasticsearch_resources",
"_type": "site_en",
"_id": "guide_index",
"_title": "Guide",
"_summary": " default Guide guide Introduction Concepts Reference Setup API Query Mapping Modules Index Modules River Java API Groovy API Appendix Clients & In",
"_url": "/guide/index.html"
},
{
"_index": "elasticsearch_resources",
"_type": "site_en",
"_id": "guide_reference_api_admin-cluster-hea",
"_title": "Cluster Health API",
"_summary": " guide Cluster Health API guidep. The cluster health API allows to get a very simple status on the health of the cluster.$ curl XGET 'http://localhost:9200/_cluster/health'p. The API can also be executed against one or more indices to get just the specified indices health:$ curl XGET 'http://localho",
"_url": "/guide/reference/api/admin-cluster-health.html"
},
{
"_index": "elasticsearch_resources",
"_type": "site_en",
"_id": "guide_reference_api_admin-cluster-nodes-info",
"_title": "Nodes Info API",
"_summary": " guide Nodes Info API guidep. The cluster nodes info API allows to retrieve one or more (or all) of the cluster nodes information.$ curl XGET 'http://localhost:9200/_cluster/nodes'$ curl XGET 'http://localhost:9200/_cluster/nodes/nodeId1,nodeId2'p. The first command retrieves information of all the ",
"_url": "/guide/reference/api/admin-cluster-nodes-info.html"
},
{
"_index": "elasticsearch_resources",
"_type": "site_en",
"_id": "guide_reference_api_admin-cluster-nodes-shutdown",
"_title": "Nodes Shutdown API",
"_summary": " guide Nodes Shutdown API guidep. The nodes shutdown API allows to shutdown one or more (or all) nodes in the cluster. Here is an example of shutting the @_local@ node the request is directed to:$ curl XPOST 'http://localhost:9200/_cluster/nodes/_local/_shutdown'p. Specific node(s) can be shutdown a",
"_url": "/guide/reference/api/admin-cluster-nodes-shutdown.html"
},
{
"_index": "elasticsearch_resources",
"_type": "site_en",
"_id": "guide_reference_api_admin-indices-create-index",
"_title": "Create Index API",
"_summary": " guide Create Index API guidep. The create index API allows to instantiate an index. ElasticSearch provides support for multiple indices, including executing operations across several indices. Each index created can have specific settings associated with it.$ curl XPUT 'http://localhost:9200/twitter",
"_url": "/guide/reference/api/admin-indices-create-index.html"
},
{
"_index": "elasticsearch_resources",
"_type": "site_en",
"_id": "guide_reference_api_admin-indices-gateway-snapsho",
"_title": "Gateway Snapshot API",
"_summary": " guide Gateway Snapshot API guidep. The gateway snapshot API allows to explicitly perform a snapshot through the gateway of one or more indices (backup them). By default, each index gateway periodically snapshot changes, though it can be disabled and be controlled completely through this API.p. Note",
"_url": "/guide/reference/api/admin-indices-gateway-snapshot.html"
},
{
"_index": "elasticsearch_resources",
"_type": "site_en",
"_id": "guide_reference_api_admin-indices-get-mapping",
"_title": "Get Mapping API",
"_summary": " guide Get Mapping API guidep. The get mapping API allows to retrieve mapping definition of index or index/type.$ curl XGET 'http://localhost:9200/twitter/tweet/_mapping'h1. Multiple Indices and Typesp. The get mapping API can be used to get more than one index or type mapping with a single call. Ge",
"_url": "/guide/reference/api/admin-indices-get-mapping.html"
},
{
"_index": "elasticsearch_resources",
"_type": "site_en",
"_id": "guide_reference_api_admin-indices-open-close",
"_title": "Open / Close Index API",
"_summary": " guide Open / Close Index API guidep. The open and close index APIs allow to close an index, and later on opening it. A closed index has almost no overhead on the cluster (except for maintaining its metadata), and is blocked for read/write operations. A closed index can be opened which will then go ",
"_url": "/guide/reference/api/admin-indices-open-close.html"
}
],
"phrases": [
"Guide"
]
},
{
"documents": [
{
"_index": "elasticsearch_resources",
"_type": "site_en",
"_id": "guide_reference_api_admin-indices-create-index",
"_title": "Create Index API",
"_summary": " guide Create Index API guidep. The create index API allows to instantiate an index. ElasticSearch provides support for multiple indices, including executing operations across several indices. Each index created can have specific settings associated with it.$ curl XPUT 'http://localhost:9200/twitter",
"_url": "/guide/reference/api/admin-indices-create-index.html"
},
{
"_index": "elasticsearch_resources",
"_type": "site_en",
"_id": "guide_reference_api_admin-indices-gateway-snapsho",
"_title": "Gateway Snapshot API",
"_summary": " guide Gateway Snapshot API guidep. The gateway snapshot API allows to explicitly perform a snapshot through the gateway of one or more indices (backup them). By default, each index gateway periodically snapshot changes, though it can be disabled and be controlled completely through this API.p. Note",
"_url": "/guide/reference/api/admin-indices-gateway-snapshot.html"
},
{
"_index": "elasticsearch_resources",
"_type": "site_en",
"_id": "guide_reference_api_admin-indices-get-mapping",
"_title": "Get Mapping API",
"_summary": " guide Get Mapping API guidep. The get mapping API allows to retrieve mapping definition of index or index/type.$ curl XGET 'http://localhost:9200/twitter/tweet/_mapping'h1. Multiple Indices and Typesp. The get mapping API can be used to get more than one index or type mapping with a single call. Ge",
"_url": "/guide/reference/api/admin-indices-get-mapping.html"
},
{
"_index": "elasticsearch_resources",
"_type": "site_en",
"_id": "guide_reference_api_admin-indices-open-close",
"_title": "Open / Close Index API",
"_summary": " guide Open / Close Index API guidep. The open and close index APIs allow to close an index, and later on opening it. A closed index has almost no overhead on the cluster (except for maintaining its metadata), and is blocked for read/write operations. A closed index can be opened which will then go ",
"_url": "/guide/reference/api/admin-indices-open-close.html"
}
],
"phrases": [
"Index API Guidep"
]
},
{
"documents": [
{
"_index": "elasticsearch_resources",
"_type": "site_en",
"_id": "guide_reference_api_admin-cluster-nodes-info",
"_title": "Nodes Info API",
"_summary": " guide Nodes Info API guidep. The cluster nodes info API allows to retrieve one or more (or all) of the cluster nodes information.$ curl XGET 'http://localhost:9200/_cluster/nodes'$ curl XGET 'http://localhost:9200/_cluster/nodes/nodeId1,nodeId2'p. The first command retrieves information of all the ",
"_url": "/guide/reference/api/admin-cluster-nodes-info.html"
},
{
"_index": "elasticsearch_resources",
"_type": "site_en",
"_id": "guide_reference_api_admin-cluster-nodes-shutdown",
"_title": "Nodes Shutdown API",
"_summary": " guide Nodes Shutdown API guidep. The nodes shutdown API allows to shutdown one or more (or all) nodes in the cluster. Here is an example of shutting the @_local@ node the request is directed to:$ curl XPOST 'http://localhost:9200/_cluster/nodes/_local/_shutdown'p. Specific node(s) can be shutdown a",
"_url": "/guide/reference/api/admin-cluster-nodes-shutdown.html"
}
],
"phrases": [
"Guide Nodes"
]
},
{
"documents": [
{
"_index": "elasticsearch_resources",
"_type": "site_en",
"_id": "404_template",
"_title": "Well, That about Wraps It Up for This Page",
"_summary": " default Well, That about Wraps It Up for This Page 404p. `I refuse to prove that I exist,' says Page, `for proof denies faith, and without faith I am nothing.'p. `But,' says Man, `The Babel fish is a dead giveaway, isn't it? It could not have evolved by chance. It proves you exist, and so therefore",
"_url": "/404_template.html"
}
],
"phrases": [
"Other Topics"
]
}
],
"LingoClusteringAlgorithm.desiredClusterCountBase": 15,
"MultilingualClustering.defaultLanguage": "English",
"processing-time-total": 27,
"processing-time-algorithm": 27,
"TermDocumentMatrixReducer.factorizationQuality": "High",
"TermDocumentMatrixReducer.factorizationFactory": "class org.carrot2.matrix.factorization.LocalNonnegativeMatrixFactorizationFactory",
"TermDocumentMatrixBuilder.titleWordsBoost": 7,
"resource-lookup": "org.carrot2.util.resource.ResourceLookup@8d603e00",
"merge-resources": true
}
}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment