dncrews/angular-elastic-builder

This is an Angular.js directive for building an Elasticsearch query. You just give it the fields and can generate a query for it.

angular-elastic-builder's Issues

How to add our own dropdown conditions

For Example

Like term , I have a new variable i have to query

{
	"size": 0,
	"filter": {
		"and": [{
			"term": {
				"status": "failed"  // my own , can have multiple values (failed,passed,pending)
			}
		}]
	}
}

filter can not be applied

setting $scope.elasticQueryBuilder.query and $scope.elasticQueryBuilder.needsUpdate = true does not work.

I changed file dist/angular-elastic-builder.js, line 478 from

prev[choice] = truthy === (~group[key][obj.field].indexOf(choice));

to

prev[choice] = truthy === (group[key][obj.field].indexOf(choice) >= 0);

to fix it.

checkboxes (for type multi) are deselected when query is parsed

@dncrews : When query is parsed multi values in query group are now converted to false whereas they should be converted to true so the checkboxes show as checked.
This regression has been introduced with commit e79a94b.

Date Fields

JSON output change

Hi,
how to change the JSON output when the rule is set, I dont want to send filter, size while forming json.
just wanted it to be .
sample json should be
Get rules

{
  "condition": "AND",
  "rules": [
    {
      "id": "price",
      "field": "price",
      "type": "double",
      "input": "text",
      "operator": "less",
      "value": "10.25"
    },
    {
      "condition": "OR",
      "rules": [
        {
          "id": "category",
          "field": "category",
          "type": "integer",
          "input": "select",
          "operator": "equal",
          "value": "2"
        },
        {
          "id": "category",
          "field": "category",
          "type": "integer",
          "input": "select",
          "operator": "equal",
          "value": "1"
        }
      ]
    }
  ]
}

Fix `needsUpdate`

If you don't put needsUpdate, the filters array never gets created...

Does this query-builder follow the suggested approach in terms of the query DSL for ES post ver. 2.X?

Thanks for a great project.
The more I read up on the changes in the Query DSL post version 2.0 ... it seems like 'and', 'or', 'all' and 'any' .. are being de-emphasised if not being deprecated altogether in favour of compound queries that use 'must', 'must_not', and 'should' that are wrapped as 'bool' queries (like below).

Are there plans to handle these types of 'new-breed' queries in this tool?

parsing_exception

hihi @dncrews i have use your example to build query like that

{
    "size": 10,
    "filter": {
        "and": [
            {
                "term": {
                    "appkey": "710659"
                }
            }
        ]
    }
}

and i receive error when using https://github.com/elastic/elasticsearch-js
{
"error": {
"root_cause": [
{
"type": "parsing_exception",
"reason": "Unknown key for a START_OBJECT in [filter].",
"line": 1,
"col": 21
}
],
"type": "parsing_exception",
"reason": "Unknown key for a START_OBJECT in [filter].",
"line": 1,
"col": 21
},
"status": 400
}

But when im modify the query like that, im fine

{
  "query": {
    "bool": {
      "filter": [
        {
          "term": {
            "appkey": "710569"
          }
        }
      ]
    }
  },
  "size": 10
}

so you can suggest me how can fix that when using your project

DatePickerPopup no longer working.

datepickerpopup isn't working now when select calendar.
http://prntscr.com/offhs9

date format parsed from query to builder defaults to current date with fixed format

@dncrews
When parsed into the builder, date fields from a query default to the current date with fixed format (calendar default format). Only some ISO formats are recognized