Re: Ignite thick client triggering PME in 2.8.0 ?

Hi, can anyone please check and respond on this..appreciate your help in advance -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Ignite thick client triggering PME in 2.8.0 ?

https://cwiki.apache.org/confluence/display/IGNITE/%28Partition+Map%29+Exchange+-+under+the+hood As per the documentation, if we are using apache ignite thick client 2.8 and above, it should not trigger PME in server nodes. But it does not look like it is skipping, I see below logs INFO 2021-02-

Issue with ignite thin client - ReliableChannel

Ignite thin client create and use ReliableChannel which starts below async thread, but while closing the channel it is not shutting down this executor service thread. This should be fine if jvm shutsdown, but it will be a problem for applications sharing jvm node. Ex: 1 JVM has multiple application

Re: Ignite 2.9 one way client to server communication

Can you please check above questions and help me out -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite 2.9 one way client to server communication

Thank you for response. If I understand correctly, so thick client connectivity time is not depending on # of server nodes, it all depends on PME length ? Can you please elaborate or point me to the resources where I can understand PME length ? I got few links on how PME works. But sorry I did not

Re: Ignite 2.9 one way client to server communication

Thank you Stephen and Ilya for your response. Please find my server and client config and let me know if I a missing anything which is causing these delays. We have 8 jvm server nodes running on Ignite 2.8.0 with 4gig each and each node is on separate host. We have 60 client nodes (Ignite 2.8.0) u

Ignite 2.9 one way client to server communication

I see that ignite 2.9 has added support for one-way thick-client to server connections. Does it reduce the time taken to connect thick client to server and provides all thick client functionalities? Does client still be in ring? Right now we r facing issues with thick client where it is taking more

Planning to pick Ignite 13006

Hi, I am interested to pick https://issues.apache.org/jira/browse/IGNITE-13006 and work on it. Please let me know for any constraints to pick it up. I see fix version on this as 2.10, but I do not see any branch created. Could you please let me know if we are planning to start 2.10 and is it the ri

Ignite thin client add column and index dynamically

I have seen that if I provide query entities in cache configuration I am able to query by column. But when I execute ALTER TABLE ADD COLUMN programmatically its not working with java thin clients where its working fine with thick clients. Java Thin clients supports sqlfieldquery then why not alter

Re: Apache ignite evolvable object

Does it save additional bytes by default or do we have to implement binarylable, if so do you have any example. If it does by default, does that mean, let's say if I send data from new version node to old version node and send the same data back to new version node will it preserve thos new field

Apache ignite evolvable object

I am using apache ignite 2.8.0. Looking for an option to have evolvable data model similar to coherence (com.tangosol.io.Evolvable). Do we have any ? Idea is to save future data if the domain model version is backward compatible and when the same model is transferred to new version, we can retrieve

Custom IgniteConfiguration does not work

I am trying to extend IgniteConfiguration class and try to enhance its properties as I needed them for some custom checks. I have created config like below and started using Ignition.start() But when I call GridKernalContext.config() I am not getting MyCustomIgniteConfiguration instance. I am stil

Pause ignite grid communication

Once the grid started, I am performing some customized post process setup. It takes about 10 milliseconds. During this 10 millis I want to pause any grid communication from other nodes (server/client) like adding any new fields or queries. Is there any way to pause grid communication once it starte

Re: Failed to start near cache (a cache with the same name without near cache is already started)

I have disabled copyonread and the time taken to getAll() reduced to 1/3. Earlier it was 300 ms on 10k entries and now it is 100ms. Is disabling copyonread is fine ??? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: How sql works for near cache

Is there any way we can get complete keyset or values from a near cache. Something like cache.keyset() -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

How sql works for near cache

If I run sql with out where condition on near caches, query will hit server node correct ? It wont fetch from near cache in local node. Is this a true statement? Ex: select _key from cachename; -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Failed to start near cache (a cache with the same name without near cache is already started)

Thank you. I am not getting this error now. But not sure if something wrong with config. When I call getAll(all keys) on near cache, then the performance is worse than regular cache. If regular cache getAll() is taking 100ms then near cache getAll() is taking 330 ms. Its almost 3 times. I am expect

Failed to start near cache (a cache with the same name without near cache is already started)

I followed the below post http://apache-ignite-users.70518.x6.nabble.com/Failed-to-start-near-cache-a-cache-with-the-same-name-without-near-cache-is-already-started-td18322.html but it did not solve my problem, hence requesting for help. I tried two options a) Start ignite with below xml config a

Re: Issue with adding nested index dynamically

Can anyone please check above comment and update. Thanks -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Issue with adding nested index dynamically

Hello, I tried to go to internals and override GridQueryProcessor but somehow I do not feel like clean solution. Just had another thought...whatever code I have written and created a pull request for, shall is surround it with -D arg like nested_field_experimental_feature or with better system prop

Benefits of near cache other than get() ?

What are the operations, out of below, that are purely benefited by near cache. When I tested it other than get() I do not see any benefit of near cache. All the other calls are going on network. I thought getAll(), keySet() and entrySet() will be coming from local node, but they are going to serv

Overriding GridQueryProcessor

Hi In order to fix the issue that we are discussing @ http://apache-ignite-users.70518.x6.nabble.com/Issue-with-adding-nested-index-dynamically-tc29571.html I found a workaround to override GridQueryProcessor and use CustomGridQueryProcessor which extends GridQueryProcessor and override few func

Re: Issue with adding nested index dynamically

Okay, so the issue you are facing with is incorrect data type which is valid, so its not an issue then. Yes agreed that it requires more testing, but I feel the fix that is going in, is safe and good to do. This fix is really important for us to proceed further. I have tested few other scnearios a

Re: Issue with adding nested index dynamically

I did not face any issue. Its working fine for me. Can you share your code and exception that you are getting I tried like below and it worked for me. ((Person)cache.get(1)).address.community) -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Issue with adding nested index dynamically

Hello Ivan, please let me know if you get a chance to check the code and merge it.. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Issue with adding nested index dynamically

Sure. Have created one https://github.com/apache/ignite/pull/7016 Can you please check this. It has all the changes at one place. please let me know for any issues. Thank you. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Issue with adding nested index dynamically

Ohh yes you are right. Without the fix, it is failing to query cache. With the other approach that I have attached earlier it failed to join node, there I have CacheConfiguration in xml file for both server and client node. Not sure if that does matters. Either way it is failing Also this is my ba

Re: Issue with adding nested index dynamically

Result should not be same, could you please share your logs. Couple of issues here. 1) *With out fix *- I got null instead of "Address.street" value [[1, Person{name='john', address=Address{street='baker', number=221}}, john, Address{street='baker', number=221}, *null*]] *With fix* [[1, Pe

Re: Issue with adding nested index dynamically

HI Ivan, thanks for the quick reply. Yes it perfectly works as needed with the fix. Person.Address.Street will not work because person.getPerson().getAddress().getStreet() does not exist. It has to be person.getAddress().getStreet(). So column name should be "Address.street" Any other name does

Re: Issue with adding nested index dynamically

I see there are couple of issues with the test 1) cache.query(new SqlFieldsQuery("alter table Person add column \"Address.street\" as street varchar")); - "as" is not supported in sql. So we should remove "as street" and it should be like cache.query(new SqlFieldsQuery("alter table Person add

Re: Does apache ignite support Spring 5.x

Please ignore, its my bad that there is maven dependency issue in my local. Sorry about that -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Issue with adding nested index dynamically

Can you please provide an update -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Does apache ignite support Spring 5.x

I see ignite-spring 2.7.6 comes with 4.3.18.RELEASE. If I exclude these jars and maintain 5.x.RELEASE, it is not working. So does ignite supports only till 4.x release? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Issue with adding nested index dynamically

ignite_bug_share.zip Thanks for the reply. Please find the attached. 1) IndextestIgniteServer1 - starts server 2) IndexTestIgniteClient1 - starts the client 3) I did not add QueryEntities - we have usecase where w

Re: Issue with adding nested index dynamically

Hello Denis/Ivan, can you please check this and if there are no issues can you merge the code. Sorry for the rush. We are getting ready for prod in next 3 months and this is really important for us and we need to test all our functionality as well. It would be a great help if we have this fixed

Re: Issue with adding nested index dynamically

Hello Ivan, can you please check and provide updates on this -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Issue with adding nested index dynamically

Can you please provide any update in this... -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Issue with adding nested index dynamically

Hello Ivan, to be more specific, if I want add field "Users.userName" - current ignite version 2.7.6 is setting the field name as "Users.userName" and default alias name as "userName" with which makes it non-queryable, non -indexable and issues during restart due to mismatch in configuration . Bu

Re: Issue with adding nested index dynamically

Thank you. One more thing to add - it is able to add index dynamically only thing is, when I restart the client it is not able join the cluster due to incorrect alias -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Issue with adding nested index dynamically

Sorry for the push. This is a major blocker for us. We have coherence clients where they can add indexes dynamically and we want to move them to ignite in next 3 months. Coherence has a way to add indexes dynamically and ignite also does supporting it. This issue exists event with QuerySqlField. If

Re: Issue with adding nested index dynamically

My apologies for multiple replies. Please consider latest reply -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Issue with adding nested index dynamically

I have tested with adding QuerySqlFields as well, it is enabling to add dynamic field and indexes on nested objects but if I restart the client again it is not able to join the grid because it is not able to find this column. But with the fix and maintaining proper aliases we are able to add fields

Re: Issue with adding nested index dynamically

ignite_bug_share.zip I have tested by adding QuerySqlFields as well, with or with out it, it is working when I add it, but if I restart the client it is not able to identify nested columns as its alias is null or n

Re: Issue with adding nested index dynamically

ignite_bug_share.zip I have tested by adding QuerySqlFields as well, with or with out it, it is working when I add it, but if I restart the client it is not able to identify nested columns as its alias is null or not

Re: Issue with adding nested index dynamically

Added test case and created pull request. Please check both the code changes under pull request #6949 and test case pull request #6955 and let me know for any suggestions. Thank you. IGNITE-12261 - Issue with adding nested index dynamically - Adding tests #6955 -- Sent from: http://apache-ignit

Re: Issue with adding nested index dynamically

Sure, will add test case. My domain model is existing domain model and I cannot change or add @QuerySqlField to my domain model. I am trying to achieve dynamic index creation on any domain model object (pojo) irrespective @QuerySqlField's -- Sent from: http://apache-ignite-users.70518.x6.nabbl

Re: Issue with adding nested index dynamically

https://github.com/apache/ignite/pull/6949 Created pull request with suggestion. Can you please check and close -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Issue with adding nested index dynamically

I have made changes and created pull request. Can you please check and let me know if there are any issues with the commit. Otherwise can you please let me know when it can it be available in maven repo so that we can start pulling it in our organization https://github.com/apache/ignite/pull/6947

Re: Issue with adding nested index dynamically

https://issues.apache.org/jira/browse/IGNITE-12261 I have created JIRA. Please let me know how I can assign to myself. My username on jira board is "kotari" -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Issue with adding nested index dynamically

We have to add indexes on cache dynamically on java pojo with nested objects. In the below example we do not have @QuerySqlField. In this case if I try to add index on "username" dynamically using "CREATE INDEX" it worked. But if I want to add index on "Address.zipcode" - this is not working as we