Correct some typos. s/looks/looks enough/ s/we should firstly/we should firstly do/
On Fri, Mar 20, 2015 at 4:37 PM, Hyunsik Choi <[email protected]> wrote: > There were some typos in my previous post. Especially, I meant 'more > and high quality'. > > In my opinion, our roadmap look enough for you guys to achieve > something you want. It takes not short time to achieve them. I think > that there is no magic. We should firstly what we already know. > > If you need more description of some features in our roadmap, please > let me know. I'll describe them. > > On Fri, Mar 20, 2015 at 3:08 PM, Hyunsik Choi <[email protected]> wrote: >> General ideas that we firstly need are already listed on the roadmap >> or Jira. Everybody know what we should do for speedup and TPC-DS. >> >> So, we need code instead of talk. >> >> If you or your company want to make Tajo faster, contribute more high >> quality codes to Tajo community. It's that all. >> >> On Fri, Mar 20, 2015 at 9:33 AM, Dongjoon Hyun <[email protected]> wrote: >>> Hi, all. >>> >>> I have a question in these day. >>> *Can we improve Tajo performance further than now?* >>> Since Tajo is well architectured, each module can be improved >>> independently. >>> From the SQL parser to the network part, there will be many candidates to >>> improve. >>> >>> If you didn't try due to lack of time to implement, you can share your idea. >>> As a Tajo community member, please feel free to comment anything. >>> We can discuss and create more issues for that. >>> >>> When we release Tajo 0.11, I believe that Tajo passes TPC-DS 99 queries (up >>> to now 26 queries) and Tajo speed becomes more faster. It depends on our >>> coding speed. :-) >>> >>> Best regards, >>> Dongjoon. >>> >>> PS. FYI, 'The Only Hadoop RDBMS' is used for SpliceMachine. (based on >>> Apache Derby and HBase, http://www.splicemachine.com/ )
