From 5c7614038f2311bd816ac7a3da9e23b2dcf30091 Mon Sep 17 00:00:00 2001 From: Rashid Khan Date: Fri, 3 Oct 2014 10:16:29 -0700 Subject: [PATCH 1/6] Version the extracted directory. Closes #462 --- README.md | 8 ++++---- tasks/build.js | 1 + tasks/config/copy.js | 13 +++++++++++++ tasks/create_packages.js | 4 ++-- 4 files changed, 20 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 6b67a6b46e92c..0563f7f5605d1 100644 --- a/README.md +++ b/README.md @@ -25,7 +25,7 @@ Kibana is an open source (Apache Licensed), browser based analytics and search d You're up and running! Fantastic! Kibana is now running on port 5601, so point your browser at http://YOURDOMAIN.com:5601. -The first screen you arrive at will ask you to configure an **index pattern**. An index pattern describes to Kibana how to access your data. We make the guess that you're working with log data, and we hope (because it's awesome) that you're working with Logstash. By default, we fill in `logstash-*` as your index pattern, thus the only thing you need to do is select which field contains the timestamp you'd like to use. Kibana reads your Elasticsearch mapping to find your time fields - select one from the list and hit *Create*. +The first screen you arrive at will ask you to configure an **index pattern**. An index pattern describes to kibana how to access your data. We make the guess that you're working with log data, and we hope (because it's awesome) that you're working with Logstash. By default, we fill in `logstash-*` as your index pattern, thus the only thing you need to do is select which field contains the timestamp you'd like to use. Kibana reads your Elasticsearch mapping to find your time fields - select one from the list and hit *Create*. **Tip:** there's an optimization in the way of the *Use event times to create index names* option. Since Logstash creates an index every day, Kibana uses that fact to only search indices that could possibly contain data in your selected time range. @@ -128,7 +128,7 @@ Or HTML status:[400 TO 499] AND (extension:php OR extension:html) ``` -While Lucene query syntax is simple and very powerful, Kibana also supports the full Elasticsearch, JSON based, Query DSL. See the [Elasticsearch documentation](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/query-dsl-query-string-query.html#query-string-syntax) for usage and examples. +While lucene query syntax is simple and very powerful, Kibana also supports the full elasticsearch, JSON based, query DSL. See the [Elasticsearch documentation](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/query-dsl-query-string-query.html#query-string-syntax) for usage and examples. ## Visualize @@ -163,7 +163,7 @@ To the right of the search box there are a row of icons for creating new visuali #### Aggregation Builder -The aggregation builder on the left of the screen is used for configuring the [metric](http://www.elasticsearch.org/guide/en/elasticsearch/reference/1.x/search-aggregations.html#_metrics_aggregations) and [bucket](http://www.elasticsearch.org/guide/en/elasticsearch/reference/1.x/search-aggregations.html#_bucket_aggregations) aggregations used to create a visualization. (If you are coming from the SQL world, buckets are similar to group-bys. Check out the [Elasticsearch docs](http://www.elasticsearch.org/guide/en/elasticsearch/reference/1.x/search-aggregations.html) for more info) For a bar chart or line chart the *metric* is used for the y-axis and the *buckets* are used for the x-axis, segment bar colors, and row/column splits. For pie charts the "metric" is used for the size of the slice and the *bucket* is used for the number of slices. Other visualizations may use these in new and different ways. +The aggregation builder on the left of the screen is used for configuring the [metric](http://www.elasticsearch.org/guide/en/elasticsearch/reference/1.x/search-aggregations.html#_metrics_aggregations) and [bucket](http://www.elasticsearch.org/guide/en/elasticsearch/reference/1.x/search-aggregations.html#_bucket_aggregations) aggregations used to create a visualization. (If you are coming from the SQL world, buckets are similar to group-bys. Check out the [elasticsearch docs](http://www.elasticsearch.org/guide/en/elasticsearch/reference/1.x/search-aggregations.html) for more info) For a bar chart or line chart the *metric* is used for the y-axis and the *buckets* are used for the x-axis, segment bar colors, and row/column splits. For pie charts the "metric" is used for the size of the slice and the *bucket* is used for the number of slices. Other visualizations may use these in new and different ways. For the remainder of this documentation we are going to use the bar chart as our example when discussing the features of the aggregation panel. The same concepts apply to the other visualizations but the bar chart is the workhorse of the visualization world. @@ -314,4 +314,4 @@ Clicking on the *View* action loads that item in the associated applications. Re Clicking *Edit* will allow you to change the title, description and other settings of the saved object. You can also edit the schema of the stored object. *Note:* this operation is for advanced users only - making changes here can break large portions of the application. - + \ No newline at end of file diff --git a/tasks/build.js b/tasks/build.js index 19d770d4b3599..97daea41de597 100644 --- a/tasks/build.js +++ b/tasks/build.js @@ -16,6 +16,7 @@ module.exports = function (grunt) { 'copy:dist', 'compile_dist_readme', 'chmod_kibana', + 'copy:versioned_dist', 'create_packages' ]); }; diff --git a/tasks/config/copy.js b/tasks/config/copy.js index 752207d9ab821..382cc49fd2565 100644 --- a/tasks/config/copy.js +++ b/tasks/config/copy.js @@ -1,4 +1,5 @@ module.exports = function (grunt) { + var version = grunt.config.get('pkg.version'); var config = { kibana_src: { @@ -59,6 +60,18 @@ module.exports = function (grunt) { dest: '<%= build %>/dist/kibana/config/' } ] + }, + + versioned_dist: { + options: { mode: true }, + files: [ + { + expand: true, + cwd: '<%= build %>/dist/kibana', + src: '**', + dest: '<%= build %>/dist/kibana-' + version + } + ] } }; diff --git a/tasks/create_packages.js b/tasks/create_packages.js index d881e6afb131e..0d1a08a922535 100644 --- a/tasks/create_packages.js +++ b/tasks/create_packages.js @@ -13,8 +13,8 @@ module.exports = function (grunt) { var archiveName = join(target, packageName + '-' + version); var distPath = join(grunt.config.get('build'), 'dist'); - var tgzCmd = 'tar -zcvf ' + archiveName + '.tar.gz kibana'; - var zipCmd = 'zip -r ' + archiveName + '.zip kibana'; + var tgzCmd = 'tar -zcvf ' + archiveName + '.tar.gz kibana-' + version; + var zipCmd = 'zip -r ' + archiveName + '.zip kibana-' + version; var options = { cwd: distPath }; From b1431c5af1401fcff42951544bec955b95c46556 Mon Sep 17 00:00:00 2001 From: Rashid Khan Date: Fri, 3 Oct 2014 10:19:53 -0700 Subject: [PATCH 2/6] Fix Leslie's changes to README.md --- README.md | 2 +- docs/discover.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 0563f7f5605d1..ea7417a9a47f8 100644 --- a/README.md +++ b/README.md @@ -128,7 +128,7 @@ Or HTML status:[400 TO 499] AND (extension:php OR extension:html) ``` -While lucene query syntax is simple and very powerful, Kibana also supports the full elasticsearch, JSON based, query DSL. See the [Elasticsearch documentation](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/query-dsl-query-string-query.html#query-string-syntax) for usage and examples. +While Lucene query syntax is simple and very powerful, Kibana also supports the full Elasticsearch, JSON based, Query DSL. See the [Elasticsearch documentation](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/query-dsl-query-string-query.html#query-string-syntax) for usage and examples. ## Visualize diff --git a/docs/discover.md b/docs/discover.md index 08334253bfa5c..8f8af05742f90 100644 --- a/docs/discover.md +++ b/docs/discover.md @@ -90,4 +90,4 @@ Or HTML status:[400 TO 499] AND (extension:php OR extension:html) ``` -While lucene query syntax is simple and very powerful, Kibana also supports the full elasticsearch, JSON based, query DSL. See the [Elasticsearch documentation](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/query-dsl-query-string-query.html#query-string-syntax) for usage and examples. +While Lucene query syntax is simple and very powerful, Kibana also supports the full Elasticsearch, JSON based, Query DSL. See the [Elasticsearch documentation](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/query-dsl-query-string-query.html#query-string-syntax) for usage and examples. From d35d6b287d3ebd803ca4e9edd8800ebf679e48e9 Mon Sep 17 00:00:00 2001 From: Rashid Khan Date: Fri, 3 Oct 2014 11:09:13 -0700 Subject: [PATCH 3/6] more leslie fixing --- README.md | 2 +- docs/quick_start.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index ea7417a9a47f8..8accc44fcae9c 100644 --- a/README.md +++ b/README.md @@ -25,7 +25,7 @@ Kibana is an open source (Apache Licensed), browser based analytics and search d You're up and running! Fantastic! Kibana is now running on port 5601, so point your browser at http://YOURDOMAIN.com:5601. -The first screen you arrive at will ask you to configure an **index pattern**. An index pattern describes to kibana how to access your data. We make the guess that you're working with log data, and we hope (because it's awesome) that you're working with Logstash. By default, we fill in `logstash-*` as your index pattern, thus the only thing you need to do is select which field contains the timestamp you'd like to use. Kibana reads your Elasticsearch mapping to find your time fields - select one from the list and hit *Create*. +The first screen you arrive at will ask you to configure an **index pattern**. An index pattern describes to Kibana how to access your data. We make the guess that you're working with log data, and we hope (because it's awesome) that you're working with Logstash. By default, we fill in `logstash-*` as your index pattern, thus the only thing you need to do is select which field contains the timestamp you'd like to use. Kibana reads your Elasticsearch mapping to find your time fields - select one from the list and hit *Create*. **Tip:** there's an optimization in the way of the *Use event times to create index names* option. Since Logstash creates an index every day, Kibana uses that fact to only search indices that could possibly contain data in your selected time range. diff --git a/docs/quick_start.md b/docs/quick_start.md index 830adc870ede9..eab04ad2114e0 100644 --- a/docs/quick_start.md +++ b/docs/quick_start.md @@ -2,7 +2,7 @@ You're up and running! Fantastic! Kibana is now running on port 5601, so point your browser at http://YOURDOMAIN.com:5601. -The first screen you arrive at will ask you to configure an **index pattern**. An index pattern describes to kibana how to access your data. We make the guess that you're working with log data, and we hope (because it's awesome) that you're working with Logstash. By default, we fill in `logstash-*` as your index pattern, thus the only thing you need to do is select which field contains the timestamp you'd like to use. Kibana reads your Elasticsearch mapping to find your time fields - select one from the list and hit *Create*. +The first screen you arrive at will ask you to configure an **index pattern**. An index pattern describes to Kibana how to access your data. We make the guess that you're working with log data, and we hope (because it's awesome) that you're working with Logstash. By default, we fill in `logstash-*` as your index pattern, thus the only thing you need to do is select which field contains the timestamp you'd like to use. Kibana reads your Elasticsearch mapping to find your time fields - select one from the list and hit *Create*. **Tip:** there's an optimization in the way of the *Use event times to create index names* option. Since Logstash creates an index every day, Kibana uses that fact to only search indices that could possibly contain data in your selected time range. From eaa1d30a38af7549d0ea484a317184886acd1716 Mon Sep 17 00:00:00 2001 From: Rashid Khan Date: Fri, 3 Oct 2014 11:11:29 -0700 Subject: [PATCH 4/6] Fixing capitalization --- README.md | 6 +++--- docs/discover.md | 4 ++-- docs/visualize.md | 2 +- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 8accc44fcae9c..9cccdac693693 100644 --- a/README.md +++ b/README.md @@ -55,7 +55,7 @@ By default Kibana shows the last 15 minutes of data. You might want to expand th ### Document list -Once you see some documents, you can begin to explore Discover. In the document list, Kibana will show you the localized version of the time field you specified in your index pattern, as well as the `_source` of the elasticsearch document. +Once you see some documents, you can begin to explore Discover. In the document list, Kibana will show you the localized version of the time field you specified in your index pattern, as well as the `_source` of the Elasticsearch document. **Tip:** By default the table contains 500 of the most recent documents. You can increase the number of documents in the table from the advanced settings screen. See the [Setting section](#advanced) of the documentation. @@ -128,7 +128,7 @@ Or HTML status:[400 TO 499] AND (extension:php OR extension:html) ``` -While Lucene query syntax is simple and very powerful, Kibana also supports the full Elasticsearch, JSON based, Query DSL. See the [Elasticsearch documentation](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/query-dsl-query-string-query.html#query-string-syntax) for usage and examples. +While lucene query syntax is simple and very powerful, Kibana also supports the full Elasticsearch, JSON based, query DSL. See the [Elasticsearch documentation](http://www.Elasticsearch.org/guide/en/Elasticsearch/reference/current/query-dsl-query-string-query.html#query-string-syntax) for usage and examples. ## Visualize @@ -163,7 +163,7 @@ To the right of the search box there are a row of icons for creating new visuali #### Aggregation Builder -The aggregation builder on the left of the screen is used for configuring the [metric](http://www.elasticsearch.org/guide/en/elasticsearch/reference/1.x/search-aggregations.html#_metrics_aggregations) and [bucket](http://www.elasticsearch.org/guide/en/elasticsearch/reference/1.x/search-aggregations.html#_bucket_aggregations) aggregations used to create a visualization. (If you are coming from the SQL world, buckets are similar to group-bys. Check out the [elasticsearch docs](http://www.elasticsearch.org/guide/en/elasticsearch/reference/1.x/search-aggregations.html) for more info) For a bar chart or line chart the *metric* is used for the y-axis and the *buckets* are used for the x-axis, segment bar colors, and row/column splits. For pie charts the "metric" is used for the size of the slice and the *bucket* is used for the number of slices. Other visualizations may use these in new and different ways. +The aggregation builder on the left of the screen is used for configuring the [metric](http://www.Elasticsearch.org/guide/en/Elasticsearch/reference/1.x/search-aggregations.html#_metrics_aggregations) and [bucket](http://www.Elasticsearch.org/guide/en/Elasticsearch/reference/1.x/search-aggregations.html#_bucket_aggregations) aggregations used to create a visualization. (If you are coming from the SQL world, buckets are similar to group-bys. Check out the [Elasticsearch docs](http://www.Elasticsearch.org/guide/en/Elasticsearch/reference/1.x/search-aggregations.html) for more info) For a bar chart or line chart the *metric* is used for the y-axis and the *buckets* are used for the x-axis, segment bar colors, and row/column splits. For pie charts the "metric" is used for the size of the slice and the *bucket* is used for the number of slices. Other visualizations may use these in new and different ways. For the remainder of this documentation we are going to use the bar chart as our example when discussing the features of the aggregation panel. The same concepts apply to the other visualizations but the bar chart is the workhorse of the visualization world. diff --git a/docs/discover.md b/docs/discover.md index 8f8af05742f90..8cced17da4e93 100644 --- a/docs/discover.md +++ b/docs/discover.md @@ -17,7 +17,7 @@ By default Kibana shows the last 15 minutes of data. You might want to expand th ### Document list -Once you see some documents, you can begin to explore Discover. In the document list, Kibana will show you the localized version of the time field you specified in your index pattern, as well as the `_source` of the elasticsearch document. +Once you see some documents, you can begin to explore Discover. In the document list, Kibana will show you the localized version of the time field you specified in your index pattern, as well as the `_source` of the Elasticsearch document. **Tip:** By default the table contains 500 of the most recent documents. You can increase the number of documents in the table from the advanced settings screen. See the [Setting section](#advanced) of the documentation. @@ -90,4 +90,4 @@ Or HTML status:[400 TO 499] AND (extension:php OR extension:html) ``` -While Lucene query syntax is simple and very powerful, Kibana also supports the full Elasticsearch, JSON based, Query DSL. See the [Elasticsearch documentation](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/query-dsl-query-string-query.html#query-string-syntax) for usage and examples. +While lucene query syntax is simple and very powerful, Kibana also supports the full Elasticsearch, JSON based, query DSL. See the [Elasticsearch documentation](http://www.Elasticsearch.org/guide/en/Elasticsearch/reference/current/query-dsl-query-string-query.html#query-string-syntax) for usage and examples. diff --git a/docs/visualize.md b/docs/visualize.md index c6faae2021124..93636d2aec9b5 100644 --- a/docs/visualize.md +++ b/docs/visualize.md @@ -30,7 +30,7 @@ To the right of the search box there are a row of icons for creating new visuali #### Aggregation Builder -The aggregation builder on the left of the screen is used for configuring the [metric](http://www.elasticsearch.org/guide/en/elasticsearch/reference/1.x/search-aggregations.html#_metrics_aggregations) and [bucket](http://www.elasticsearch.org/guide/en/elasticsearch/reference/1.x/search-aggregations.html#_bucket_aggregations) aggregations used to create a visualization. (If you are coming from the SQL world, buckets are similar to group-bys. Check out the [elasticsearch docs](http://www.elasticsearch.org/guide/en/elasticsearch/reference/1.x/search-aggregations.html) for more info) For a bar chart or line chart the *metric* is used for the y-axis and the *buckets* are used for the x-axis, segment bar colors, and row/column splits. For pie charts the "metric" is used for the size of the slice and the *bucket* is used for the number of slices. Other visualizations may use these in new and different ways. +The aggregation builder on the left of the screen is used for configuring the [metric](http://www.Elasticsearch.org/guide/en/Elasticsearch/reference/1.x/search-aggregations.html#_metrics_aggregations) and [bucket](http://www.Elasticsearch.org/guide/en/Elasticsearch/reference/1.x/search-aggregations.html#_bucket_aggregations) aggregations used to create a visualization. (If you are coming from the SQL world, buckets are similar to group-bys. Check out the [Elasticsearch docs](http://www.Elasticsearch.org/guide/en/Elasticsearch/reference/1.x/search-aggregations.html) for more info) For a bar chart or line chart the *metric* is used for the y-axis and the *buckets* are used for the x-axis, segment bar colors, and row/column splits. For pie charts the "metric" is used for the size of the slice and the *bucket* is used for the number of slices. Other visualizations may use these in new and different ways. For the remainder of this documentation we are going to use the bar chart as our example when discussing the features of the aggregation panel. The same concepts apply to the other visualizations but the bar chart is the workhorse of the visualization world. From d3c076b7f083819d28231b9d8d2362816535977a Mon Sep 17 00:00:00 2001 From: Rashid Khan Date: Fri, 3 Oct 2014 11:14:04 -0700 Subject: [PATCH 5/6] Fixing some new capitalization issues --- README.md | 4 ++-- docs/discover.md | 2 +- docs/visualize.md | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 9cccdac693693..45cda61b34f38 100644 --- a/README.md +++ b/README.md @@ -128,7 +128,7 @@ Or HTML status:[400 TO 499] AND (extension:php OR extension:html) ``` -While lucene query syntax is simple and very powerful, Kibana also supports the full Elasticsearch, JSON based, query DSL. See the [Elasticsearch documentation](http://www.Elasticsearch.org/guide/en/Elasticsearch/reference/current/query-dsl-query-string-query.html#query-string-syntax) for usage and examples. +While Lucene query syntax is simple and very powerful, Kibana also supports the full Elasticsearch, JSON based, Query DSL. See the [Elasticsearch documentation](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/query-dsl-query-string-query.html#query-string-syntax) for usage and examples. ## Visualize @@ -163,7 +163,7 @@ To the right of the search box there are a row of icons for creating new visuali #### Aggregation Builder -The aggregation builder on the left of the screen is used for configuring the [metric](http://www.Elasticsearch.org/guide/en/Elasticsearch/reference/1.x/search-aggregations.html#_metrics_aggregations) and [bucket](http://www.Elasticsearch.org/guide/en/Elasticsearch/reference/1.x/search-aggregations.html#_bucket_aggregations) aggregations used to create a visualization. (If you are coming from the SQL world, buckets are similar to group-bys. Check out the [Elasticsearch docs](http://www.Elasticsearch.org/guide/en/Elasticsearch/reference/1.x/search-aggregations.html) for more info) For a bar chart or line chart the *metric* is used for the y-axis and the *buckets* are used for the x-axis, segment bar colors, and row/column splits. For pie charts the "metric" is used for the size of the slice and the *bucket* is used for the number of slices. Other visualizations may use these in new and different ways. +The aggregation builder on the left of the screen is used for configuring the [metric](http://www.elasticsearch.org/guide/en/Elasticsearch/reference/1.x/search-aggregations.html#_metrics_aggregations) and [bucket](http://www.elasticsearch.org/guide/en/Elasticsearch/reference/1.x/search-aggregations.html#_bucket_aggregations) aggregations used to create a visualization. (If you are coming from the SQL world, buckets are similar to group-bys. Check out the [Elasticsearch docs](http://www.elasticsearch.org/guide/en/Elasticsearch/reference/1.x/search-aggregations.html) for more info) For a bar chart or line chart the *metric* is used for the y-axis and the *buckets* are used for the x-axis, segment bar colors, and row/column splits. For pie charts the "metric" is used for the size of the slice and the *bucket* is used for the number of slices. Other visualizations may use these in new and different ways. For the remainder of this documentation we are going to use the bar chart as our example when discussing the features of the aggregation panel. The same concepts apply to the other visualizations but the bar chart is the workhorse of the visualization world. diff --git a/docs/discover.md b/docs/discover.md index 8cced17da4e93..fc4d147396133 100644 --- a/docs/discover.md +++ b/docs/discover.md @@ -90,4 +90,4 @@ Or HTML status:[400 TO 499] AND (extension:php OR extension:html) ``` -While lucene query syntax is simple and very powerful, Kibana also supports the full Elasticsearch, JSON based, query DSL. See the [Elasticsearch documentation](http://www.Elasticsearch.org/guide/en/Elasticsearch/reference/current/query-dsl-query-string-query.html#query-string-syntax) for usage and examples. +While Lucene query syntax is simple and very powerful, Kibana also supports the full Elasticsearch, JSON based, Query DSL. See the [Elasticsearch documentation](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/query-dsl-query-string-query.html#query-string-syntax) for usage and examples. diff --git a/docs/visualize.md b/docs/visualize.md index 93636d2aec9b5..0d300171839ef 100644 --- a/docs/visualize.md +++ b/docs/visualize.md @@ -30,7 +30,7 @@ To the right of the search box there are a row of icons for creating new visuali #### Aggregation Builder -The aggregation builder on the left of the screen is used for configuring the [metric](http://www.Elasticsearch.org/guide/en/Elasticsearch/reference/1.x/search-aggregations.html#_metrics_aggregations) and [bucket](http://www.Elasticsearch.org/guide/en/Elasticsearch/reference/1.x/search-aggregations.html#_bucket_aggregations) aggregations used to create a visualization. (If you are coming from the SQL world, buckets are similar to group-bys. Check out the [Elasticsearch docs](http://www.Elasticsearch.org/guide/en/Elasticsearch/reference/1.x/search-aggregations.html) for more info) For a bar chart or line chart the *metric* is used for the y-axis and the *buckets* are used for the x-axis, segment bar colors, and row/column splits. For pie charts the "metric" is used for the size of the slice and the *bucket* is used for the number of slices. Other visualizations may use these in new and different ways. +The aggregation builder on the left of the screen is used for configuring the [metric](http://www.elasticsearch.org/guide/en/Elasticsearch/reference/1.x/search-aggregations.html#_metrics_aggregations) and [bucket](http://www.elasticsearch.org/guide/en/Elasticsearch/reference/1.x/search-aggregations.html#_bucket_aggregations) aggregations used to create a visualization. (If you are coming from the SQL world, buckets are similar to group-bys. Check out the [Elasticsearch docs](http://www.elasticsearch.org/guide/en/Elasticsearch/reference/1.x/search-aggregations.html) for more info) For a bar chart or line chart the *metric* is used for the y-axis and the *buckets* are used for the x-axis, segment bar colors, and row/column splits. For pie charts the "metric" is used for the size of the slice and the *bucket* is used for the number of slices. Other visualizations may use these in new and different ways. For the remainder of this documentation we are going to use the bar chart as our example when discussing the features of the aggregation panel. The same concepts apply to the other visualizations but the bar chart is the workhorse of the visualization world. From c54d0f0608c45e430bfc1ecf03eddb2d0bc0f288 Mon Sep 17 00:00:00 2001 From: Rashid Khan Date: Fri, 3 Oct 2014 11:16:28 -0700 Subject: [PATCH 6/6] One more capitalization problem in the readme --- README.md | 2 +- docs/visualize.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 45cda61b34f38..4678c60c86fc8 100644 --- a/README.md +++ b/README.md @@ -163,7 +163,7 @@ To the right of the search box there are a row of icons for creating new visuali #### Aggregation Builder -The aggregation builder on the left of the screen is used for configuring the [metric](http://www.elasticsearch.org/guide/en/Elasticsearch/reference/1.x/search-aggregations.html#_metrics_aggregations) and [bucket](http://www.elasticsearch.org/guide/en/Elasticsearch/reference/1.x/search-aggregations.html#_bucket_aggregations) aggregations used to create a visualization. (If you are coming from the SQL world, buckets are similar to group-bys. Check out the [Elasticsearch docs](http://www.elasticsearch.org/guide/en/Elasticsearch/reference/1.x/search-aggregations.html) for more info) For a bar chart or line chart the *metric* is used for the y-axis and the *buckets* are used for the x-axis, segment bar colors, and row/column splits. For pie charts the "metric" is used for the size of the slice and the *bucket* is used for the number of slices. Other visualizations may use these in new and different ways. +The aggregation builder on the left of the screen is used for configuring the [metric](http://www.elasticsearch.org/guide/en/elasticsearch/reference/1.x/search-aggregations.html#_metrics_aggregations) and [bucket](http://www.elasticsearch.org/guide/en/elasticsearch/reference/1.x/search-aggregations.html#_bucket_aggregations) aggregations used to create a visualization. (If you are coming from the SQL world, buckets are similar to group-bys. Check out the [Elasticsearch docs](http://www.elasticsearch.org/guide/en/elasticsearch/reference/1.x/search-aggregations.html) for more info) For a bar chart or line chart the *metric* is used for the y-axis and the *buckets* are used for the x-axis, segment bar colors, and row/column splits. For pie charts the "metric" is used for the size of the slice and the *bucket* is used for the number of slices. Other visualizations may use these in new and different ways. For the remainder of this documentation we are going to use the bar chart as our example when discussing the features of the aggregation panel. The same concepts apply to the other visualizations but the bar chart is the workhorse of the visualization world. diff --git a/docs/visualize.md b/docs/visualize.md index 0d300171839ef..9cd61202f49bc 100644 --- a/docs/visualize.md +++ b/docs/visualize.md @@ -30,7 +30,7 @@ To the right of the search box there are a row of icons for creating new visuali #### Aggregation Builder -The aggregation builder on the left of the screen is used for configuring the [metric](http://www.elasticsearch.org/guide/en/Elasticsearch/reference/1.x/search-aggregations.html#_metrics_aggregations) and [bucket](http://www.elasticsearch.org/guide/en/Elasticsearch/reference/1.x/search-aggregations.html#_bucket_aggregations) aggregations used to create a visualization. (If you are coming from the SQL world, buckets are similar to group-bys. Check out the [Elasticsearch docs](http://www.elasticsearch.org/guide/en/Elasticsearch/reference/1.x/search-aggregations.html) for more info) For a bar chart or line chart the *metric* is used for the y-axis and the *buckets* are used for the x-axis, segment bar colors, and row/column splits. For pie charts the "metric" is used for the size of the slice and the *bucket* is used for the number of slices. Other visualizations may use these in new and different ways. +The aggregation builder on the left of the screen is used for configuring the [metric](http://www.elasticsearch.org/guide/en/elasticsearch/reference/1.x/search-aggregations.html#_metrics_aggregations) and [bucket](http://www.elasticsearch.org/guide/en/elasticsearch/reference/1.x/search-aggregations.html#_bucket_aggregations) aggregations used to create a visualization. (If you are coming from the SQL world, buckets are similar to group-bys. Check out the [Elasticsearch docs](http://www.elasticsearch.org/guide/en/elasticsearch/reference/1.x/search-aggregations.html) for more info) For a bar chart or line chart the *metric* is used for the y-axis and the *buckets* are used for the x-axis, segment bar colors, and row/column splits. For pie charts the "metric" is used for the size of the slice and the *bucket* is used for the number of slices. Other visualizations may use these in new and different ways. For the remainder of this documentation we are going to use the bar chart as our example when discussing the features of the aggregation panel. The same concepts apply to the other visualizations but the bar chart is the workhorse of the visualization world.