The JethroData Blog

Updates on JethroData, SQL-on-Hadoop and Big Data

JethroData Raises Additional $8.1 Million in Funding

Posted by Eli Singer on June 9, 2015 at 7:30 AM

I am extremely pleased to announce that we have recently raised an $8.1 million investment round. The round was led by our new partner Square Peg Capital, with participation from our existing investor, Pitango Venture Capital. Arad Naveh of Square Peg will be joining our board of directors and I am looking forward to working with him and benefiting from his vast experience as both an entrepreneur and an investor.

Read More

Topics: Announcements, in the news

Meet Us at Hadoop Summit 2015

Posted by JethroData Team on June 8, 2015 at 11:02 AM

Attending Hadoop Summit 2015 in San Jose? We are too, and we'd love for you to come by our booth and chat about how JethroData can help your company. You can find us at booth G9, right next door to SnapLogic.

Read More

Topics: Big Data, Hadoop, Events

What's new in JethroData 1.0

Posted by Ofir Manor on April 7, 2015 at 11:13 AM

As we announced earlier today, JethroData 1.0 was just released. Since launching the public beta six months ago, we have added numeruos improvements and bug fixes across the board. I would like to share some highlights:

Read More

JethroData is Now in GA

Posted by Eli Singer on April 7, 2015 at 5:00 AM

I'm thrilled to announce that JethroData, the fastest SQL-on-Hadoop solution in the market, is now in GA. After more than two years in extensive development, we are proud to release this ready-for-prime-time, stable and highly performant version of the product.

Read More

Topics: Blog, Announcements, in the news, Product

Being "Creative" with TPC-DS Benchmark - Dynamic Partition Pruning

Posted by Ofir Manor on November 10, 2014 at 9:01 AM

In this post, I would like to present a common optimization challenge, how is is solved in JethroData, and how some other SQL-on-Hadoop products "overcame" that challenge by manually modifying their benchmark scripts and queries to avoid the situation (which was quite a surprise for us when figured it while running our own benchmarks).

Read More

Topics: Blog