maria-discuss team mailing list archive

[Peter Laursen <peter_laursen@xxxxxxxxxx>]

I think Sergei G. told me once that TokuDB would not compile with Visual
Studio and that MariaDB would only try to fix it in MariaDB if Toku people
wanted to collaborate on this (what they did not). it probably was before
TokuDB was swalloed by Percona .

-- Peter

On Thu, Oct 13, 2016 at 1:36 PM, Vladislav Vaintroub <vvaintroub@xxxxxxxxx>
wrote:

>
>
> On 13.10.2016 12:00, Peter Laursen wrote:
>
> I have a few questions
>
> 1) will RocksDB be available on Windows? ToduDB isn't (because it does not
> compile on Visual Studio I think).
>
> Personally, I plan to make this happen . At least RocksDB works on
> Windows, the port seems to be done by competent people (MS Bing folks) so
> that part compiles, a runs and was benchmarked as well.
> https://github.com/facebook/rocksdb/blob/4cab5ebecdb42ceff7030a7606b5b5
> c31ba702ef/WINDOWS_PORT.md
> I expect this port to be solid.
>
> As for TokuDB,  if I remember correctly, its original team declared it to
> be compilable and runnable only on Linux x64 with  "modern" C++ (back than
> it could have been gcc's idea of C++11)  and absolutely necessary jemalloc
> , so I figured it was not worth looking at making a port. I even would
> speculate nobody has tried to compile TokuDB on Windows that far.
>
>
>
> 2) How large a set of configuraton options will RocksDB have? InnoDB now
> has100+ I guess, and that is a mess IMO. I liked the simplicity of the now
> dead Primebase (if I remember the name right) storage engine in this
> respect. Also is there an overview somehere of current and planned
> configuration options?
>
>
> -- Peter
> -- Webyog
>
>
> On Thu, Oct 13, 2016 at 6:50 AM, Roberto Spadim <roberto@xxxxxxxxxxxxx>
> wrote:
>
>> just some ideas...
>>
>> --
>> at first time i read plugable parser, and i was thinking that it could
>> allow nosql (handler socket/memcahce) protocol inside mysql "session"
>> (connect + auth + allow communicate with server), removing the sql
>> parser/optimizer without loosing mysql_connect() authentication/security
>>
>> a "plugable" parser, could remove a lot of nosql client side/server side
>> libs, maybe a nosql parser could be nice to be implemented
>> like"mysql_crud_get()", "mysql_crud_set()", etc .. without installing a
>> daemon plugin (handlersocket/memcache)
>>
>> a plugable parser could allow a python/R/julia/anything to run a
>> analytics algorithm direct to storage engine? i don't know if this could
>> help at allow v8/others languages at server side but the idea sounds ok to
>> me, something like mysql_v8_eval("v8 script"), just ideas...
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~maria-discuss
>> Post to     : maria-discuss@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~maria-discuss
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~maria-discuss
> Post to     : maria-discuss@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~maria-discuss
> More help   : https://help.launchpad.net/ListHelp
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~maria-discuss
> Post to     : maria-discuss@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~maria-discuss
> More help   : https://help.launchpad.net/ListHelp
>
>