diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 3bdc9cc8cc2cf..e57fe84b11cfb 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -5,7 +5,7 @@ We enjoy working with contributors to get their code accepted. There are many ap
The process for contributing to any of the Elasticsearch repositories is similar.
1. Sign the contributor license agreement
-Please make sure you have signed the [http://www.elasticsearch.org/contributor-agreement/](Contributor License Agreement). We are not asking you to assign copyright to us, but to give us the right to distribute your code without restriction. We ask this of all contributors in order to assure our users of the origin and continuing existence of the code. You only need to sign the CLA once.
+Please make sure you have signed the [Contributor License Agreement](http://www.elasticsearch.org/contributor-agreement/). We are not asking you to assign copyright to us, but to give us the right to distribute your code without restriction. We ask this of all contributors in order to assure our users of the origin and continuing existence of the code. You only need to sign the CLA once.
2. Rebase your changes
Update your local repository with the most recent code from the main Kibana repository, and rebase your branch on top of the latest master branch. We prefer your changes to be squashed into a single commit.
@@ -14,3 +14,4 @@ Update your local repository with the most recent code from the main Kibana repo
Push your local changes to your forked copy of the repository and submit a pull request. In the pull request, describe what your changes do and mention the number of the issue where discussion has taken place, eg “Closes #123″.
Then sit back and wait. There will probably be discussion about the pull request and, if any changes are needed, we would love to work with you to get your pull request merged into Kibana.
+
diff --git a/config.js b/config.js
index 30d70cd988c23..8d694bd880287 100644
--- a/config.js
+++ b/config.js
@@ -22,6 +22,7 @@ var config = new Settings(
kibana_index: "kibana-int",
modules: ['histogram','map','pie','table','filtering',
'timepicker','text','fields','hits','dashcontrol',
- 'column','derivequeries','trends','bettermap','query'],
+ 'column','derivequeries','trends','bettermap','query',
+ 'terms'],
}
);
diff --git a/panels/pie/module.js b/panels/pie/module.js
index 467fe9a4faa43..e2d660c3282be 100644
--- a/panels/pie/module.js
+++ b/panels/pie/module.js
@@ -25,10 +25,10 @@ angular.module('kibana.pie', [])
.controller('pie', function($scope, $rootScope, querySrv, dashboard, filterSrv) {
$scope.panelMeta = {
- status : "Deprecating Soon",
+ status : "Deprecated",
description : "Uses an Elasticsearch terms facet to create a pie chart. You should really only"+
- " point this at not_analyzed fields for that reason. This panel is going away soon, to be"+
- " replaced with a panel that can represent a terms facet in a variety of ways."
+ " point this at not_analyzed fields for that reason. This panel is going away soon, it has"+
+ " been replaced by the terms panel. Please use that one instead."
};
// Set and populate defaults
@@ -247,11 +247,10 @@ angular.module('kibana.pie', [])
colors: querySrv.colors
};
- // Populate element
+ // Populate legend
if(elem.is(":visible")){
scripts.wait(function(){
- scope.plot = $.plot(elem, scope.data, pie);
- scope.legend = scope.plot.getData();
+ scope.legend = $.plot(elem, scope.data, pie).getData();
if(!scope.$$phase) {
scope.$apply();
}
diff --git a/panels/terms/editor.html b/panels/terms/editor.html
new file mode 100644
index 0000000000000..3568e529fc361
--- /dev/null
+++ b/panels/terms/editor.html
@@ -0,0 +1,50 @@
+