Amazon EMR (Elastic MapReduce) vs. Apache Hive

We are running it to perform preparation which takes a few hours on EC2 to be running on a spark-based EMR cluster to total the preparation inside minutes rather than a few hours. Ease of utilization and capacity to select from either Hadoop or spark. Processing time diminishes from 5-8 hours to 25-30 minutes compared with the Ec2 occurrence and more in a few cases.

Incentivized

Apache Hive shines for ad-hoc analysis and plugging into BI tools. Its SQL-like syntax allows for ease of use not for only for engineers but also for data analysts. Through our experience, there are probably more desirable tools to use if you are planning on integrating Hive into your processing pipeline.

Incentivized

• The cluster size of MapReduce is very dynamic and therefore scalability is good for EMR.
• It also works well with other Amazon Web Services like Amazon Simple Storage Service, which means that data can be taken from those services and written back to them.
• I tried using the in-house hosting at the university I work in, but there would be a lot of complications with technical support required. For Amazon, the support and documentation was good to solve these problems faster.

Incentivized

• Hive syntax is almost like SQL, so for someone already familiar with SQL it takes almost no effort to pick up Hive.
• To be able to run map reduce jobs using json parsing and generate dynamic partitions in parquet file format.
• Simplifies your experience with Hadoop especially for non-technical/coding partners.

Incentivized

• Sometimes bootstrapping certain tools comes with debugging costs. The tools provided by some of the enterprise editions are great compared to EMR.
• Like some of the enterprise editions EMR does not provide on premises options.
• No UI client for saving the workbooks or code snippets. Everything has to go through submitting process. Not really convenient for tracking the job as well.

Incentivized

• Use Hive for analytical work loads. Write once and read many scenarios. Do not prefer updates and deletes.
• Behind scenes Hive creates map reduce jobs. Hive performance is slow compared to Apache Spark.
• Map reduce writes the intermediate outputs to dial whereas Spark operates in in-memory and uses DAG.

Incentivized

Since I do not know the second data warehouse solution that integrate with HDFS as well as Hive.

Documentation is quite good and the product is regularly updated, so new features regularly come out. The setup is straightforward enough, especially once you have already established the overall platform infrastructure and the aws-cli APIs are easy enough to use. It would be nice to have some out-of-the-box integrations for checking logs and the Spark UI, rather than relying on know-how and digging through multiple levels to find the informations

Incentivized

Hive is a very good big data analysis and ad-hoc query platform, which supports scaling also. The BI processes can be easily integrated with Hadoop via the Hive. It can deal with a much larger data set that traditional RDBMS can not. It is a "must-have" component of the big data domain.

Incentivized

I give the overall support for Amazon EMR this rating because while the support technicians are very knowledgeable and always able to help, it sometimes takes a very long time to get in contact with one of the support technicians. So overall the support is pretty good for Amazon EMR.

Incentivized

Apache Hive is a FOSS project and its open source. We need not definitely comment on anything about the support of open source and its developer community. But, it has got tremendous developer support, awesome documentation. I would justify the fact that much support can be gathered from the community backup.

Incentivized

Snowflake is a lot easier to get started with than the other options. Snowflake's data lake building capabilities are far more powerful. Although Amazon EMR isn't our first pick, we've had an excellent experience with EC2 and S3. Because of our current API interfaces, it made more sense for us to continue with Hadoop rather than explore other options.

Incentivized

We have used a simple but necessary function such as merging certain data tables, which although they may be from different areas, complement each other or are necessary, you can use metadata if what you need is to validate the origin of your information and what impact it has, is also feasible.

Incentivized

• It was obviously cheaper and convenient to use as most of our data processing and pipelines are on AWS. It was fast and readily available with a click and that saved a ton of time rather than having to figure out the down time of the cluster if its on premises.
• It saved time on processing chunks of big data which had to be processed in short period with minimal costs. EMR solved this as the cluster setup time and processing was simple, easy, cheap and fast.
• It had a negative impact as it was very difficult in submitting the test jobs as it lags a UI to submit spark code snippets.

Incentivized

• Good ROI for being able to access data easily across the network, we have large amounts of data and this is a good system to access it
• Good ROI for being easy to learn how to use for new employees, not much time spent which saves costs
• Good ROI for being able to integrate with Spark and other applications, hence data can be analyzed through programs

Incentivized