[
https://issues.apache.org/jira/browse/DRILL-4740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Rogers updated DRILL-4740:
-------------------------------
Summary: Improvements to "Analyzing the Yelp Academic Dataset" (was:
Awkward wording in "Analyzing the Yelp Academic Dataset")
> Improvements to "Analyzing the Yelp Academic Dataset"
> -----------------------------------------------------
>
> Key: DRILL-4740
> URL: https://issues.apache.org/jira/browse/DRILL-4740
> Project: Apache Drill
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 1.6.0
> Reporter: Paul Rogers
> Priority: Minor
>
> Consider the topic paragraph for the Yelp sample data page:
> http://drill.apache.org/docs/analyzing-the-yelp-academic-dataset/
> It could use a bit of TLC. For example:
> "Apache Drill is one of the fastest growing open source projects, with the
> community making rapid progress with monthly releases The key difference is
> Drill’s agility and flexibility."
> This is a non-sequiter. The speed and agility of the software does not drive
> the monthly releases. Can we reword it to say that Drill’s speed and agility
> makes it a popular project? And that many people work hard to make it better
> with monthly releases? Something like that...
> (Although, at present, releases have dropped to bi-monthly or quarterly...)
> And:
> "Along with meeting the table stakes for SQL-on-Hadoop, which is to achieve
> low latency performance at scale, …"
> Seems two problems.
> 1. What does it mean “meeting the table stakes”? Very unclear.
> 2. This is a run-on sentence that tries to say multiple thoughts in a single
> sentence and should be rewritten.
> Then, there is redundancy:
> "...Drill allows users to analyze the data without any ETL or up-front schema
> definitions. … Drill, has a “no schema” approach…"
> I’m sure this paragraph was written quickly early on, but it could certainly
> be improved a bit…
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
