Mined Opinions For API: elasticsearch

This tab contains all the opinions collected from Stack Overflow about the API. The other tabs present summaries of the opinions using different algorithms.
  • You can't have a field that contains different types of values.. details
  • If this is something you must have you can just convert all the values of this field to string.. details
  • A bit longer - ElasticSearch is not schema-less - it's dynamic.. details
  • For some fields, like CODETERM19 , I would like to have type mapping for CODETERM20 in specific format.. details
  • We can turn off dynamic type mapping by putting CODETERM16 in CODETERM17 .. details
  • For example some CODETERM1 are some time appearing as perfect integer, like CODETERM2 , but some time it appears as CODETERM3 , like CODETERM4 .. details
  • Now let's say, my first set of data is having CODETERM8 value as CODETERM9 , so type of CODETERM10 is mapped as CODETERM11 .. details
  • What I want is to extract each article and convert it to RDF/JSON (I know how to write a model) using Apache Jena, so I can have a separate document for each article, and later import them all to a index like CouchDB or Elasticsearch to perform searches.. details
  • Not sure if you know but it's possible to set all mappings during index creation and it has much more intuitive API.. details
  • thanks this is what the logs seems to tell me.. details
  • Note, that types can also be created dynamically at any time by adding a record of a new type.. details
  • In the current version of elasticsearch search (0.19.4) "YYY" is ignored and mapping is assigned to the "XXX" type.. details
  • While reading the doc, for me it says "creates a mapping called tweet within the twitter index", this means XXX is the mapping name and YYY is the type name.. details
  • If I already provided the type name in the url, why should i still provide a type name in the content?If I provide the type name in the content, why can't I just call some url like: CODESNIPPET_JAVA3 .. details
  • Thanks .. details
  • And on an index where I don't want to use any type (all documents indexed are the same kind of data), but I want to create a mapping for that index, am I supposed to handle that by creating only one type with its mapping, and always use that type (in the CouchDB river for example)?. details
  • It's not what i understand from the doc, but what I think is:- One index can have types- Types have a mappingThus we don't create a mapping like the documentation says, but we create a type, that has a mapping, or we update the type's mapping no?. details
  • Thus if there is a mapping name, there can normally be many "mappings" for an index So, in the end, XXX and YYY are/should be the same?. details
  • So when some data have CODETERM12 as CODETERM13 , like CODETERM14 , then it is throwing exception, as the type is mapped to CODETERM15 .. details
  • So if there are 20 fields in JSON, I bother for types of 4 fields, for other 16 fields if they are considered as String, I am OK with that.. details
  • But it will disable type mapping for all fields.. details
  • So when some data have CODETERM12 as CODETERM13 , like CODETERM14 , then it is throwing exception, as the type is mapped to CODETERM15 .. details
  • By default, CODETERM5 is CODETERM6 .. details
  • Confusion between mappings and types in ElasticSearch.. details
  • Sorry, I'm new to ElasticSearch.. details
  • Elasticsearch has a very good fluent JSON builder; unfortunately, as far as I can tell, it's not a module but part of the bulk of the elasticsearch codebase, so it's not easily used without elasticsearch.. details
Summaries the opinions about elasticsearch using topic modeling.
  • 0. article mapping search couchdb extract jena import rdf separate write: 3
    • A bit longer - ElasticSearch is not schema-less - it's dynamic.. details
    • We can turn off dynamic type mapping by putting index.mapper.dynamic: false in elasticsearch.yml .. details
    • What I want is to extract each article and convert it to RDF/JSON (I know how to write a model) using Apache Jena, so I can have a separate document for each article, and later import them all to a index like CouchDB or Elasticsearch to perform searches.. details
  • 1. mapping create yyy xxx doc call couchdb twitter tweet river: 11
    • You can't have a field that contains different types of values.. details
    • If this is something you must have you can just convert all the values of this field to string.. details
    • For some fields, like date , I would like to have type mapping for datetime in specific format.. details
    • Not sure if you know but it's possible to set all mappings during index creation and it has much more intuitive API.. details
    • thanks this is what the logs seems to tell me.. details
    • In the current version of elasticsearch search (0.19.4) "YYY" is ignored and mapping is assigned to the "XXX" type.. details
    • And on an index where I don't want to use any type (all documents indexed are the same kind of data), but I want to create a mapping for that index, am I supposed to handle that by creating only one type with its mapping, and always use that type (in the CouchDB river for example)?. details
    • While reading the doc, for me it says "creates a mapping called tweet within the twitter index", this means XXX is the mapping name and YYY is the type name.. details
    • Thus if there is a mapping name, there can normally be many "mappings" for an index So, in the end, XXX and YYY are/should be the same?. details
    • It's not what i understand from the doc, but what I think is:- One index can have types- Types have a mappingThus we don't create a mapping like the documentation says, but we create a type, that has a mapping, or we update the type's mapping no?. details
    • Thanks .. details
  • 2. time provide integer url content create note add dynamically record: 4
    • For example some Ids are some time appearing as perfect integer, like 123 , but some time it appears as String , like a123 .. details
    • Now let's say, my first set of data is having Id value as 123 , so type of Id is mapped as Integer .. details
    • Note, that types can also be created dynamically at any time by adding a record of a new type.. details
    • If I already provided the type name in the url, why should i still provide a type name in the content?If I provide the type name in the content, why can't I just call some url like: CODESNIPPET .. details
  • 0. mapping throw module builder codebase bulk mapper integer exception true: 7
    • So when some data have Id as String , like a123 , then it is throwing exception, as the type is mapped to Integer .. details
    • But it will disable type mapping for all fields.. details
    • So if there are 20 fields in JSON, I bother for types of 4 fields, for other 16 fields if they are considered as String, I am OK with that.. details
    • By default, index.mapper.dynamic is true .. details
    • Sorry, I'm new to ElasticSearch.. details
    • Confusion between mappings and types in ElasticSearch.. details
    • Elasticsearch has a very good fluent JSON builder; unfortunately, as far as I can tell, it's not a module but part of the bulk of the elasticsearch codebase, so it's not easily used without elasticsearch.. details
Summaries of the opinions about elasticsearch using three algorithms (Textrank, Lexrank and Luhn) adopted from extractive summarization. Each algorithm was used once for the positive opinions and once for the negative opinions.
  • If this is something you must have you can just convert all the values of this field to string .
  • If I already provided the type name in the url, why should i still provide a type name in the content?If I provide the type name in the content, why can't I just call some url like: CODESNIPPET JAVA3 .
  • What I want is to extract each article and convert it to RDF JSON (I know how to write a model) using Apache Jena, so I can have a separate document for each article, and later import them all to a index like CouchDB or Elasticsearch to perform searches .
  • For example some Ids are some time appearing as perfect integer, like 123 , but some time it appears as String , like a123 .
  • For some fields, like date , I would like to have type mapping for datetime in specific format .
  • While reading the doc, for me it says "creates a mapping called tweet within the twitter index", this means XXX is the mapping name and YYY is the type name .
  • Thus if there is a mapping name, there can normally be many "mappings" for an index So, in the end, XXX and YYY are should be the same?.
  • It's not what i understand from the doc, but what I think is: One index can have types Types have a mappingThus we don't create a mapping like the documentation says, but we create a type, that has a mapping, or we update the type's mapping no?.
  • And on an index where I don't want to use any type (all documents indexed are the same kind of data), but I want to create a mapping for that index, am I supposed to handle that by creating only one type with its mapping, and always use that type (in the CouchDB river for example)?.
  • thanks this is what the logs seems to tell me .
  • If this is something you must have you can just convert all the values of this field to string .
  • If I already provided the type name in the url, why should i still provide a type name in the content?If I provide the type name in the content, why can't I just call some url like: CODESNIPPET JAVA3 .
  • What I want is to extract each article and convert it to RDF JSON (I know how to write a model) using Apache Jena, so I can have a separate document for each article, and later import them all to a index like CouchDB or Elasticsearch to perform searches .
  • For some fields, like date , I would like to have type mapping for datetime in specific format .
  • While reading the doc, for me it says "creates a mapping called tweet within the twitter index", this means XXX is the mapping name and YYY is the type name .
  • Thus if there is a mapping name, there can normally be many "mappings" for an index So, in the end, XXX and YYY are should be the same?.
  • It's not what i understand from the doc, but what I think is: One index can have types Types have a mappingThus we don't create a mapping like the documentation says, but we create a type, that has a mapping, or we update the type's mapping no?.
  • And on an index where I don't want to use any type (all documents indexed are the same kind of data), but I want to create a mapping for that index, am I supposed to handle that by creating only one type with its mapping, and always use that type (in the CouchDB river for example)?.
  • In the current version of elasticsearch search (0 19 4) "YYY" is ignored and mapping is assigned to the "XXX" type .
  • Note, that types can also be created dynamically at any time by adding a record of a new type .
  • If this is something you must have you can just convert all the values of this field to string .
  • If I already provided the type name in the url, why should i still provide a type name in the content?If I provide the type name in the content, why can't I just call some url like: CODESNIPPET JAVA3 .
  • What I want is to extract each article and convert it to RDF JSON (I know how to write a model) using Apache Jena, so I can have a separate document for each article, and later import them all to a index like CouchDB or Elasticsearch to perform searches .
  • For example some Ids are some time appearing as perfect integer, like 123 , but some time it appears as String , like a123 .
  • Now let's say, my first set of data is having Id value as 123 , so type of Id is mapped as Integer .
  • While reading the doc, for me it says "creates a mapping called tweet within the twitter index", this means XXX is the mapping name and YYY is the type name .
  • Thus if there is a mapping name, there can normally be many "mappings" for an index So, in the end, XXX and YYY are should be the same?.
  • It's not what i understand from the doc, but what I think is: One index can have types Types have a mappingThus we don't create a mapping like the documentation says, but we create a type, that has a mapping, or we update the type's mapping no?.
  • And on an index where I don't want to use any type (all documents indexed are the same kind of data), but I want to create a mapping for that index, am I supposed to handle that by creating only one type with its mapping, and always use that type (in the CouchDB river for example)?.
  • Not sure if you know but it's possible to set all mappings during index creation and it has much more intuitive API .
  • Confusion between mappings and types in ElasticSearch .
  • Sorry, I'm new to ElasticSearch .
  • Elasticsearch has a very good fluent JSON builder; unfortunately, as far as I can tell, it's not a module but part of the bulk of the elasticsearch codebase, so it's not easily used without elasticsearch .
  • By default, index.mapper.dynamic is true .
  • So when some data have Id as String , like a123 , then it is throwing exception, as the type is mapped to Integer .
  • But it will disable type mapping for all fields .
  • So if there are 20 fields in JSON, I bother for types of 4 fields, for other 16 fields if they are considered as String, I am OK with that .
  • Confusion between mappings and types in ElasticSearch .
  • Sorry, I'm new to ElasticSearch .
  • Elasticsearch has a very good fluent JSON builder; unfortunately, as far as I can tell, it's not a module but part of the bulk of the elasticsearch codebase, so it's not easily used without elasticsearch .
  • By default, index.mapper.dynamic is true .
  • So when some data have Id as String , like a123 , then it is throwing exception, as the type is mapped to Integer .
  • But it will disable type mapping for all fields .
  • So if there are 20 fields in JSON, I bother for types of 4 fields, for other 16 fields if they are considered as String, I am OK with that .
  • Confusion between mappings and types in ElasticSearch .
  • Sorry, I'm new to ElasticSearch .
  • Elasticsearch has a very good fluent JSON builder; unfortunately, as far as I can tell, it's not a module but part of the bulk of the elasticsearch codebase, so it's not easily used without elasticsearch .
  • By default, index.mapper.dynamic is true .
  • So when some data have Id as String , like a123 , then it is throwing exception, as the type is mapped to Integer .
  • But it will disable type mapping for all fields .
  • So if there are 20 fields in JSON, I bother for types of 4 fields, for other 16 fields if they are considered as String, I am OK with that .
Summaries of the opinions about elasticsearch using Opinosis, an abstractive summarizer of opinions..
Summaries of the opinions about elasticsearch using contrastive viewpoints. Each entry contains a pair of positive and negative sentences that are most likely discussing about similar API features.
Summaries of opinions about based on specific API aspects, such as, performance, usability, etc. The 'Overview' page provides an overview of the aspects detected in the opinions. The 'Trend' page shows the distribution of polarity over time for each aspect. The 'Positive Opinions' page groups positive opinions by the detected aspects. The 'Contrastive By Aspect' page shows paris of contrastive opinions under each aspect (where found).
Onlysentiment:
  • Thanks .
  • N/A
Usability:
  • If this is something you must have you can just convert all the values of this field to string.
  • So if there are 20 fields in JSON, I bother for types of 4 fields, for other 16 fields if they are considered as String, I am OK with that.
Features:
  • We can turn off dynamic type mapping by putting CODETERM16 in CODETERM17 .
  • By default, CODETERM5 is CODETERM6 .
Bug:
  • N/A
  • So when some data have CODETERM12 as CODETERM13 , like CODETERM14 , then it is throwing exception, as the type is mapped to CODETERM15 .
  • Onlysentiment: 1
    1. general: 1
  • Features: 3
    1. general: 3
      • We can turn off dynamic type mapping by putting CODETERM16 in CODETERM17 .. details
      • While reading the doc, for me it says "creates a mapping called tweet within the twitter index", this means XXX is the mapping name and YYY is the type name.. details
      • If I already provided the type name in the url, why should i still provide a type name in the content?If I provide the type name in the content, why can't I just call some url like: CODESNIPPET_JAVA3 .. details
  • Usability: 14
    1. mapping: 5
      • For some fields, like CODETERM19 , I would like to have type mapping for CODETERM20 in specific format.. details
      • In the current version of elasticsearch search (0.19.4) "YYY" is ignored and mapping is assigned to the "XXX" type.. details
      • And on an index where I don't want to use any type (all documents indexed are the same kind of data), but I want to create a mapping for that index, am I supposed to handle that by creating only one type with its mapping, and always use that type (in the CouchDB river for example)?. details
      • It's not what i understand from the doc, but what I think is:- One index can have types- Types have a mappingThus we don't create a mapping like the documentation says, but we create a type, that has a mapping, or we update the type's mapping no?. details
      • Thus if there is a mapping name, there can normally be many "mappings" for an index So, in the end, XXX and YYY are/should be the same?. details
    2. general: 4
      • If this is something you must have you can just convert all the values of this field to string.. details
      • A bit longer - ElasticSearch is not schema-less - it's dynamic.. details
      • Not sure if you know but it's possible to set all mappings during index creation and it has much more intuitive API.. details
      • thanks this is what the logs seems to tell me.. details
    3. time: 1
      • For example some CODETERM1 are some time appearing as perfect integer, like CODETERM2 , but some time it appears as CODETERM3 , like CODETERM4 .. details
    4. import: 1
      • What I want is to extract each article and convert it to RDF/JSON (I know how to write a model) using Apache Jena, so I can have a separate document for each article, and later import them all to a index like CouchDB or Elasticsearch to perform searches.. details
    5. data: 1
      • Now let's say, my first set of data is having CODETERM8 value as CODETERM9 , so type of CODETERM10 is mapped as CODETERM11 .. details
    6. types: 2
      • You can't have a field that contains different types of values.. details
      • Note, that types can also be created dynamically at any time by adding a record of a new type.. details
  • Features: 2
    1. general: 2
      • By default, CODETERM5 is CODETERM6 .. details
      • Sorry, I'm new to ElasticSearch.. details
  • Bug: 1
    1. general: 1
      • So when some data have CODETERM12 as CODETERM13 , like CODETERM14 , then it is throwing exception, as the type is mapped to CODETERM15 .. details
  • Usability: 5
    1. general: 5
      • So if there are 20 fields in JSON, I bother for types of 4 fields, for other 16 fields if they are considered as String, I am OK with that.. details
      • But it will disable type mapping for all fields.. details
      • So when some data have CODETERM12 as CODETERM13 , like CODETERM14 , then it is throwing exception, as the type is mapped to CODETERM15 .. details
      • Confusion between mappings and types in ElasticSearch.. details
      • Elasticsearch has a very good fluent JSON builder; unfortunately, as far as I can tell, it's not a module but part of the bulk of the elasticsearch codebase, so it's not easily used without elasticsearch.. details