Google的Dremel是什么?它与Mapreduce有什么不同? [英] What is Google's Dremel? How is it different from Mapreduce?

查看:480
本文介绍了Google的Dremel是什么?它与Mapreduce有什么不同?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

Google的Dremel 在这里描述。 Dremel和Mapreduce有什么区别?

解决方案

检查 article out。 Dremel是蜂巢未来应该(而且将会)的未来。

MapReduce及其上的解决方案(如Pig,Hive等)的主要问题是它们在执行作业和获得答案之间存在固有延迟。 Dremel采用了一种全新的方法(在2010年出现在谷歌的那篇论文中),其中... ...


...使用新颖的查询基于聚合树的执行引擎...

...运行几乎实时互动 adhoc 查询两个MapReduce都无法查询的内容。并且Pig和Hive不是实时的

您应该密切关注项目出来的。对我来说,这也是非常新的......所以,欢迎任何其他专家评论!



编辑: Dremel是 HIVE (而不是我之前提到的MapReduce)应该是。 Hive现在提供了一个SQL界面来运行MapReduce作业。 Hive具有非常高的延迟,因此在临时数据分析中不太实用。 Dremel通过使用与MapReduce不同的技术为数据提供了非常快速的SQL接口。


Google's Dremel is described here. What's the difference between Dremel and Mapreduce?

解决方案

Check this article out. Dremel is the what the future of hive should (and will) be.

The major issue of MapReduce and solutions on top of it, like Pig, Hive etc, is that they have an inherent latency between running the job and getting the answer. Dremel uses a totally novel approach (came out in 2010 in that paper by google) which...

...uses a novel query execution engine based on aggregator trees...

...to run almost realtime , interactive AND adhoc queries both of which MapReduce cannot. And Pig and Hive aren't real time

You should keep an eye on projects coming out of this. Is is pretty new for me too... so any other expert comments are welcome!

Edit: Dremel is what the future of HIVE (and not MapReduce as I mentioned before) should be. Hive right now provides a SQL like interface to run MapReduce jobs. Hive has very high latency, and so is not practical in ad-hoc data analysis. Dremel provides a very fast SQL like interface to the data by using a different technique than MapReduce.

这篇关于Google的Dremel是什么?它与Mapreduce有什么不同?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
相关文章
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆