Sorry Bob. I forgot to attach patch to issue.
On Fri, Jul 1, 2016 at 7:19 AM, 胡永亮/Bob <[email protected]> wrote: > hello, * Vasiliy <[email protected]>* > > I saw the issue, the status is the following: > > * Status:* Patch Available > > But, I check the code in the github: > https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/cache/store/jdbc/CacheAbstractJdbcStore.java > > > The related code was not changed for fixing this bug. > > I want to know, how can I get the code patch? > > thanks. > > ------------------------------ > 胡永亮 > > Bob > > > *From:* Vasiliy Sisko <[email protected]> > *Date:* 2016-06-29 15:37 > *To:* [email protected] > *Subject:* Re: Re: argument type mismatch of oracle TIMESTAMP field when > call loadCache > > Hello Bob. > > > We create issue to fix that problem. You can watch it on page: > https://issues.apache.org/jira/browse/IGNITE-3394 > > On Wed, Jun 29, 2016 at 7:34 AM, 胡永亮/Bob <[email protected]> wrote: > >> sorry, the infomation is not in detail. >> >> My ignite's version is new release version: 1.6. >> >> ------------------------------ >> 胡永亮 >> >> Bob >> >> >> *From:* Vasiliy Sisko <[email protected]> >> *Date:* 2016-06-28 19:18 >> *To:* [email protected] >> *Subject:* Re: Re: argument type mismatch of oracle TIMESTAMP field when >> call loadCache >> Hello Bob. >> >> What version of Ignite are you use? >> >> On Tue, Jun 28, 2016 at 12:01 PM, [email protected] <[email protected]> >> wrote: >> >>> 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), >>> "AKA130" VARCHAR2(3) NOT NULL ENABLE, >>> "AAB001" NUMBER(20,0), >>> "AKA101" VARCHAR2(3), >>> "BKC192" TIMESTAMP (6), >>> "AKC193" VARCHAR2(50), >>> "BKC231" VARCHAR2(300), >>> "BKC194" TIMESTAMP (6), >>> "AKC195" VARCHAR2(3), >>> "AKC196" VARCHAR2(50), >>> "BKC232" VARCHAR2(300), >>> "BKC317" VARCHAR2(3), >>> "AKA151" FLOAT(126), >>> "AKC021" VARCHAR2(3), >>> "BKC021" VARCHAR2(3), >>> "BKC197" VARCHAR2(3), >>> "BKC120" VARCHAR2(3), >>> "BKC128" VARCHAR2(3), >>> "BKC126" VARCHAR2(3), >>> "BAE073" VARCHAR2(16), >>> "AKE013" VARCHAR2(3), >>> "BKC023" VARCHAR2(3), >>> "AAA027" VARCHAR2(6), >>> "BKC378" VARCHAR2(50), >>> "BKC379" VARCHAR2(50), >>> "BKC380" VARCHAR2(50), >>> "BKC381" VARCHAR2(50), >>> "AAB034" VARCHAR2(16), >>> "BAC888" VARCHAR2(16), >>> "AAB301" VARCHAR2(16), >>> "BKC390" VARCHAR2(20), >>> "BKC500" VARCHAR2(30), >>> "BKA130" VARCHAR2(3), >>> "AKB021" VARCHAR2(200), >>> "BKF050" VARCHAR2(20), >>> "AKC273" VARCHAR2(50), >>> "AKF002" VARCHAR2(100), >>> "AMC020" TIMESTAMP (6), >>> "AKE021" VARCHAR2(20), >>> "AKE020" VARCHAR2(20), >>> "BKC191" VARCHAR2(20), >>> "BKC190" VARCHAR2(20), >>> "AAE017" VARCHAR2(50), >>> "AAE032" TIMESTAMP (6), >>> "AAC999" VARCHAR2(16), >>> "AAE135" VARCHAR2(20), >>> "AAC003" VARCHAR2(50), >>> "AAC004" VARCHAR2(3), >>> "BAE450" NUMBER(20,0), >>> "AAB999" VARCHAR2(16), >>> "AAB004" VARCHAR2(500), >>> "AAB019" VARCHAR2(3), >>> "AAB020" VARCHAR2(3), >>> "BKC233" VARCHAR2(2048), >>> "BAE013" VARCHAR2(100), >>> "BKC319" VARCHAR2(3), >>> "AAE013" VARCHAR2(200), >>> "BKC050" VARCHAR2(3), >>> "BKC051" VARCHAR2(3), >>> "BKC052" VARCHAR2(200), >>> "BKC053" VARCHAR2(200), >>> "BKC054" VARCHAR2(200), >>> "BAZ001" NUMBER(20,0), >>> "BAZ002" NUMBER(20,0), >>> "BZE011" VARCHAR2(50), >>> "BZE036" TIMESTAMP (6), >>> "AAE011" VARCHAR2(50), >>> "AAE036" TIMESTAMP (6), >>> "AAE100" VARCHAR2(3), >>> "BKC055" VARCHAR2(3), >>> "BKC056" VARCHAR2(3), >>> "BKC057" VARCHAR2(3), >>> "BKC058" VARCHAR2(3), >>> "BKB010" VARCHAR2(3), >>> "BKB011" VARCHAR2(3), >>> "BKC059" VARCHAR2(50), >>> "BKC060" FLOAT(126), >>> "BKC280" VARCHAR2(50), >>> "BKC281" VARCHAR2(50), >>> "BKC282" VARCHAR2(50), >>> "BKC283" VARCHAR2(50), >>> "BKC284" VARCHAR2(50), >>> "BKE160" VARCHAR2(3), >>> "BKE161" VARCHAR2(50), >>> "BKE162" TIMESTAMP (6), >>> "BKC401" VARCHAR2(3), >>> "BKC285" VARCHAR2(300), >>> "BKC286" VARCHAR2(300), >>> "BKC287" VARCHAR2(100), >>> "BKC288" VARCHAR2(200), >>> "BKC289" VARCHAR2(50), >>> "BKC290" VARCHAR2(50), >>> "BKC291" FLOAT(126), >>> "BKC292" FLOAT(126), >>> "BAB024" VARCHAR2(200), >>> "AAE009" VARCHAR2(200), >>> "AAE010" VARCHAR2(200), >>> CONSTRAINT "pk_kc21" PRIMARY KEY ("AKB020", "AKC190") >>> USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS >>> STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 >>> PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 >>> BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT) >>> TABLESPACE "IGNITE" ENABLE >>> ) SEGMENT CREATION IMMEDIATE >>> PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 >>> NOCOMPRESS LOGGING >>> STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 >>> PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 >>> BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT) >>> TABLESPACE "IGNITE" >>> >>> ------------------------------ >>> 胡永亮 >>> >>> bob >>> >>> >>> *From:* Alexey Kuznetsov <[email protected]> >>> *Date:* 2016-06-28 10:50 >>> *To:* [email protected] >>> *Subject:* Re: argument type mismatch of oracle TIMESTAMP field when >>> call loadCache >>> Hi, Bob! >>> >>> Could post here a sample table script that help us to reproduce the >>> problem? >>> Something like "create table test (....)". >>> >>> Also, just in case please specify your Oracle version. >>> >>> Thanks! >>> >>> -- >>> Alexey Kuznetsov >>> >>> >> >> >> -- >> Vasiliy Sisko >> GridGain Systems >> www.gridgain.com >> >> > > > -- > Vasiliy Sisko > GridGain Systems > www.gridgain.com > > > > --------------------------------------------------------------------------------------------------- > Confidentiality Notice: The information contained in this e-mail and any > accompanying attachment(s) > is intended only for the use of the intended recipient and may be > confidential and/or privileged of > Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader > of this communication is > not the intended recipient, unauthorized use, forwarding, printing, > storing, disclosure or copying > is strictly prohibited, and may be unlawful.If you have received this > communication in error,please > immediately notify the sender by return e-mail, and delete the original > message and all copies from > your system. Thank you. > > --------------------------------------------------------------------------------------------------- > -- Vasiliy Sisko GridGain Systems www.gridgain.com
