Re: Unexpected performance issue with SQL query followed by error

Sure I can give that a try, so I start multiple nodes and define a collocation key on the tables being joined together (from the many object to the single cardinality ones)? The data is being pulled to populate a work list for users, sort of a jira issue list for example. So the data goes to the c

Re: Unexpected performance issue with SQL query followed by error

I see what you are saying, so if I would start lets say 4 nodes on the machine instead of 1 I should get a drastic increase of response time? I'd be happy to give that a try, anything special I need to cater for based on the case we are running here? -- View this message in context: http://apac

Re: Unexpected performance issue with SQL query followed by error

Hello, Both are using the same database and same data, I did some count(*) checks on the tables in Oracle and H2 and they yield the same count. This means that things go wrong on another level, not sure where though. Lets take a step back and rerun the tests: This is the SQL: /SELECT DISTINCT a

Re: Unexpected performance issue with SQL query followed by error

Hi, Please fine the explain plan attached. explainplan.png br jan -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Unexpected-performance-issue-with-SQL-query-followed-by-error-tp4726

Re: Unexpected performance issue with SQL query followed by error

Well iterating trough via the JDBC resultset takes a good 2 seconds, query itself just over 4 seconds. This is actually slower than running it via the oracle jdbc connection (executeQuery: 645ms / rs iteration: 1271ms). Looks like my hopes to cut down on the response time of this particular use cas

Re: Unexpected performance issue with SQL query followed by error

Okey, progress! Executing this one from back in the thread: /EXPLAIN ANALYZE SELECT DISTINCT * FROM "Activity".activity activity0 LEFT OUTER JOIN "Activity".activityuseraccountrole activityuseraccountrole0 ON activity0.activity_Id=activityuseraccountrole0.activity_Id/ Generates the following,

Re: Unexpected performance issue with SQL query followed by error

Hello, No the ones listed are all the regular ones (PK, FK indexes from the auto generated code), I execute 'SELECT * FROM INFORMATION_SCHEMA.INDEXES' to list them. I tried adding them in the 'CacheConfig' class I am using to define the caches and then they seem to appear. I will add the other on

Re: Unexpected performance issue with SQL query followed by error

Okey so we can indeed conclude that the indexes are not registered. This is the output: /SELECT ACTIVITY0.ACTIVITY_ID, ACTIVITYUSERACCOUNTROLE0.ACTIVITY_ID FROM "Activity".ACTIVITY ACTIVITY0 /* "Activity".ACTIVITY.__SCAN_ */ LEFT OUTER JOIN "Activity".ACTIVITYUSERACCOUNTROLE ACTIVITYUS

Re: Unexpected performance issue with SQL query followed by error

Hello, Yes indeed, I am using those classes. Can I verify in the H2 console that the indexes are there as expected? br jan -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Unexpected-performance-issue-with-SQL-query-followed-by-error-tp4726p5279.html Sent from t

Re: Unexpected performance issue with SQL query followed by error

Hello, This one has been running for 10 minutes now without producing results - so rather the join. /EXPLAIN ANALYZE SELECT DISTINCT * FROM "Activity".activity activity0 LEFT OUTER JOIN "Activity".activityuseraccountrole activityuseraccountrole0 ON activity0.activity_Id=activityuseraccountrole0.a

Re: Unexpected performance issue with SQL query followed by error

And indeed, I am running with these options: /MEM_ARGS="-XX:PermSize=256m -Xms1g -Xmx8g -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:+UseTLAB -XX:NewSize=128m -XX:MaxNewSize=128m -XX:MaxTenuringThreshold=0 -XX:SurvivorRatio=1024 -XX:+UseCMSInitiatingOccupancyOnly -XX:CMSInitiatingOccupancyFraction

Re: Unexpected performance issue with SQL query followed by error

Hello, The activity table is 121823 records and the activityuseraccountrole 1027839 records. First one runs under a second and produces: /SELECT DISTINCT ACTIVITY0._KEY, ACTIVITY0._VAL, ACTIVITY0.ACTIVITY_ID, ACTIVITY0.TIMESTAMP, ACTIVITY0.CONTAINER_ID, ACTIVITY0.ACTIVITY

Re: Unexpected performance issue with SQL query followed by error

Thanks, Added the code and executed the following: EXPLAIN ANALYZE SELECT DISTINCT * FROM "Activity".activity activity0 LEFT OUTER JOIN "Activity".activityuseraccountrole activityuseraccountrole0 ON activityuseraccountrole0.activity_Id = activity0.activity_Id AND activityuseraccountrole0.useracco

Re: Unexpected performance issue with SQL query followed by error

Hello Alexei, Thanks for this! Could you provide the attachment you speak of I think you forgot to attach it. br jan -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Unexpected-performance-issue-with-SQL-query-followed-by-error-tp4726p5162.html Sent from the Apa

Re: Unexpected performance issue with SQL query followed by error

Hello, Please find the attached pojo instances with group index annotations. JoinPerfPojos.zip Yes I understand that there are probably better ways to retrieve the data, but the point of my exercise is to see how we c

Re: Unexpected performance issue with SQL query followed by error

I tried to defined the grouped indexes but I see no result on the explain plan nor on the actual run. This must mean that either I am doing something wrong or that something is going wrong. First attempt I annotated the fields on the objects, for example an extract of the Activity pojo: //**

Re: Unexpected performance issue with SQL query followed by error

Thanks, It indeed looks like its not using indexes. I'll have a go with it and let you know where I ended up. SELECT DISTINCT ACTIVITY0.ACTIVITY_ID AS __C0, ACTIVITY0.SEQUENCENR AS __C1, ACTIVITY0.NAME_MLID AS __C2, ACTIVITY0.NAME AS __C3, ACTIVITY0.DESCRIPTION_MLID AS __C4,

Re: Unexpected performance issue with SQL query followed by error

Hello, I adapted the JVM settings as follows: -server -XX:PermSize=256m -Xms1g -Xmx8g -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:+UseTLAB -XX:NewSize=128m -XX:MaxNewSize=128m -XX:MaxTenuringThreshold=0 -XX:SurvivorRatio=1024 -XX:+UseCMSInitiatingOccupancyOnly -XX:CMSInitiatingOccupancyFraction=

Unexpected performance issue with SQL query followed by error

Hello All, Following up on my previous adventures I am not at the point where I can test my real life case - replacing a module which is performing slow by heavy database access. This is the

Re: SQL Aliases are not interpreted correctly

Hello, Thanks works like a charm! Up to the next level in my experiment. br jan -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/SQL-Aliases-are-not-interpreted-correctly-tp4281p4692.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: SQL Aliases are not interpreted correctly

Superb, that would really do the trick for my use cases! best regards jan -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/SQL-Aliases-are-not-interpreted-correctly-tp4281p4356.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: SQL Aliases are not interpreted correctly

Hello, Yes I totally agree that the generated Java class should follow the well known conventions. An intermediate solution might be (I say might since I do not know the inner workings of Ignite) to have the variables 'ugly' in the Java class and have pretty accessors (get/set). All 'better' sol

Re: SQL Aliases are not interpreted correctly

Hello, Ah I see yes, so in order for me to be able to 'switch' our db layer to use the cache I would need to customize the generator in order to generate classes and cache definitions matching with the actual tables names. Does it work in a case sensitive manner as well or is it case insensitive o

SQL Aliases are not interpreted correctly

Hello, Continuing my previous journey in order to use Ignite as a cache for my database I am now testing with the next step in my sql test cases. Again using the 'Activity' case from previous iterations I am now hitting an unexpected case of interpretation of the sql aliases we use in our queries.

Re: Unexpected SQL error when running sql with conditions

This works great now on latest nightly, thanks! -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Unexpected-SQL-error-when-running-sql-with-conditions-tp3899p4280.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite Schema Import Utility - Mismatch when loading data between Date and Timestamp

Thank you, planning a test session next week! -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Schema-Import-Utility-Mismatch-when-loading-data-between-Date-and-Timestamp-tp3790p4152.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Unexpected SQL error when running sql with conditions

Thanks, I will try as you suggest to see what it does! I assume the changes will be hitting a nightly build somewhere next week as well so depending on my availability I might just regenerate using the new code instead. br jan -- View this message in context: http://apache-ignite-users.70518.

Re: Ignite Schema Import Utility - Mismatch when loading data between Date and Timestamp

Thanks, out of office for two days but I will test asap when I'm back! -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Schema-Import-Utility-Mismatch-when-loading-data-between-Date-and-Timestamp-tp3790p3966.html Sent from the Apache Ignite Users mailing li

Unexpected SQL error when running sql with conditions

Hello, As a next step in my tests I am trying to run a sql query via the JDBC driver against my loaded 'activity' cache. A first test works fine: rs = conn.createStatement().executeQuery("select * from activity"); Adding a condition to that results in a weird error, for example: rs = conn.create

Re: Ignite Schema Import Utility - BinaryMetadata mismatch error when using gerenated classes

Thanks, hooked up the jar's and it looks like its loading the data into the cache now! best regards jan -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Schema-Import-Utility-BinaryMetadata-mismatch-error-when-using-gerenated-classes-tp3857p3881.html S

Re: Ignite Schema Import Utility - BinaryMetadata mismatch error when using gerenated classes

Thanks, Is the '1.6.0-SNAPSHOT' available on a maven repo somewhere or do I just download the ZIP and use the extaracted jars? br jan -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Schema-Import-Utility-BinaryMetadata-mismatch-error-when-using-gerenated

Re: Ignite Schema Import Utility - Mismatch when loading data between Date and Timestamp

Thank you! I registered two additional threads for the problems, referring back to this one in terms of generated collaterals, hope that is ok. br jan -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Schema-Import-Utility-Mismatch-when-loading-data-betwee

Ignite Schema Import Utility - Case mismatch between table index and query index defined in generated code

Hello, Continuing my initial mention of this problem in another thread where more information such as DDL and generated code can be found: Looki

Ignite Schema Import Utility - BinaryMetadata mismatch error when using gerenated classes

Hello, I get an error which stops the cache from loading in 'BinaryUtils.mergeMetadata' when it tries to merge two values for the 'nameMlid' field. At a certain point it generates a mismatch error because newFieldTypeName is set to long and OldFieldTypeName is set to Object. The trace leading to

Re: Ignite Schema Import Utility - Mismatch when loading data between Date and Timestamp

Thanks! For the two other cases (case mismatch on index and binary mismatch), should I start a separate thread or will we continue this in the current one? best regards jan -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Schema-Import-Utility-Mismatch-wh

Re: Ignite Schema Import Utility - Mismatch when loading data between Date and Timestamp

Thanks! About the Long vs long, indeed after experimenting with changing all Long types to long in the generated code I found out that there was a problem when it tried to set NULL on a primitive long. So they should remain Long where NULL is allowed as you indicate indeed (otherwise it would caus

Re: Ignite Schema Import Utility - Mismatch when loading data between Date and Timestamp

In addition to the above, I also find it strange that it generates both long and Long types for what seem to be very similar fields, for example: /** Value for predecessortypeEnumid. */ private long predecessortypeEnumid; /** Value for successortypeEnumid. */ private long successo

Re: Ignite Schema Import Utility - Mismatch when loading data between Date and Timestamp

Hello, Please find the attached script to create the table and the generated pojo file. I also included an insert for the record which is giving problems, in case the data matters. This is running against an Oracle Database 11g Release 11.2.0.1.0 activity_DDL.txt

Ignite Schema Import Utility - Mismatch when loading data between Date and Timestamp

Hello, I am experimenting with the auto schema generator functionality and experience the following issue. I have a table with a declared 'DATE' column (Oracle). When loading the cache it actually gets a 'Timestamp' typed value from the recordset. Looking in the following method I see no logic to