...I do not agree with you... Yeah right. I am so upset. Was waiting for your nod
LOL Dr Mich Talebzadeh LinkedIn * https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw <https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw>* http://talebzadehmich.wordpress.com *Disclaimer:* Use it at your own risk. Any and all responsibility for any loss, damage or destruction of data or any other property which may arise from relying on this email's technical content is explicitly disclaimed. The author will in no case be liable for any monetary damages arising from such loss, damage or destruction. On 14 August 2016 at 12:40, Jörn Franke <[email protected]> wrote: > I do not agree with you . Competition is needed for innovation. I would be > more concerned if there is no innovation. This is really bad for companies. > > Besides, as others pointed out Spark and Hive have different use cases. > There are use cases where Spark is better and other where Hive is better. > There are also a lot of use cases where both are useless. > > On 08 Aug 2016, at 03:49, 理 <[email protected]> wrote: > > in my opinion, multiple engine is not advantage, but reverse. it > disperse the dev energy. > consider the activity ,sparksql support all tpc ds without modify > syntax! but hive cannot. > consider the tech, dag, vectorization, etc sparksql also has, seems > the code is more efficiently. > > > regards > On 08/08/2016 08:48, Will Du <[email protected]> wrote: > > First, hive supports different engines. Look forward it's dynamic engine > switch > Second, look forward hadoop 3rd gen and map reduce on memory will fill the > gap > > Thanks, > Will > > On 2016年8月7日, at 20:27, 理 <[email protected]> wrote: > > hi, > sparksql improve so fast, both hive and sparksql are similar, so > hive will lost or not? > > regards > > > > > >
