The issue I was seeing was caused by this line:
cost double DEFAULT '0',
in ctakes-ytex\scripts\data\hsql\kernel\create_tables.sql
fixed by removing the quotes around the 0 in any double and int declarations
But still if anyone is using ctakes-ytex with hsqlbd 2.3.4 I'd be
interested in any hearing if you ran into any other issues
On Fri, Mar 31, 2017 at 11:27 AM, James Masanz <masanz.ja...@gmail.com>
wrote:
> Here's the error I'm seeing when I try mvn clean install -DskipTests=true
>
> java.sql.SQLSyntaxErrorException: incompatible data types in combination
>
> Here's the part of the log
>
> jdbc.sqlcmd:
> [echo] db.schemaPUBLIC
> [echo] umls.schema ${db.schema}
> [echo] umls.catalog
> [echo] execute ./hsql/kernel/create_tables.sql
> [copy] Copying 1 file to C:\Users\james\AppData\Local\Temp
> [echo] executing C:\Users\james\AppData\Local\Temp\ytex1924671612.sql
> 31 Mar 2017 11:21:08 INFO ENGINE - open start - state not modified
> 31 Mar 2017 11:21:08 INFO ENGINE - dataFileCache open start
> 31 Mar 2017 11:21:08 INFO ENGINE - dataFileCache open end
> [sql] Executing resource: C:\Users\james\AppData\Local\
> Temp\ytex1924671612.sql
> [sql] Failed to execute: CREATE CACHED TABLE classifier_eval_svm (
> classifier_eval_id int not null , cost double DEFAULT '0', weight
> varchar(50), degree int DEFAULT '0', gamma double DEFAULT
> 0', kernel int NULL, supportVectors int null, vcdim double null )
> 31 Mar 2017 11:21:08 INFO ENGINE - dataFileCache commit start
> 31 Mar 2017 11:21:08 INFO ENGINE - dataFileCache commit end
> 31 Mar 2017 11:21:08 INFO ENGINE - Database closed
>
> On Fri, Mar 31, 2017 at 11:16 AM, Finan, Sean <
> sean.fi...@childrens.harvard.edu> wrote:
>
>> Challenging all ytex gurus and officianados ...
>>
>> One of the main goals for ctakes 4.0 is to get the dictionary databases
>> upgraded from hsqldb 1.8 to the current 2.3.4.
>>
>> We have lvg and the fast dictionary lookup straightened out, but we are
>> having issues with the ytex dictionary. Can anybody out there push forward
>> and claim the "ytex master" prize by helping us sort this out?
>>
>> The RM team was hoping to freeze a release candidate today, but time
>> spent on ytex is causing postponement.
>>
>> Thanks,
>> Sean
>>
>
>
