Re: Apache Ignite "work" folder for clients

Thanks, much appreciated. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Apache Ignite "work" folder for clients

Ok, thanks. Next question. Is there an example of an xml config setting for this? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Apache Ignite "work" folder for clients

Is there a way to configure a separate "work" folder for Apache Ignite based on the clients or is the "work" folder hard-coded to only be at the server level itself?Kenan -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Apache Ignite & Cassandra configuration with code?

Is it possible to fully configure the connection between Apache Ignite v2.3 & Cassandra? I started the Cassandra Integration with 1.8 and, at the time, the configuration had to be done fully with xml. I'm just curious if there have been enough changes and updates over time (that I'm unaware of) t

Re: SqlQuery with Cassandra cache

I was starting to think that was the case. Thanks for the help and verifying that for me, Val. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

SqlQuery with Cassandra cache

Can someone explain to me what I'm doing wrong? I'm trying to query an Ignite cache backed up by Cassandra, but I keep getting the following error. Can a SqlQuery be created against a C*-backed cache? I would think so, but not sure exactly how and there are no good examples that I can find in th

Re: Ignite/Cassandra failing to use supplied value for where clause

Ok. The "transient" keyword was the issue. It was a holdover from something else (a previous example that I was using as my basis for this), most likely. Here are the results from the run once I removed "transient" from all of the fields in both Test1Key & Test1: >>> Read from C* (get). Key: [

Re: Ignite/Cassandra failing to use supplied value for where clause

I don't see how because this is what's in the table. And the code specifically sets the "myId" to a value before it runs. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite/Cassandra failing to use supplied value for where clause

Hi Andrey, I tried taking pieces from your example and I still couldn't make it work. First, I removed the annotations out of the POJOs and physically mapped the information in the persistence settings. Still got the error with "my_id". Second, I tried adding the QueryEntity xml config you had.

Re: Ignite/Cassandra failing to use supplied value for where clause

So can someone try to take my example and actually get it to work? It's baffling to me why this fails as it does. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite/Cassandra failing to use supplied value for where clause

Yeah, sorry about the confusion. I was playing around with the field names to see if that was a possible issue and had refactored the "Test1Key.id" field to "Test1Key.myId". It should have been "myId" originally since the column name was "my_id" (see the updated Test1Key below). I'm just not get

Re: Ignite/Cassandra failing to use supplied value for where clause

I don't understand what the reasoning behind manually setting the IndexedType pair in the configuration. Yes, this is a field that is indexed, but the problem is that it's not correctly pulling the data from C* and it's worked in the past with other C* tables/caches via @Annotation without the nee

Re: Ignite/Cassandra failing to use supplied value for where clause

These were included in the project file link in the initial post. Here they are in text for reference. The only thing not posted is the pom.xml and it's just standard SpringBoot Ignite w/ Cassandra. cassandra-ignite.xml test1-cassandra-persistence-settings.xml cassandra-connection-settings.xml Te

Re: Ignite/Cassandra failing to use supplied value for where clause

Here's the C* setup: -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Ignite/Cassandra failing to use supplied value for where clause

I've got to be missing something simple here, but I'm having trouble with Ignite calling C* with the POJO key that I'm supplying it when it tries to "cache.get". Whenever I try to supply the "cache.get" method with my POJO key, it complains that it's null when it tries to execute the CQL. I've in

Re: Cassandra failing to ReadThrough using Cache.get(key) without preloading

Ok, that worked for me, too. Such a small change that I kept overlooking. Thanks a lot! -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Cassandra failing to ReadThrough using Cache.get(key) without preloading

Any other thoughts? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Cassandra failing to ReadThrough using Cache.get(key) without preloading

I forgot to post the output: -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Cassandra failing to ReadThrough using Cache.get(key) without preloading

Ok, I see that now. It turns out that this /*is*/ the correct data and SQL INSERTS. This is a test table copied from an existing working table and these are the correct values that are in the working table as well. I changed the hashCode() & equals() methods to account for the potential "null" v

Re: Cassandra failing to ReadThrough using Cache.get(key) without preloading

I provided the correct classes above and the CQL statements are 100% correct. Please see below to know how the data relates to each column. It looks like you're skipping over 1 of the first 5 columns when reading through which is why you see a null starting at col5 rather than starting at col6.

Re: Cassandra failing to ReadThrough using Cache.get(key) without preloading

That would make sense if col5 was null, but it's only col6 & col7 that are null and they are both String columns which allow for null. In addition, if col5 was null, then the cache wouldn't load upon doing a manual load which it does. Also, just in case, I went ahead and changed the "long" types

Web Agent 2.1.3 giving message "You are using an older version of the agent."

I've pulled the latest docker image and web-agent (2.1.3) and am running against 2.1-bin code, but whenever I try to connect, all I get is the following: [2017-09-06 07:49:30,891][INFO ][main][AgentLauncher] Starting Apache Ignite Web Console Agent... Agent configuration: User's security tokens

Re: Cassandra failing to ReadThrough using Cache.get(key) without preloading

I made that change and the result was the same, so it looks like it's not creating a new cache with the getOrCreateCache() method. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Cassandra failing to ReadThrough using Cache.get(key) without preloading

FYI, my update wasn't that my problem was solved, but that the website got rid of the work that I did to post the code. Please take a look at the code that I've posted yesterday because I'm still having the issue. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Cassandra failing to ReadThrough using Cache.get(key) without preloading

Trying this again... OUTPUT Output From Not Preloading the Cache: Output From Preloading the Cache: CODE cassandra-ignite.xml persistence-settings.xml persistence-settings.full.xml (Tried in case I needed to fully define in thexml) connection-settings.xml TestResponseKey TestResponse ApplicationCon

Cassandra failing to ReadThrough using Cache.get(key) without preloading

Starting this thread over. I think it will help to actually mark the thread as "HTML Format" to get all of my changes. (I accidentally deleted the last thread when I was trying to just delete my last reply) OUTPUT Output From Not Preloading the Cache: Output From Preloading the Cache: CODE cassan

Re: Cassandra failing to ReadThrough using Cache.get(key) without preloading

Ok, I'm going to try this again... OUTPUT Output From Not Preloading the Cache: Output From Preloading the Cache: CODE cassandra-ignite.xml persistence-settings.xml persistence-settings.full.xml (Tried in case I needed to fully define in the xml) connection-settings.xml TestResponseK

Re: Cassandra failing to ReadThrough using Cache.get(key) without preloading

Wow. Ok. After I spent about 30-45 minutes getting it put together and looking pretty, too. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Cassandra failing to ReadThrough using Cache.get(key) without preloading

According to everything that I've read, hooking up Cassandra with Ignite should allow for doing a lazy load of the Cache using the Cache.get(key) without using "loadCache" beforehand. However, using Ignite v2.1, I'm not seeing that occur. If I use "loadCache", then my "get" returns values appropr

Re: PCF tile for Ignite

We've got the desire to run Ignite containerized within PCF instead of Docker. We have an ELA with Pivotal . Are there examples on running Ignite within PCF? I'm not sure I know exactly where to begin. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/PCF-tile-f

Re: Ignite to Cassandra change from 1.9 to 2.0

Thanks, Igor. We look forward to the next version coming out. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-to-Cassandra-change-from-1-9-to-2-0-tp13099p13470.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite to Cassandra change from 1.9 to 2.0

Ok, I have finally been able to get back to this. First, I switched the @QuerySqlField annotations back to the fields from the setters as instructed. Then I executed with a minimal persistence settings xml file which only defined the strategy as POJO, but did not specify the field/column combinat

Re: Ignite to Cassandra change from 1.9 to 2.0

First, I do have setters on the class, just didn't include them for space reasons. Second, this is the exact opposite from what I was told originally back January for v1.8. So, this looks like it was a breaking change introduced in v2.0. I haven't checked the latest "what's new" recently. Was t

Re: Ignite to Cassandra change from 1.9 to 2.0

I upgraded from Ignite 1.9 to Ignite 2.0 and this started happening. The stacktrace is below. Also, I'm including the .sh script that I'm running so you can see that the only difference between the executions is pointing to v1.9 versus pointing to v2.0. My code didn't change, but it fails in 2.0

Ignite to Cassandra change from 1.9 to 2.0

I've just upgraded to the new version 2.0 from 1.8/1.9 with a Cassandra .xml configuration as the backing data-store. However, v2.0 is failing to pull the column name that's tied to the field name in the persistence definition. Because of that, the CQL being generated is trying to call Cassandra

Re: WebConsole local install (v1.9) help needed

It looks like it's working now. I think it was a proxy issue. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/WebConsole-local-install-v1-9-help-needed-tp12086p12090.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

WebConsole local install (v1.9) help needed

I'm having trouble with the WebConsole on my local Windows environment. I've done "npm install --no-optional" for both the "backend" and "frontend" and "npm start" for the "backend". However, whenever I try to do "npm run dev" for the "frontend", it doesn't look like it finishes. It gets to the

Re: Ignite with Cassandra questions / errors

Ah, now I understand. That worked. Thanks! -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-with-Cassandra-questions-errors-tp9607p9913.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite with Cassandra questions / errors

That really wouldn't be the cause. I didn't actually include the full bean class implementations in the initial post in order to save space, but they are actual fully-realized beans. Here are their actual implementations. == import org.apache.ignite.cache.affinit

Re: Ignite with Cassandra questions / errors

Ok, so I got my code working reading/inserting/updating from/to C*, but I had to manually set up the persistence.xml as below and change my java.sql.Timestamp types in the class to java.util.Date types. comment = 'Test table for Ignite/Cassandra connection'

Re: Ignite with Cassandra questions / errors

This is what I remember reading in the docs as well. However, I just ran the DDLGenerator using my Cassandra-persistence-settings.xml file and the following is what it generated. So, either I don't have something set up correctly for Ignite to recognize the Annotations, or there's a problem in th

Ignite with Cassandra questions / errors

Hi. I have 2 questions regarding Ignite & Cassandra. I'm using Ignite v1.8 I'm trying to get a very simple example working with read/write through to c*, but I'm having some difficulty. First, I'm trying to use the POJO strategy of configuration for both the key & value persistence with the cla

Re: Online documentation

As stated in the original post, the Cassandra Examples page (https://apacheignite-mix.readme.io/docs/examples). The "read-through and write-through" and "write-behind" (pasted in original post) links among others on the site. -- View this message in context: http://apache-ignite-users.70518.x6

Re: Online documentation

Ok, that makes sense. But there are a lot of links on the "-mix" site that don't work and send you to a 404 Page Not Found error page. This is why I'm posting. I think the links are using the "current site" location, which is the "-mix" site, but are located at the normal non-mix site and thus u

Online documentation

With the move to v1.8 there are a lot of broken links in the online documentation (example: Cassandra Examples page for v1.8 - This link doesn't work: https://apacheignite-mix.readme.io/v1.8/docs/persistent-store#write-behind-caching). The old online documentation pointed to apacheignite.readme.i

Javadoc at GridGain website is at version 1.6 instead of 1.7.1

The Javadoc link at the GridGain website hasn't been updated to the latest release of 1.7.1 and is still referring back to v 1.6.0. This is the link " https://ignite.apache.org/releases/1.6.0/javadoc ". -- View this message in context: http:/

Re: Argument Type Mismatch for Oracle CLOB

Thanks, Alexey. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Argument-Type-Mismatch-for-Oracle-CLOB-tp7748p7774.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Argument Type Mismatch for Oracle CLOB

I found the git IGNITE-3394 entry on the web.However, the "type" looks to be a Java class and doesn't really give me anything to go on for a CLOB vs a VARCHAR2. However, I did create a Transformer and plugged it in (or so I thought) to try and see what came through for each field during a debu

Re: Argument Type Mismatch for Oracle CLOB

Is there an example of how this is used/done? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Argument-Type-Mismatch-for-Oracle-CLOB-tp7748p7767.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Argument Type Mismatch for Oracle CLOB

I'm getting an "argument type mismatch" for my Oracle CLOB when trying to call "loadCache". I ran into similar situation like this before with Oracle Timestamp when using version 1.6 of the ignite fabric and had to upgrade to the 1.7.0 version of the ignite fabric to fix that defect. This looks v