RE: Example for server client configuration in ignite

2018-09-03 Thread Sriveena Mattaparthi
Hi, Please point to some reference on the below questions. Thanks & Regards, Sriveena From: Sriveena Mattaparthi Sent: Friday, August 31, 2018 4:24 PM To: user@ignite.apache.org Subject: RE: Example for server client configuration in ignite Hi Evgenii, In the document mentioned on Result Set

Fulltext matching

2018-09-03 Thread Courtney Robinson
Hi, We've got Ignite in production and decided to start using some fulltext matching as well. I've investigated and can't figure out why my queries are not matching. I construct a query entity e.g new QueryEntity(keyClass, valueClass) and in debug I can see it generates a list of fields e.g. a,

Re: ignte cluster hang with GridCachePartitionExchangeManager

2018-09-03 Thread Ilya Kasnacheev
Hello! The operation will execute after partition map exchange (or maybe several ones). Just be sure to avoid waiting on operation from discovery event listener. Regards, -- Ilya Kasnacheev пн, 3 сент. 2018 г. в 17:37, wangsan : > Thanks! > > Can I do cache operations(update cache item) in

Re: ignite cluster management

2018-09-03 Thread Ilya Kasnacheev
Hello! I think you can have a singleton service that periodically checks the attributes() for all nodes. If anyone is amiss from previous runs, try to re-start it. Be sure to use 'exclude neighbours' cache affinity setting when having multiple server nodes on same machine to avoid data loss.

Re: .net entity based configuration / datetime field error

2018-09-03 Thread Som Som
I’m connecting to the server node via DBeaver (connection settings\ jdbc url - jdbc:ignite:thin://xxx.xx.xx.xx/). I can query DateTime field if I use Attributes Based Configuration and I get an error mentioned below in case of using QueryEntity Based Configuration. How to configure a cache with

Re: ignite cluster management

2018-09-03 Thread wangsan
1. Note that you will have problem writing to caches when topology changes. Why not just query ignite.cluster(), expose node traits as node.attributes()? >> Yes, I use attributes for node join. But I want to know the stopped >> nodes(when node left) . Then I can do some operations such as

Re: .net entity based configuration / datetime field error

2018-09-03 Thread Igor Sapego
Which exactly ODBC driver are you talking about? Best Regards, Igor On Mon, Sep 3, 2018 at 4:48 PM wt wrote: > not sure if it helps but the odbc driver doesnt play nice with date fields > and deals with them in binary format > > class org.apache.ignite.binary.BinaryInvalidTypeException > >

Re: ignte cluster hang with GridCachePartitionExchangeManager

2018-09-03 Thread wangsan
Thanks! Can I do cache operations(update cache item) in another thread from discovery event listeners? And the operation(update cache item) will execute concurrently or execute before partition map exchange? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Query execution too long even after providing index

2018-09-03 Thread Andrey Mashenkov
HI, Have you tried to increase index inlineSize? It is 10 bytes by default. Your indices uses simple value types (Java primitives) and all columns can be easily inlined. It should be enough to increase inlineSize up to 32 bytes (3 longs + 1 int = 3*(8 /*long*/ + 1/*type code*/) + (4/*int*/ +

Query execution too long even after providing index

2018-09-03 Thread Prasad Bhalerao
Hi, My cache has 1 million rows and the sql is as follows. This sql is taking around 1.836 seconds to execute and this time increases as I go on adding the data to this cache. Some time it takes more than 4 seconds. Is there any way to improve the execution time? *SQL:* SELECT id,

Re: error starting Ignite -Failed to activate node components

2018-09-03 Thread Вячеслав Коптилин
Hello, The root cause of the issue is that your Spring configuration is not quite correct. It seems that the `dataSource` property [1] refers to the `dsSQLServer_Sustainanalytics` which cannot be found: Caused by: class org.apache.ignite.IgniteCheckedException: Spring bean with the provided

Re: .net entity based configuration / datetime field error

2018-09-03 Thread wt
not sure if it helps but the odbc driver doesnt play nice with date fields and deals with them in binary format class org.apache.ignite.binary.BinaryInvalidTypeException your error looks to be related - have you tried the jdbc driver as a test? -- Sent from:

error after activating cluster - Failed to wait for completion of partition map exchange

2018-09-03 Thread wt
a Single node cluster starts fine. If i set it to active i get the following error popup (log file) [2018-09-03 13:54:45,187][INFO ][main][IgniteKernal%POC5] >>>__ >>> / _/ ___/ |/ / _/_ __/ __/ >>> _/ // (7 7// / / / / _/ >>>

error starting Ignite -Failed to activate node components

2018-09-03 Thread wt
Ignition.start("C:igniteexamplesconfigpersistentstoreexample-persistent-store.xml"); "C:\Program Files\Java\jdk1.8.0_151\bin\java" "-javaagent:C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2017.3\lib\idea_rt.jar=51729:C:\Program Files\JetBrains\IntelliJ IDEA

.net entity based configuration / datetime field error

2018-09-03 Thread Som Som
Hello. if I use Attributes Based Configuration I can put enitity into the cache via key value api and than read rhis entity through the dbeaver(select * from testentity) *Code:* namespace Example { public class TestEntity { [QuerySqlField] public string ValueString

Re: ScanQuery throwing Exception for java Thin client while peerclassloading is enabled

2018-09-03 Thread Ilya Kasnacheev
Hello! It's not resolved so it's not in Nightly yet! Please check again once it is in Resolved state. Regards, -- Ilya Kasnacheev пн, 3 сент. 2018 г. в 14:25, Saby : > Hi Ilya, > Thanks for your response. > Is the fix included in the Nightly build? I took the nightly build of 3rt > Sep, but

Re: ScanQuery throwing Exception for java Thin client while peerclassloading is enabled

2018-09-03 Thread Saby
Hi Ilya, Thanks for your response. Is the fix included in the Nightly build? I took the nightly build of 3rt Sep, but it didn't work. It(ScanQuery) is still expecting all the pojos and predicate classes in the Server lib when trying to fetch the data using Thin client.

Re: Query 3x slower with index

2018-09-03 Thread Andrey Mashenkov
Hi Actually, first query uses index on affinity key which looks more efficient than index on category_id column. The first query can process groups one by one and stream partial results from map phase to reduce phase as it use sorted index lookup, while second query should process full dataset on

Re: How close client connection to server

2018-09-03 Thread F.D.
Forget it! There was another problem. Thanks, F.D. On Sat, Sep 1, 2018 at 12:11 AM F.D. wrote: > Hi, > > yes I tried and I got the same error. > > On Thu, Aug 30, 2018 at 6:33 PM Ilya Kasnacheev > wrote: > >> Hello! >> >> Have you tried Ignition::StopAll(false); ? >> >> Regards, >> -- >>

Instant data type mapping to SQLServer through Pojo store

2018-09-03 Thread michal23849
Hi, I have a Instant data types in my Ignite data model and I want to map it to SQL Server. I don't have a problem with Date or Time types, but I can't map the Instant one. Is there any way to still map it (even to VARCHAR) or if it is not on the supported data types