New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ignite Thin client Index Query is not working with Ignite Server and client version : 2.16.0 #11310
Comments
Please provide full stack trace of the error. The text |
Thanks @ptupitsyn for quick response . Please find the stack trace .
I cross checked the code the text failed to process request is coming as response from the ignite server. |
Root cause is still not clear. We should either find the problem in the server logs, or enable |
I am using ClientConfiguration to initialise ignite, not find appropriate method to set sendServerExceptionStackTraceToClient method. public static ClientConfiguration getServerConfiguration(String[] clusterNodes, int connectTimeout, int retryLimit) { |
@timoninmaxim @yurinaryshkin @ptupitsyn |
|
thanks a lot @ptupitsyn , Please find the complete error logs from server org.apache.ignite.client.ClientException: Ignite failed to process request [768]: com.cisco.cjp.cache.model.EntityValue Please let me know what I am missing in the configuration. |
Looks like a bug in thin client index query - it tries to deserialize data on the server side, which is not only inefficient, but also can fail like this because client classes are not available. We should always use Line 158 in a225705
|
@timoninmaxim @alex-plekhanov could you please have a look? See my previous comment for details. |
@ptupitsyn @Manojred1236 Thanks for the report! I'll have a look. |
Thanks @ptupitsyn @timoninmaxim , One question with the index query will it possible to fetch only required fields ? example from the EntityValue pojo I want to fetch only dtoJson, will it possible ? if possible please point to example. |
@ptupitsyn , Do we need to define the index query entity before the cache creation ? what if the cache is already available will the index query take into effect(Tested looks like not taking into effect) do we need to stop and start the ignite server in order to take index query take into effect ? Is there any possibility to take index query entity take effort without restarting the ignite server ? |
You don't have to restart the server, just make sure indexes are set up correctly for the cache. |
When data available in cache fetching the data from cache using Index query throwing below error
org.apache.ignite.client.ClientException: Ignite failed to process request [19]: com.cisco.cjp.cache.model.EntityValue (server status code [1])
Where there is no data exist in cache the response contain empty. not faced above mentioned issue.
Ignite Configuration
Entity Value
Index Query
Not finding a appropriate logs/reason why the index query not working with Thin client
Please assist if there are any configuration changes required.
The text was updated successfully, but these errors were encountered: