Why don't you try presto with monetdb? Should be easy to write a connector. https://prestodb.io On 04/16/2015 03:34 PM, José Raúl Pérez Rodríguez wrote:
Hi Luciana,
I am involved in the same decision, Vertica or MonetDB.
I choose Vertica for only one reason, scalability.
Despite I will use only de Community Edition, that limit scaling up to 3 nodes,the problem with MonetDB is that not support full functionalities at cluster lever, for example queries on a distributed table, can't be sorted, I maked a question to the developers mail list, and the answer was that this is not supported yet, they want to do it, but can't be sure when.
I would like to work with monet but at production level, this is a serious limitation.
Greetings
On 4/16/15, shamsul hassan <shamsulbuddy@gmail.com> wrote:
there is only one thing which has stopped me for using MonetDB in production is the lack of UPSERT operation. In my case new data comes every 30 mins and I cannot truncate and load the whole table again. Ideally an UPSERT would have helped here as it will only touch those records which are new or changed without truncating the whole table.
I raised the question few days before in Community list but didn't get any useful answer.
If i get any workaround for these UPSERTS the i would be as happy as pig in dirty water :)
Thanks
On Thu, Apr 16, 2015 at 2:37 PM, Ruben Silva < ruben.silva@cortex-intelligence.com> wrote:
Hello Luciano,
I don't have a full grasp of the new stuff introduced into MonetDB in the last year, but as far as I know there are still major differences between the two systems for me the most important is scalability. Vertica has no single point of failure when working as a cluster. However the CE version is limited to three nodes, so scalability is also limited in that case.
Vertica relies heavily on projections as a way to improve performance. If your data model is relatively stable it is something fairly easy to use, but if your data model changes at a high rate you will have a considerable amount of additional work managing the projections. Also if you use many projections they will hurt your DML statements performance.
MonetDB feeds on CPU and has no boundaries for its appetite, consuming as much resources as possible in order to respond to a single statement. That can be very good or very bad, it depends on your use case. Vertica has resource pools that are used to regulate the stuff (IO, Ram, CPU) that each query is allowed to use.
I don't know your use case (and that is crucial for a good advice), but if you are considering a scenario where you have a single machine for the database system, then go with MonetDB without any doubt. It is just faster and simpler.
Cumprimentos (Regards),
2015-04-16 14:04 GMT+01:00 Luciano Sasso <luciano@gsgroup.com.br>:
Hi,
The team of staff this questioning me about using Vertica, but it has limitations on the CE version. Someone already used the Vertica has some advantage over MonetDB?
-- Luciano Sasso Vieira Data Scientist & Solutions Architect
luciano@gsgroup.com.br <http://www.gsgroup.com.br> | tel: 17 3353-0833 | cel: 17 99706-9335 www.gsgroup.com.br
------------------------------ [image: Avast logo] <http://www.avast.com/>
Este email foi escaneado pelo Avast antivírus. www.avast.com
_______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list
_______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list
users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list