ALL COVERED TOPICS

NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter

NAVIGATE MAIN CATEGORIES

Close

"Data Is" or "Data Are"?

Paul M. Davis:

“Data is” or “data are”? It’s the type of sticky linguistic thicket that invites vociferous debate. […] I generally err towards “data are”, if for no other reason than to avoid angry email from data and/or grammar geeks.

Make sure you don’t miss the link to Simon Rogers’s post on Datablog looking into this same topic.

As for myself and this blog, I’ve made the (un)educated decision a while back to go with “data is” (based only on the fact that it sounds better).

Original title and link: "Data Is" or "Data Are"? (NoSQL database©myNoSQL)

via: http://www.greenplum.com/blog/topics/big-data-topics/data-is-or-data-are