Re: Re: argument type mismatch of oracle TIMESTAMP field when call loadCache

2016-06-27 Thread hu...@neusoft.com
hi, Alexey First, thanks your reply. My oracle version is 12.1.0.1.0, the ddl script is the following: CREATE TABLE "UIGNITE"."KC21" ( "AKB020" VARCHAR2(20) NOT NULL ENABLE, "AKC190" VARCHAR2(24) NOT NULL ENABLE, "AAC001" NUMBER(20,0) NOT NULL ENABLE, "AAZ500" VARCHAR2(50), "AKA1

argument type mismatch of oracle TIMESTAMP field when call loadCache

2016-06-27 Thread hu...@neusoft.com
hi, When I loaded the data from oracle through cache.loadData. The exception which is argument type mismatch of oracle TIMESTAMP happened. The detail: I produced the schema through the tool schema-import-tool. A pojo object is Kc21, and it has a property Bkc192, its type is

Re: Re: About benchmark and scalability testing

2016-06-02 Thread hu...@neusoft.com
only supports SELECTs. Therefore, I recommend to measure Ignite's performance using your actual use-case. Start from reading Ignite's documentation [1]. [1] http://apacheignite.readme.io 2016-06-02 11:34 GMT+03:00 hu...@neusoft.com : Hi, Is there somebody making the performance tes

About benchmark and scalability testing

2016-06-02 Thread hu...@neusoft.com
Hi, Is there somebody making the performance testing for Ignite? Who used the Benchmark Factory™ or BenchmarkSQL which supports TPC-C to test Ignite? I want to know how does Ignite compare with mysql or oracle in OLTP. Or, where can I find the related article? Any guidance