One server per "view"?

35 views
Skip to first unread message

David Kincaid

unread,
Sep 9, 2013, 11:08:53 PM9/9/13
to elephan...@googlegroups.com
Could you guys help me understand something about ElephantDB that isn't clear for me? Does each server instance only have a single "view"? It sounds like the ElephantDB shard files are created by a single MR job. So that means that you can't have one server holding data for more than one index. Is that how it works?

Thanks,

Dave

Soren Macbeth

unread,
Sep 9, 2013, 11:15:29 PM9/9/13
to elephan...@googlegroups.com
Each "view" or index is stored in something called a "domain" in edb parlance. You can serve as many domains as you like in your edb cluster. The shards (the number of which is configurable for each domain) of each domain are distributed amongst the servers in the cluster. A MR job creates or updates a domain, which is then served by the edb cluster. 


--
You received this message because you are subscribed to the Google Groups "elephantdb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elephantdb-us...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.



--
http://about.me/soren

David Kincaid

unread,
Sep 10, 2013, 8:16:22 AM9/10/13
to elephan...@googlegroups.com
Thanks, Soren. That answers my question. I have a project where we are pretty closely following Nathan's architecture in his Big Data book. We are just starting to build a few views on the master data in a serving layer. I'd like to give ElephantDB a try since it seems like it's built for doing exactly this. I'm facing a lot of opposition to that from others that want us to use an RDBMS (Oracle preferred) to populate a table that is served by a materialized view. One big selling point for doing that is that client applications that need to access these indexes can use their standard ODBC/JDBC tools to connect. We'll see if I can convince them to try out a better solution.

Thanks again for the answer.

- Dave

Jeroen van Dijk

unread,
Sep 10, 2013, 8:31:11 AM9/10/13
to elephan...@googlegroups.com
Hi David, 

As an aside, if SQL access is a required feature. You can also look into http://sploutsql.com . I haven't tried it myself, but it has much in common with ElephantDB while providing SQL access [1]. JDBC access seems to be a TODO.

If SQL is not a required feature, I can +1 ElephantDB :-)

Jeroen

Reply all
Reply to author
Forward
0 new messages