date:20170831

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
ApplicationConfig
Application
DATA
Table Info
Inserts




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

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
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
ApplicationConfig
Application
DATA
Table Info
Inserts




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: UPDATE SQL for nested BinaryObject throws exception.

This is a part of the real code that I wrote.

-
  List entities = new ArrayList<>();
  QueryEntity qe = new QueryEntity(String.class.getName(), "cache");
  qe.addQueryField("attribute.prop1", Double.class.getName(), "prop3");
  qe.addQueryField("attribute.prop2", String.class.getName(), "prop4");
  qe.addQueryField("attribute.prop.prop1", Double.class.getName(), "prop5");
  qe.addQueryField("attribute.prop.prop2", String.class.getName(), "prop6");

  BinaryObject bo  =ib.builder("cache").setField("attribute",
ib.builder("cache.attribute")
  .setField("prop",
ib.builder("cache.attribute.prop")
   .setField("prop1", 50.0, Double.class)
   .setField("prop2", "old", String.class))
  .setField("prop1", 50.0, Double.class)
  .setField("prop2", "old", String.class)).build();

  cache.put("key1", bo);
  cache.query(new SqlFieldsQuery("update cache set prop4 = 'new'  where
prop3 >= 20.0"));//OK
  cache.query(new SqlFieldsQuery("update cache set prop6 = 'new'  where
prop5 >= 20.0"));//NG
-

I can update 'prop4' by SQL, but I do not update 'prop6' by SQL. 



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

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


TestResponseKey


TestResponse


ApplicationConfig


Application


DATA

Table Info


Inserts






--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: UPDATE SQL for nested BinaryObject throws exception.

Hi,

Currently referencing nested object's fields from SQL isn't supported for
both regular Java objects and for BinaryObject-s.

In other words, having 

class B {
private String field1;
}

class A {
private B bField;
}

you cannot update it like `update A set bField.field1=?`

Kind regards,
Alex.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: GC stalling all the activity

2017-08-31 Thread dkarachentsev

Hi,

Under batch I understand key-value map that you pass to putAll().

Thanks!
-Dmitry.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: UPDATE SQL for nested BinaryObject throws exception.

2017-08-31 Thread Andrey Mashenkov

Does this work for regular objects?


BWT: looks like a type when you set a builder to field instead of binary
object itself "bb.build()"

On Thu, Aug 31, 2017 at 4:32 PM, takumi  wrote:

> I use SqlQuery for nested BinaryObject.
> The BinaryObject instance is following structure.
>
>BinaryObjectBuilder bb2 = binary.builder("nested2
> hoge").setField("field2", "old", String.class);
>BinaryObjectBuilder bb = binary.builder("nested
> hoge").setField("field1",
> bb2);
>binary.builder("hoge").setField("field0", bb);
>
> The sample SQL to throw an exception is "update " + CACHE_NAME + " set
> field2 = 'new'".
>
> The cause to throw an exception to is that I update a field of BinaryObject
> which is child of nested BinaryObject .
> When I update a field of BinaryObject which is nested BinaryObject, it do
> not throw an exception.
>
> Should I not use this SQL for child of nested BinaryObject?
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>



-- 
Best regards,
Andrey V. Mashenkov

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

2017-08-31 Thread Evgenii Zhuravlev

Great news! Thank you for the update.

Evgenii

2017-08-31 16:47 GMT+03:00 Kenan Dalley :

> 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/
>

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/

UPDATE SQL for nested BinaryObject throws exception.

I use SqlQuery for nested BinaryObject.
The BinaryObject instance is following structure.

   BinaryObjectBuilder bb2 = binary.builder("nested2
hoge").setField("field2", "old", String.class);
   BinaryObjectBuilder bb = binary.builder("nested hoge").setField("field1",
bb2);
   binary.builder("hoge").setField("field0", bb);

The sample SQL to throw an exception is "update " + CACHE_NAME + " set
field2 = 'new'". 

The cause to throw an exception to is that I update a field of BinaryObject
which is child of nested BinaryObject .
When I update a field of BinaryObject which is nested BinaryObject, it do
not throw an exception.

Should I not use this SQL for child of nested BinaryObject?



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Ignite as Cache and Query layer for Cassandra.

2017-08-31 Thread Mark Farnan

Howdy,

I'm currently evaluating Ignite for a project, and am looking for some
guidance and project sample for using Ignite over Cassandra as a cache and
query layer.
Note: The Cassandra database and schema already exists and is mature.

In a Recent Infoworld post, (
https://www.infoworld.com/article/3191895/application-development/light-a-fire-under-cassandra-with-apache-ignite.html
) it stated

"No remodeling of Cassandra data
Apache Ignite reads from Apache Cassandra and other NoSQL databases, so
moving Cassandra data into Ignite requires no data modification. The data
schema can also be migrated directly into Ignite as is. "

However, I can't find in any documentation, or online articles, guidance
on just how to do this and there are no links in the article.
- The Ignite docs /cassandra section appear to only cover using
Cassandra as a persistence layer, not for going over and caching /
querying an existing schema. (unless I'm missing something obvious !)
- The Youtube video cuts out to blank at the end, so no links are shown.
The links on the slideshare document appear to be broken.
- Can't find any git hub for examples on how to do this (especially not
for the couple you tube vids)

Can anyone please point me to some working sample code and/or
documentation on how to do this ?

I'm especially interested in not having to migrate any schema's, nor
having to pre-load the data into the cache. (lazy load), which the
articles imply.
Also some of the data would be too large to load it all into Ram anyway.

Any assistance greatly appreciated.

Regards

Mark.

Re: Ignite 2.1.0 - Thread deadlock on DefaultSingletonBeanRegistry.getSingleton

Denis, yes I can confirm that the issue doesn't stand for 2.0.
I'll drill down into the issue and will file a ticket soon.

Kind regards,
Alex.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Schema vs CacheName

Hi,

Schema name and cache names match by default when a cache is configured via
either annotations or QueryEntity-es
Please refer to the following documentation section.

Let me clarify your questions:
Q1: You can set a schema name distinct from the default matching the cache
name by calling CacheConfiguration#setSchema
Tables created with CREATE TABLE will end up in PUBLIC schema, with no
options.
Q2: You can use setSchema on a query level to avoid specifying a particular
schema
Q3: There is no such thing like "PUBLIC cache"
Q4: It's a good practice specifying all the schema names in cross-cache
queries, but, of course, you could opt out from
specifying a schema belonging to the cache from which you are running a
query or a schema that has been set on a query level.

Kind regards,
Alex.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: We want to configure near cache on client so that we can handle high TPS items and avoid network call to server

Hi,

1. You can set an eviction policy distinct from the one of the underlying
server cache but you can set a
distinct expiration policy for a near cache as for now; there is, actually,
even no NearCacheConfiguration#setExpiryPolicyFactory method
2. For example, if you have the following configuration for a cache

CacheConfiguration cacheConf = ...;
...
cacheConf.setExpiryPolicyFactory(AccessedExpiryPolicy.factoryOf(new
Duration(TimeUnit.SECONDS,5)));

NearCacheConfiguration nearConf = new
NearCacheConfiguration<>(); 
nearConf.setNearEvictionPolicy(new LruEvictionPolicy<>(1000)); 

then if an entry which exists in the near cache is updated in the underlying
server cache then
near cache will be notified about it and the expiration policy will take
that fact into account.

If you access 2000 entities within 2 seconds then due to the LRU eviction
policy 1000 of them will be evicted.
If you have 100 entities in the near cache that were accessed 2 seconds ago
and read 500 entities within 3 seconds
then those 100 entities will expire and get removed from the near cache.

Kind regards,
Alex.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Configuring path of binary_meta, db directories etc

Please ignore.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Configuring path of binary_meta, db directories etc

2017-08-31 Thread Evgenii Zhuravlev

Hi,

Please
check org.apache.ignite.configuration.IgniteConfiguration#setWorkDirectory.
As for now, there is no option to specify a custom path only for binary
metadata.

Kind regards,
Evgenii

2017-08-31 15:17 GMT+03:00 userx :

> Hi,
>
> How can we configure a customized path for meta information which by
> default
> gets created in work folder under ignite_home ?
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Transaction Speed

2017-08-31 Thread Andrey Mashenkov

Ricky,

Does you mean you try to update same two entries in all 50_000 transactions?
Is it possible to collocate this entries?


On Thu, Aug 31, 2017 at 5:56 AM, rnauv  wrote:

> I want to make 2 clients concurrently calculate some values from a cache
> that
> read from a database, and store the result in the database. I can't use
> atomic cacheAtomicityMode as there is no lock so that the calculation might
> get an old value. I also need a backup to avoid lost cache when a node
> fail.
> Let's say I run 2 servers, and 2 clients. Right now, I'm able to do 50_000
> transactions for two rows in 70 seconds (around 1400 TPS). If it's
> possible,
> I want to increase the TPS.
>
> My initial configuration is like this:
> Server configuration:
> 1. CacheAtomicityMode = transactional
> 2. Read Through, Write Through, and Write Behind = true
> 3. Cache Mode = partitioned
> 4. Backup = 1
> 5. Query entities for my table
> 6. cacheStoreFactory for my CacheStore
> 7. DiscoverySPI which I set to my localhost
>
> Client configuration have the same configuration as the server excluding
> ReadThrough, WriteThrough, WriteBehind, QueryEntities, and
> CacheStoreFactory.
>
> The Transaction Concurrency is pessimistic while transaction isolation is
> repeatable_read.
> I didn't set Write synchronization mode (which by default will be
> PRIMARY_SYNC).
>
> The transaction procedure is similar with the one in Ignite Documentation
> [1].
>
> Any suggestions?
>
> Thanks,
> Ricky
>
> [1] https://apacheignite.readme.io/docs/transactions
>
>
>
> -
> -- Ricky
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>



-- 
Best regards,
Andrey V. Mashenkov

Configuring path of binary_meta, db directories etc

2017-08-31 Thread userx

Hi,

How can we configure a customized path for meta information which by default
gets created in work folder under ignite_home ?



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Please ignore

2017-08-31 Thread Alexander Fedotov

For test purposes only.

Kind regards,
Alex.

Re: Ignite Persistence on Kubernetes.

Thank you for your answer.
I choose MongoDB with StatefulSets, and I try to try it.




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

In Partitioned Mode, backup node is not restored.