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
9, Anil <anilk...@gmail.com> wrote:
>
>> Hi,
>>
>> java.lang.ClassCastException:
>> org.apache.ignite.internal.binary.BinaryObjectImpl
>> cannot be cast to org.apache.ignite.cache.affinity.Affinity exception
>> thrown when a field updated using Bi
y.Affinity exception
> thrown when a field updated using BinaryObject for a cache entry. and it is
> intermittent.
>
> Following is the snippet i am using
>
> IgniteCache<Affinity, BinaryObject> cache =
> ignite.cache(CacheManager.CACHE).withKeepBinary();
> IgniteCa
Hi,
java.lang.ClassCastException:
org.apache.ignite.internal.binary.BinaryObjectImpl cannot be cast to
org.apache.ignite.cache.affinity.Affinity exception thrown when a field
updated using BinaryObject for a cache entry. and it is intermittent.
Following is the snippet i am using
IgniteCache
ot;,
>> ""));
>> cache.put(4L, new Organization(4L, "org4", false, "woodlands",
>> ""));
>> cache.put(5L, new Organization(5L, "org5", false, "changi", ""));
>&g
> > > > Note that this actually doesn't matter if the class is
>> available
>> >> on
>> >> > > > > server's local classpath. In this case it will be always used
>> >> > > regardless
>> >> > > > of
>
, true, "jurong west",
> ""));
> cache.put(4L, new Organization(4L, "org4", false, "woodlands",
> ""));
> cache.put(5L, new Organization(5L, "org5", false, "changi", ""));
> // cache.put
t;));
cache.put(5L, new Organization(5L, "org5", false, "changi", ""));
// cache.put(6L, new Organization(6L, "org6", true, "jurong island",
""));
IgniteCache<Long, BinaryObject> binaryCache = cache.wi
ot;, ""));
cache.put(3L, new Organization(3L, "org3", true, "jurong west", ""));
cache.put(4L, new Organization(4L, "org4", false, "woodlands", ""));
cache.put(5L, new Organization(5L, "org5", false,
;> I've run your code and it works fine for me on ignite 1.7-1.9 versions
>> and master branch.
>>
>> On Thu, Mar 30, 2017 at 12:19 PM, David Li <david.li...@gmail.com> wrote:
>>
>>> Hello,
>>>
>>> I am having a little issue with
;> I am having a little issue with the ScanQuery for BinaryObject.
>>
>> Some code snippets
>>
>> IgniteCache<Long, Organization> cache = ignite.cache(CacheConfig.CACHE_NAME);
>> IgniteCache<Long, BinaryObject> binaryCache = cache.withKeepBinary();
>
Hi David,
I've run your code and it works fine for me on ignite 1.7-1.9 versions and
master branch.
On Thu, Mar 30, 2017 at 12:19 PM, David Li <david.li...@gmail.com> wrote:
> Hello,
>
> I am having a little issue with the ScanQuery for BinaryObject.
>
> Some code snippets
Hello,
I am having a little issue with the ScanQuery for BinaryObject.
Some code snippets
IgniteCache<Long, Organization> cache = ignite.cache(CacheConfig.CACHE_NAME);
IgniteCache<Long, BinaryObject> binaryCache = cache.withKeepBinary();
// scan query
IgniteBiPredicate<Lon
My code error, BinaryObject deserialize twice.
ThanksShawn
On 02/11/2017 06:26，vkulichenko<valentin.kuliche...@gmail.com> wrote：
Shawn,
What's the actual issue after you disabled compact footer? Exc
Shawn,
What's the actual issue after you disabled compact footer? Exception?
Incorrect behavior?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/restore-Java-Object-from-BinaryObject-tp10525p10556.html
Sent from the Apache Ignite Users mailing list
leases/mobile/org/apache/ignite/configuration/BinaryConfiguration.html#isCompactFooter().On Thu, Feb 9, 2017 at 1:28 PM, shawn.du <shawn...@neulion.com.cn> wrote:
Hi,I implement a cacheStore, this cachestore will persist a binaryObject into bytes and store in MySQL blob. Ex
nt a cacheStore, this cachestore will persist a binaryObject
> into bytes and store in MySQL blob.
> Exceptions occurred when calling loadCache function:
> binaryObject.deserialize() will throw exceptions like "Cannot find
> metadata for object with compact footer: -1615140068"
> If I
Hi,I implement a cacheStore, this cachestore will persist a binaryObject into bytes and store in MySQL blob. Exceptions occurred when calling loadCache function:binaryObject.deserialize() will throw exceptions like "Cannot find metadata for object with compact footer: -1615140068&
, there is still no compression supported.
So only you can do is to write algorithms in your side to handle such cases
like your Map<String, BitSet>.
Thanks!
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/BinaryObject-and-String-intern-tp9826p9891.html
Sen
thanks dkarachentsev.
在2017年01月03日 18:25，dkarachentsev 写道:Actually no, because Ignite internally will store it as a BinaryObject and
will send to other nodes in a binary format as well, where all string fields
will be unmarshaled without intern().
--
View
Actually no, because Ignite internally will store it as a BinaryObject and
will send to other nodes in a binary format as well, where all string fields
will be unmarshaled without intern().
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/BinaryObject-and-String
If I don't use binary object and use POJO and never call keepBinary, it
will?
Thanks
Shawn
-邮件原件-
发件人: dkarachentsev [mailto:dkarachent...@gridgain.com]
发送时间: 2017年1月3日 15:16
收件人: user@ignite.apache.org
主题: Re: BinaryObject and String.intern
This won't give you any benefit, because
This won't give you any benefit, because Strings will be marshaled and stored
in binary format. In other words you'll get a binary copy of your string,
which is managed just like any other object.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/BinaryObject
ntity.setFields(fields);
Public class MyEntryProcessor implements
EntryProcessor<String,BinaryObject,Object>
{
Private List values;
public Object process(MutableEntry<String, BinaryObject> entry,
Object... args)
{
BinaryObjectBuilder builder
this
and always specify the list of fields to select.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/query-binaryobject-cache-in-zeppelin-tp9473p9614.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
|
|
+--+
Thanks
Shawn
发件人: Andrey Mashenkov [mailto:andrey.mashen...@gmail.com]
发送时间: 2016年12月15日 18:21
收件人: user@ignite.apache.org
主题: Re: 答复: 答复: query binaryobject cache in zeppelin
Hi Shawn,
I've got Zeppelin sources, rewrite test query
All Seems good.
>
>
>
> Thanks
>
> Shawn
>
>
>
> *发件人:* Andrey Mashenkov [mailto:andrey.mashen...@gmail.com]
> *发送时间:* 2016年12月12日 18:54
> *收件人:* user@ignite.apache.org
> *主题:* Re: 答复: query binaryobject cache in zeppelin
>
>
>
> Hi Shawn,
>
>
&g
with
ignite 1.8, I had to build from source and change pom.xml to use ignite 1.8.0.
All Seems good.
Thanks
Shawn
发件人: Andrey Mashenkov [mailto:andrey.mashen...@gmail.com]
发送时间: 2016年12月12日 18:54
收件人: user@ignite.apache.org
主题: Re: 答复: query binaryobject cache in zeppelin
Hi Shawn
String> fields = new LinkedHashMap<>();
> List indexes = new ArrayList<>();
> for (ColumnScheme columnScheme : columns)
> {
> fields.put(columnScheme.getName(), columnScheme.getType());
> if (columnScheme.isEnsureIndex())
> {
> indexes.add(new Q
setIndexes(indexes);
entity.setFields(fields);
Shawn
发件人: Andrey Mashenkov [mailto:amashen...@gridgain.com]
发送时间: 2016年12月12日 17:24
收件人: user@ignite.apache.org
主题: Re: query binaryobject cache in zeppelin
Hi Shawn,
Classes that you want to use in queries should be set via setQueryEntitie
gt; Hi,
>
>
>
> Today, I had a try of zeppelin. After setup a zeppelin node and began to
> issue SQL for query, I don’t know how to input the *table name* of SQL.
>
> For my cache are built with BinaryObject and config with setQueryEntities.
>
>
>
> It is possible to do query in zeppinlin for these caches?
>
>
>
> Thanks
>
> Shawn
>
Hi,
Today, I had a try of zeppelin. After setup a zeppelin node and began to
issue SQL for query, I don't know how to input the *table name* of SQL.
For my cache are built with BinaryObject and config with setQueryEntities.
It is possible to do query in zeppinlin for these caches
/BinaryObject-performance-issue-tp4375p8747.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
the nodes. I even tried creating a dummy first object with all the possible
fields before iterating through the resultset, but that did not help. The
only thing that helped was making sure each binaryobject had all of the
fields set to something no matter what.
Any ideas?
--
View this message
-with-binaryobject-tp8581p8631.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
ployee = new Employee(1,"bob");
cache.put(1, employee);
try (IgniteCache<Integer, BinaryObject> binaryCache =
ignite.getOrCreateCache(cfg).withKeepBinary()){
binaryCache.invoke(1, new EntryProcessor<Integer,
BinaryObject, Object>(){
ichenko <
>> valentin.kuliche...@gmail.com> wrote:
>>
>>> Cross-posting this to dev list.
>>>
>>> Vladimir,
>>>
>>> To be honest, I don't see much difference between null values for
>>> objects and zero values for primitives. Fr
honest, I don't see much difference between null values for objects
>> and zero values for primitives. From BinaryObject semantics standpoint,
>> both are default values for corresponding types. These values will be
>> returned from the BinaryObject.field() method regardless of
-using-binaryobjectbuilder
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/dynamic-data-structure-with-binaryobject-tp8581p8595.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
ch difference between null values for objects
> and zero values for primitives. From BinaryObject semantics standpoint,
> both are default values for corresponding types. These values will be
> returned from the BinaryObject.field() method regardless of whether we
> actually save then in t
Hi experts,
I wonder to know the blew scenario is possible in ignite with binaryobject?
At first, cache is empty.
I put a cache entry with key1 and value with field A.
After a while,
I put a cache entry with the same key key1 and value with field B, note
field A keep the old value
Cross-posting this to dev list.
Vladimir,
To be honest, I don't see much difference between null values for objects
and zero values for primitives. From BinaryObject semantics standpoint,
both are default values for corresponding types. These values will be
returned from the BinaryObject.field
/vol8/p1816-teller.pdf.
Thanks
Shawn
发件人: Vladimir Ozerov [mailto:voze...@gridgain.com]
发送时间: 2016年10月28日 5:21
收件人: user@ignite.apache.org
主题: Re: BinaryObject pros/cons
Hi,
I am not very concerned with null fields overhead, because usually it won't be
significant. However
r. Unless you have hundreds of fields
> most of which are nulls (very rare case), the overhead is minimal.
>
> -Val
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/BinaryObject-pros-cons-tp8541p8563.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
.nabble.com/BinaryObject-pros-cons-tp8541p8563.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi expert,
BinaryObject gives great convenience to create dynamic objects. Does it have
disadvantages?
Take below example, does each field name will consume memory or not? Many
RDBMS which has fixed table schema, column name willn't use memory/disk.
How does it for BinaryObject
le the
> keys that give back null, are BinaryObject instances as presented by Visor.
>
>
> Did you encounter this before?
>
>
> Thanks,
>
> Nicu
>
>
> Met vriendelijke groeten/Meilleures salutations/Best regards
>
> Nicolae Marasoiu
> Agile Developer
> E ni
noticed that the keys we can get the
value for, are the right class, Pair, in this case, while the keys that give
back null, are BinaryObject instances as presented by Visor.
Did you encounter this before?
Thanks,
Nicu
Met vriendelijke groeten/Meilleures salutations/Best regards
Nicolae
Cool. Thanks. That helped.
I assume without that setting the cache store on the server node was trying
to de-serialize the cache key BinaryObject and hence it failed.
I will implement the CacheStore interface to optimize the bulk loads and
updates to the cache.
--
View this message in context
Hi,
Please try setting this in your cache configuration:
cfg.setStoreKeepBinary(true);
This will force Ignite to work with binary objects when interacting with the
store. Note that your store should implement CacheStore<BinaryObject,
BinaryObject>.
-Val
--
View this message in c
the cache as IgniteCache<BinaryObject, BinaryObject> by
passing the configuration object. The cache is backed by a cache store.
b. create the binary object for the cache key using the builder and
call cache.get(builder.build());
I tried debugging the server node and verified that the cacheS
This exception means that there was an attempt of BinaryObject
deserialization, but there is no class definition for this BinaryObject.
More specifically, it tries to find the mapping between type ID and class
name, which is stored in the system cache and on the local FS when the
object
from
the local file? Does the exception appear only when working with
BinaryObject's?
Thanks.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Iterating-through-a-BinaryObject-cache-fails-tp6038p6276.html
Sent from the Apache Ignite Users mailing list archive
pBinary flag, I was able to iterate through the
> cache and add or drop fields from a BinaryObject at runtime. This was the
> original purpose of iterating through the cache.
>
> The changes (of adding and/or dropping a field) made to the cache are not
> reflecting on h2 debug console
1. The strange part is even when the binary objects are created with
different type names (different for key BinaryObject and for value
BinaryObject), I am able to query the field that is the part of the key
BinaryObject by specifying the valuetype
2. By "binary type descriptor" I
Hi,
You should always use withKeepBinary if you plan to work with a cache
containing BInaryObject key or value (including queries). The flag is used
internally to prevent deserialization from binary representation to actual
class instance.
So the answers are:
1. yes if you want to load binary
ved after setting a
> custom key type. The data got loaded into the cache.
>
> 1. The strange part is that even if I set different key and value types the
> below query executes correctly
>
> SqlQuery<BinaryObject, BinaryObject> query = new
> SqlQuery<>(tab
Thanks for pinpointing the issue. The issue got resolved after setting a
custom key type. The data got loaded into the cache.
1. The strange part is that even if I set different key and value types the
below query executes correctly
SqlQuery<BinaryObject, BinaryObject> query
the cache instance for
loading it?
2. I didn't follow the reason why I should specify withKeepBinary() when
fetching the cache for querying since the original cache instance itself is
of the type IgniteCache<String, BinaryObject>. Does ignite try to
deserialize it when I don't specify withKeepBin
Hi,
You're using 'withKeepBinary()' incorrectly. This method returns another
instance of IgniteCache which you can use to prevent BinaryObject
deserialization on the client side. This doesn't change the cache itself.
See the example here on this should be done:
https://apacheignite.readme.io/docs
Hi,
The problematic line of code is this one:
qe.setKeyType(String.class.getCanonicalName());
Basically, because of this configuration, SQL engine expect to have a String
as a key and therefore tries to unwrap the BinaryObject and fails on
deserialization. You should use your own name, as you
using
the DataStreamer API into an IgniteCache<BinaryObject, BinaryObject>.
Kindly find the gist here
<https://gist.github.com/shahamit/561e638f02ec6a67c4185035d999fb41> and let
me know your inputs.
Thanks.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabb
No its not related. The other thread is for cache loading issue with an
ignite cache <BinaryObject, BinaryObject>.
This issue is while iterating through a cache of <String, BinaryObject> that
is preloaded with data. The exception is similar though. I am not sure if
its all som
Hi,
Is the question somehow related to your previous quiestion, entitled Error
while loading data into cache with BinaryObject as key field ?
I see the same eexception here.
How do you fill the cache with data ?
2016-07-01 11:39 GMT+03:00 pragmaticbigdata <amits...@gmail.com>:
> I
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Error-while-loading-data-into-cache-with-BinaryObject-as-key-field-tp6014p6042.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
;amits...@gmail.com>
wrote:
> From the documentation I understood that BinaryMarshaller is the default
> Marshaller used for serializing and storing objects in the cache. So, all
> the java pojo objects added to the cache are converted to the binary format
> (which is repesented by t
>From the documentation I understood that BinaryMarshaller is the default
Marshaller used for serializing and storing objects in the cache. So, all
the java pojo objects added to the cache are converted to the binary format
(which is repesented by the BinaryObject class) and deserialized whene
I am using ignite version 1.6 and I have a replicated cache of <String,
BinaryObject> pre-loaded. In order to try out the dynamic structure change
ability with BinaryObjects, I tried iterating through the cache with
different approaches. All of them fail with an error
Caused by:
> What was returned as the type name before? As I see from your code that you
used some getter to retrieve the name.
I have a IgniteCache<BinaryObject, BinaryObject>. The type name for the key
object before was a string "My_Object_ValueType" and "My_Object_KeyType"
gt;
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Error-while-loading-data-into-cache-with-BinaryObject-as-key-field-tp6014p6019.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
--
Best regards,
Alexei Scherbakov
I am using ignite version 1.6 and getting an error while loading data from a
csv file through DataStreamer into a IgniteCache<BinaryObject,
BinaryObject>. The error is
Failed to execute compound future reducer: GridCompoundFuture [rdc=null,
initFlag=1, lsnrCalls=0, done=false, cancelled
Hi, everyone.
I found out about the BinaryObject functionality for storing and
manipulating data on Ignite (
http://apacheignite.gridgain.org/docs/binary-marshaller).
I decided to adopt it, in order to reduce the hassle during data-migrations.
However, when I try to do SQL queries on a cache
Hi,
BinaryObject is designed to represent POJOs in binary format, in this case
schema change is generally a very rare event, so there is no performance
concern about metadata update. You use case is more specific and thus
requires specific solution.
And btw, I'm not sure I understand
I need BinaryObject to process ScanQueries on data with dynamic categories
list. There are 30 different categories at current case.
My Task is to calculate amount of persons in each category, so *map* is not
working for me.
try (QueryCursor cursor = cache.query(new ScanQuery<Long, BinaryObj
Agree with Andrey. This use case doesn't look like a good fit for
BinaryObject, is there any particular reason for using it? Is Map not
working for you?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/BinaryObject-performance-issue-tp4375p4392.html
Sent
Hello!
I need to put <Long, MapInteger, String>> data structure to cache.
I have found out that there is a BinaryObject, that solves the problem of
dynamic fields list and improves cache query operations performance.
But I faced a performance issue.
I have 3 node cluster with 5GB of RA
e-ignite-users.70518.x6.nabble.com/Loading-objects-saved-as-BinaryObject-tp2804p2806.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
101 - 177 of 177 matches
Mail list logo
