Uses of Class
lumis.portal.bigdata.query.AbstractSubAggregationAwareAggregation

Packages that use AbstractSubAggregationAwareAggregation

Package	Description
lumis.portal.bigdata.elasticsearch	lumis.portal.bigdata implementation for using Elasticsearch.
lumis.portal.bigdata.query	Interfaces and classes used for performing a query in IBigDataRepository (more specifically in an IBigDataSearcher).

Uses of AbstractSubAggregationAwareAggregation in lumis.portal.bigdata.elasticsearch

Fields in lumis.portal.bigdata.elasticsearch declared as AbstractSubAggregationAwareAggregation

Modifier and Type	Field and Description
protected AbstractSubAggregationAwareAggregation	AbstractSubAggregationAwareAggregationResult.aggregation

Constructors in lumis.portal.bigdata.elasticsearch with parameters of type AbstractSubAggregationAwareAggregation

Constructor and Description
AbstractSubAggregationAwareAggregationResult(AbstractSubAggregationAwareAggregation aggregation, org.elasticsearch.search.aggregations.Aggregations result, lumis.portal.bigdata.elasticsearch.IFilterParser.ParseContext context) Create a new instance;

Uses of AbstractSubAggregationAwareAggregation in lumis.portal.bigdata.query

Subclasses of AbstractSubAggregationAwareAggregation in lumis.portal.bigdata.query

Modifier and Type	Class and Description
class	DateHistogramAggregation Date histogram aggregation.
class	DateRangeAggregation Date range aggregation.
class	FilterAggregation Aggregation used to narrow down the current query document space.
class	GeoDistanceAggregation Aggregation that aggregates the documents based on a center point and a collection of ranges. This aggregation produces a result of type IGeoDistanceAggregationResult.
class	HistogramAggregation Histogram aggregation.
class	NestedObjectAggregation This aggregation should be used mainly when some aggregations must be performed over fields inside a nested object field. In this case, the aggregations should be added as sub-aggregations of a nested object aggregation. For example, suppose we have a person document type with the following fields: name (text) address (nested object) street (keyword) number (keyword) And there are 3 documents in this document type: {"name": "Nara Jones"} {"name": "Albert Russef", "address": [{"street": "Av Rio Branco", "number": "23"}, {"street": "Av Francisco Bicalho"}]} {"name": "Josef Camus", "address": [{"street": "Av Presidente Vargas"}]} If a filter aggregation must be created with a filter to restrict the documents to those with the field address.number, and this filter aggregation has a terms aggregation as sub aggregation, the terms aggregation result will have the buckets Av Rio Branco and Av Francisco Bicalho, because, since there's no nested aggregation, both of them will be considered in filter aggregation.
class	ReverseNestedAggregation Reverse Nested Aggregation.
class	TermsAggregation Aggregation that produces an ITermsAggregationResult.