NearCache can be used through ODBC interface

Hi Val, LocalCache works well with ODBC interface. But Is there any issue using the NearCache through ODBC interface? Please give me descriptive idea about how to use it via ODBC interface. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/NearCache-can-be-used-thr

Re: NearCache can be used through ODBC interface

Hi Kumar! You can use ODBC interface for querying to any cache. But keep in your mind that Ignite SQL engine sends request on all nodes and data will be got from usual cache (not near). Thanks, Nikolay. On Wed, Jan 4, 2017 at 11:31 AM, Navneet Kumar wrote: > Hi Val, > LocalCache works well wit

NOT IN in ignite

HI, As per ignite documentation, IN operator does not use index and has to be use as *join table.* Hoping this holds good for* NOT IN *operator as well. String sql = "SELECT p.* from PERSON_CACHE.PERSON p join table(joinId varchar(50) = ?) i on i.joinId = p.personId join table(joinId varchar(50

Re: Affinity

Hi Sergi, Did you get a chance to look into it ? Thanks.

Re: Affinity

Hi, The query should work because everything is colocated. If not, then it would be nice to have a self contained test case. Sergi 2017-01-04 14:08 GMT+03:00 Anil : > Hi Sergi, > > Did you get a chance to look into it ? Thanks. >

Re: NOT IN in ignite

Your query is wrong: Joined rows will produce a cartesian product of all the row pairs, thus you will have a row Person[100, 'Name100'] that correctly passed the first join and paired with n['Name200'] in the second join. Since 'Name100' <> 'Name200', it will be correctly returned in the result se

Re: NearCache can be used through ODBC interface

In that case I cannot read the records from near cache using the Near cache. Is it true? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/NearCache-can-be-used-through-ODBC-interface-tp9859p9865.html Sent from the Apache Ignite Users mailing list archive at Nabble

Re: NOT IN in ignite

I am not clear how joined rows produce cartesian product. Can you please correct the query ? thanks. On 4 January 2017 at 17:06, Sergi Vladykin wrote: > Your query is wrong: > > Joined rows will produce a cartesian product of all the row pairs, thus > you will have a row Person[100, 'Name100']

Re: NOT IN in ignite

> I am not clear how joined rows produce cartesian product. > I guess you have to learn SQL then: https://en.wikipedia.org/wiki/Join_(SQL) https://en.wikipedia.org/wiki/Cartesian_product > > Can you please correct the query ? thanks. > > Just use NOT IN, <> will not use index anyways. Sergi

Re: NearCache can be used through ODBC interface

SQL query distributed on whole cluster, near cache not needed for it. Records will be read on data node (usually cache, not near) in any case for queries and usage data from near cache will not provide performance benefit. On Wed, Jan 4, 2017 at 2:43 PM, Navneet Kumar wrote: > In that case I can

Invalid message type: -84 error

I'm evaluating Ignite and am currently the exception Inavlid Message type: -84 when the topology changes on the Ignite cluster. I'm using the default-config.xml on Ignite version 1.7. Ive setup 2 servers to each have an ignite server node on them, and the nodes are "seeing" each other (after a very

Re: Invalid message type: -84 error

Hi, Could you provide reproducible example? On Wed, Jan 4, 2017 at 3:12 PM, mark_balmer < mark.bal...@moodinternational.com> wrote: > I'm evaluating Ignite and am currently the exception Inavlid Message type: > -84 when the topology changes on the Ignite cluster. I'm using the > default-config.x

Re: Invalid message type: -84 error

As mentioned I have two physical windows servers (server1 and server2), each is running Ignite by using the Ignite.bat file. Each is using the default-config.xml setup. Although on server2 the default-config.xml has got the following TcpDiscoverySpi properties set so that it can "see" the ignite no

Re: Invalid message type: -84 error

An update on this, it seems I can only get the exception if I have the second node in the cluster. If I just run the Java code against a single server node it doesnt throw the error. However, it still takes a very long time to connect. Here is the output from the topology change in the console, it

Re: Invalid message type: -84 error

I see that ports from 47100 to 47109 enlisted in ip finder. By default the addresses used by CommunicationSpi. Could you leave only one port range? 192.168.10.231:47500..47509

Re: Invalid message type: -84 error

Nikolai, thanks for the response, i've corrected those two points and the issues are resolved :) Thanks -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Invalid-message-type-84-error-tp9869p9874.html Sent from the Apache Ignite Users mailing list archive at Nabbl

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

Re: Affinity

Thank you Sergi. i will double check this again from my side. On 4 January 2017 at 16:50, Sergi Vladykin wrote: > Hi, > > The query should work because everything is colocated. If not, then it > would be nice to have a self contained test case. > > Sergi > > 2017-01-04 14:08 GMT+03:00 Anil : > >

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: Old AWS SDK version, why?

Chandresh, thanks for taking this over! Please update all the modules then which are ignite-aws, ignite-gce and ignite-clouds. The modules are listed in the ticket. As for testing, you need to run corresponding tests on TeamCity which has all required keys. Otherwise, you need to create a pers

Re: Old AWS SDK version, why?

Thank you for pointing to the Github discussion, Denis. If I understood it correctly, it doesn't apply to my case (at least according to my understanding of the topic). I've checked the expire properties of the S3 objects, and they are not set: Expiry Date:None Expiration Rule:N/A Al

Re: Cluster hung after a node killed

Thanks Val. Ticket has been fixed for 1.9, Any idea when 1.9 will be available? -Sam -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Cluster-hung-after-a-node-killed-tp8965p9880.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Near cache can be used with SQL Database

The answer is here: http://apache-ignite-users.70518.x6.nabble.com/NearCache-can-be-used-through-ODBC-interface-td9859.html -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Near-cache-can-be-used-with-SQL-Database-tp9805p9881.html Sent from the Apache Ignite

Re: Affinity

The thread continues here: http://apache-ignite-users.70518.x6.nabble.com/Affinity-td9744i20.html -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Affinity-tp9744p9882.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Cluster hung after a node killed

Sam, There is no exact date as for now. I would recommend to monitor the dev list for activity around this. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Cluster-hung-after-a-node-killed-tp8965p9883.html Sent from the Apache Ignite Users mailing list arc

Re: Old AWS SDK version, why?

Chandresh has just updated the SDK version and I’ve merged the changes to Ignite’s master branch https://issues.apache.org/jira/browse/IGNITE-4519 You can build the project from sources and check if the SDK version was a cause of your issue.

grouped index sort vs filter

I have an object with fields member_id, name, and priority. I have created a grouped index on member_id+ name and member_id + priority. I want to run queries like "select * from table where member_id = 123 order by member_id, priority asc. The problem is that sometimes the query optimizer choose

Re: grouped index sort vs filter

Currently there is no way to manually control which index to use. Do you see a difference in performance? I'm not sure ordering is taking advantage of the index there in any case. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/grouped-index-sort-vs-filter-

Re: Ignite with Cassandra questions / errors

Ok, I took a look at the *HistoryResult* implementation once again and found the reason. Your java class should follow JavaBeans Conventions . The most important here is that you class should implement getters/setters methods for READ/WR

答复: 回复：BinaryObject and String.intern

Hi dkarachentsev, Suppose I have a String array and array length is 1000. There are many duplicated values and only five distinct values in the array. We store them using blow ways, which one save memory most? #1 List #2 Map In client side, #2 will save mem

Re: 答复: 回复：BinaryObject and String.intern

Hi, Shawn. Some time ago I created issue "Provide some kind of pluggable compression SPI support" [1] But it is not implemented yet. May be in Ignie 2.0 there could be some kind of such API. See discussion [2] [1] https://issues.apache.org/jira/browse/IGNITE-3592 [2] http://apache-ignite-develope

compute SQL returned data.

Hi experts, I want to compute the SQL returned data on the server side. Is there any examples? Thanks Shawn

Re: 答复: 回复：BinaryObject and String.intern

Hi Shawn, BitSet will be marshaled using BitSet.writeObject() serialization implementation. In other words, if this approach saves your memory in heap, it will save it in Ignite as well. If you save collection of strings, Ignite will not check for duplicates as JVM does, and as mentioned Alexey,

Re: compute SQL returned data.

Hi, I'm not sure that undestrand what do you want. Could you describe your case more details? Also you can find examples on here: https://github.com/apache/ignite/tree/master/examples/src/main/java/org/apache/ignite/examples On Thu, Jan 5, 2017 at 10:20 AM, Shawn Du wrote: > Hi experts, > > > >

Re: compute SQL returned data.

You can use compute tasks [1], in which invoke SQL query and process results. [1] https://apacheignite.readme.io/docs/compute-grid -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/compute-SQL-returned-data-tp9890p9893.html Sent from the Apache Ignite Users mailin