Hi Kevin, This is right, JARs in libs folder are added to node classpath on startup and replacing them in runtime doesn't have any effect.
However, you don't need to deploy your POJOs on server nodes. Ignite stores all its data in binary format (see [1] for details) and never serializes it on the server side unless you explicitly ask for this. CacheJdbcPojoStore automatically detects if there is a class available and uses BinaryObjectBuilder if it's not. You can then provide DB query that will be used to load the data in loadCache() method parameters, so you can define the list of fields to load. Take a look preload() method in [2] to see how this can be done. Let me know if you have more questions. [1] https://apacheignite.readme.io/docs/binary-marshaller [2] https://github.com/apache/ignite/blob/master/examples/schema-import/src/main/java/org/apache/ignite/schema/Demo.java -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/jar-file-update-issue-in-ignite-server-side-tp4401p4428.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
