Hi Alexey,
Sorry for delayed response.
For point 1, the reason i need is when a service fetches & returns pojos,
if the key is not a member of the pojo (in our case the keys are java
int/long type) how else will the client who consumes the pojos know their
id/keys.
On point 2, I will try as you
Hi Vasiliy,
Thanks for responding. I had figured that issue a few days back & have
already deployed ignite (not released in prod yet). I am sorry i should
have updated the team here. Sorry about that & thanks for helping.
I did find one other issue w.r.t to writing/reading to PostgreSQL json
Hello @mlekshma.
In process of your github project debugging I notice that you use a wrong
version of H2 dependency.
A version in you project is 1.4.193. But with Ignite 2.1 you should use
1.4.195 version of H2.
Also pom.xml file contains commented valid version of H2.
When I change H2 library
Hello @mlekshma.
I will try to fix you problem tomorrow.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Trouble-using-latest-Ignite-Web-Console-2-1-tp15929p16202.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Muthu,
1) If you declare id in your POJO you will consume memory twice, because id
is already a key that will be used to put into cache.
Do you really need this?
2) Actually you could do this with web console, but a bit tricky...
Go to "Summary screen" -> Scroll down to "Client" section -> Click
Hi Alexey,
Just to add a little more context & summarize...I have been really trying
to get this to work for a while so i can begin deploying ignite but as yet
i haven't manged to get this working...below are the current list of issues,
1. The cache fails loading with the configurations
Hi Alexey,
Try this,
https://github.com/softwarebrahma/IgniteCacheWithAutomaticExternalPersistence
Can be run like below,
java -jar -Ddb.host=localhost -Ddb.port=5432 -Ddb.name=postgres
-DIGNITE_QUIET=false target\CacheAutomaticPersistence-0.0.1-SNAPSHOT.jar
Regards,
Muthu
-- The real danger
Hi Andrey,
The latest version worked for the connection. However when i try to import
domain models from my database it fails past the schema selection
page..once i select my database and hit next it doesn't show my two tables
that i have in that. Also when i select all (instead of my specific
Thanks Andrey...I did use the latest..also i validated the token without
which the agent doesn't even connect (btw i couldn't initially get the
web-agent version downloaded from console.gridgain to connect to web
console...it failed complaining version mismatch...then i took the version
from
Hi Muthu,
Do you use following image (in console execute following command: "docker
images")?
REPOSITORYTAGIMAGE ID
apacheignite/web-console-standalone latest ae3d24152e68
Also, please validate token in agent
Hi Folks,
First a big thanks for making the latest version of web console available
on docker hub (https://hub.docker.com/r/apacheignite/web-console-standalone/).
As i understand this has fixes for some issues i encountered with ignite
2.0 version
I tried it but unfortunately it looks like this
11 matches
Mail list logo
