schemaless

Elasticsearch: is there a way to declare for all (possibly dynamic) subfields of an object field as string?

孤者浪人 提交于 2019-12-30 11:25:10
问题 I have a doc_type with a mapping similar to this very simplified one: { "test":{ "properties":{ "name":{ "type":"string" }, "long_searchable_text":{ "type":"string" }, "clearances":{ "type":"object" } } } } The field clearances should be an object, with a series of alphanumeric identifiers for filtering purposes. A typical document will have this format: { "name": "Lord Macbeth", "long_searchable_text": "Life's but a walking shadow, a poor player, that..." "clearances": { "glamis":

Why is it called NoSQL?

蓝咒 提交于 2019-12-24 15:33:33
问题 I've recently worked with MongoDB and learned about its schemaless design. However, I'm confused with the term NoSQL? Why is it called that? Doesn't it use SQL or SQL-like queries? I've also read from an article that the main difference lies in how data is stored. Is this true? In the case of MongoDB, it's stored like JSON documents. Also, I'm confused why I always see 'NoSQL vs relational databases'. Aren't NoSQL databases relational? I believe documents in MongoDB are still related/linked

Solr Schemaless Mode creating fields as MultiValued

╄→гoц情女王★ 提交于 2019-12-08 06:51:11
问题 I'm using Solr 6.1 in Schemaless Mode. After creating a collection and indexing a sample data the fields created were all set to have MultiValued = true, except for unique id. The problem is when querying this data using SolrNet it wouldn't map the result to the model correctly. The queried results is returned as an array and require all my properties in the model to be updated to ICollection type. Is there anyway we can set these field to MultiValued = false when indexing the sample data? An

Using a Filesystem (Not a Database!) for Schemaless Data - Best Practices

浪子不回头ぞ 提交于 2019-12-03 10:48:12
问题 After reading over my other question, Using a Relational Database for Schema-Less Data, I began to wonder if a filesystem is more appropriate than a relational database for storing and querying schemaless data. Rather than just building a file system on top of MySQL, why not just save the data directly to the filesystem? Indexing needs to be figured out, but modern filesystems are very stable, have great features like replication, snapshot and backup facilities, and are flexible at storing

What is the best open source solution for storing time series data? [closed]

为君一笑 提交于 2019-12-03 03:52:55
问题 As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 7 years ago . I am interested in monitoring some objects. I expect to get about 10000 data points every 15 minutes. (Maybe not at first, but this is

Using a Relational Database for Schemaless Data - Best Practices

﹥>﹥吖頭↗ 提交于 2019-11-28 16:44:05
After reading a shocking article written by Bret Taylor (co-creator of FriendFeed; current CTO of Facebook), How FriendFeed uses MySQL to store schema-less data , I began to wonder if there are best practices for using a RDBMS such as Oracle, MySQL, or PostgreSQL for storing and querying schemaless data? Few people like to admit they're using a relational database when NoSQL is the new hotness, which makes it difficult to find good articles on the topic. How do I implement a schemaless (or "document-oriented") database as a layer on top of a relational database? thats the classic article in

How to export collection to CSV in MongoDB?

戏子无情 提交于 2019-11-28 15:30:17
How do you export all the records in a MongoDB collection to a .csv file? mongoexport --host localhost --db dbname --collection name --type=csv > test.csv This asks me to specify name of the fields I need to export. Can I just export all the fields without specifying the names of fields? campeterson @karoly-horvath has it right. Fields are required for csv. According to this bug in the MongoDB issue tracker https://jira.mongodb.org/browse/SERVER-4224 you MUST provide the fields when exporting to a csv . The docs are not clear on it. That is the reason for the error. Try this: mongoexport -

What's the attraction of schemaless database systems?

时光怂恿深爱的人放手 提交于 2019-11-28 03:28:05
I've been hearing a lot of talk about schema-less (often distributed) database systems like MongoDB, CouchDB, SimpleDB, etc... While I can understand they might be valuable for some purposes, in most of my applications I'm trying to persist objects that have a specific number of fields of a specific type, and I just automatically think in the relational model. I'm always thinking in terms of rows with unique integer ids, null/not null fields, SQL datatypes, and select queries to find sets. While I'm attracted to the distributed nature and easy JSON/RESTful interfaces of these new systems, I

Using a Relational Database for Schemaless Data - Best Practices

余生长醉 提交于 2019-11-27 09:53:14
问题 After reading a shocking article written by Bret Taylor (co-creator of FriendFeed; current CTO of Facebook), How FriendFeed uses MySQL to store schema-less data, I began to wonder if there are best practices for using a RDBMS such as Oracle, MySQL, or PostgreSQL for storing and querying schemaless data? Few people like to admit they're using a relational database when NoSQL is the new hotness, which makes it difficult to find good articles on the topic. How do I implement a schemaless (or

How to export collection to CSV in MongoDB?

我们两清 提交于 2019-11-27 09:11:59
问题 How do you export all the records in a MongoDB collection to a .csv file? mongoexport --host localhost --db dbname --collection name --type=csv > test.csv This asks me to specify name of the fields I need to export. Can I just export all the fields without specifying the names of fields? 回答1: @karoly-horvath has it right. Fields are required for csv. According to this bug in the MongoDB issue tracker https://jira.mongodb.org/browse/SERVER-4224 you MUST provide the fields when exporting to a