Can aggregation use a prepared result of real-time Map Reduce task?


(Tong Liu) #1

(I move the topic from github issue to here)

I want to know the theory of ES aggregation.
Maybe, it is one of them:
(1) like a Database. compute when the aggregation query comes.
(2) like Storm. When a data comes, it aggregate once. You don't need
aggregate when query comes. The aggregation query use a prepared result. So
it is very quick when query. Storm is like a real-time Hadoop.

So ES is like (1)a common Database? or (2)Storm?
Thank you!

(

This is imotov answer:

In short the answer to your question is aggregations are computed when an
aggregation query comes, but because of data structures that elasticsearch
is using, they can computed in very efficient manner.

)

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/c8bd9a10-4698-4563-8f04-b79e5f9c4bc2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(Tong Liu) #2

I still want to know some basic theory about that efficient manner.
Thank you very much!

在 2014年8月7日星期四UTC+8下午12时00分31秒,Tong Liu写道:

(I move the topic from github issue to here)

I want to know the theory of ES aggregation.
Maybe, it is one of them:
(1) like a Database. compute when the aggregation query comes.
(2) like Storm. When a data comes, it aggregate once. You don't need
aggregate when query comes. The aggregation query use a prepared result. So
it is very quick when query. Storm is like a real-time Hadoop.

So ES is like (1)a common Database? or (2)Storm?
Thank you!

(

This is imotov answer:

In short the answer to your question is aggregations are computed when an
aggregation query comes, but because of data structures that elasticsearch
is using, they can computed in very efficient manner.

)

On Thursday, August 7, 2014 12:00:31 PM UTC+8, Tong Liu wrote:

(I move the topic from github issue to here)

I want to know the theory of ES aggregation.
Maybe, it is one of them:
(1) like a Database. compute when the aggregation query comes.
(2) like Storm. When a data comes, it aggregate once. You don't need
aggregate when query comes. The aggregation query use a prepared result. So
it is very quick when query. Storm is like a real-time Hadoop.

So ES is like (1)a common Database? or (2)Storm?
Thank you!

(

This is imotov answer:

In short the answer to your question is aggregations are computed when an
aggregation query comes, but because of data structures that elasticsearch
is using, they can computed in very efficient manner.

)

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/22f55524-4778-4ed6-858c-4a4994ef7b5e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(Tong Liu) #3

I still want to know some basic theory about that efficient manner.

On Thursday, August 7, 2014 12:00:31 PM UTC+8, Tong Liu wrote:

(I move the topic from github issue to here)

I want to know the theory of ES aggregation.
Maybe, it is one of them:
(1) like a Database. compute when the aggregation query comes.
(2) like Storm. When a data comes, it aggregate once. You don't need
aggregate when query comes. The aggregation query use a prepared result. So
it is very quick when query. Storm is like a real-time Hadoop.

So ES is like (1)a common Database? or (2)Storm?
Thank you!

(

This is imotov answer:

In short the answer to your question is aggregations are computed when an
aggregation query comes, but because of data structures that elasticsearch
is using, they can computed in very efficient manner.

)

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/eeedcf51-a0e0-4016-ab83-2854d32acb69%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(Tong Liu) #4

Hi, is there some one know?
Is the aggregation have a cache? And +1 to the cache, when new proper data
comes?
Query visit the cache, not calculate from index and shard?

On Thursday, August 7, 2014 12:03:44 PM UTC+8, Tong Liu wrote:

I still want to know some basic theory about that efficient manner.

On Thursday, August 7, 2014 12:00:31 PM UTC+8, Tong Liu wrote:

(I move the topic from github issue to here)

I want to know the theory of ES aggregation.
Maybe, it is one of them:
(1) like a Database. compute when the aggregation query comes.
(2) like Storm. When a data comes, it aggregate once. You don't need
aggregate when query comes. The aggregation query use a prepared result. So
it is very quick when query. Storm is like a real-time Hadoop.

So ES is like (1)a common Database? or (2)Storm?
Thank you!

(

This is imotov answer:

In short the answer to your question is aggregations are computed when an
aggregation query comes, but because of data structures that elasticsearch
is using, they can computed in very efficient manner.

)

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/afc5d7e7-60e0-4b2e-8535-d6bb09e21fc8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(system) #5