Re: Package jar file path for sql Query Entity

[Vladislav Pyatkov <vl...@gmail.com>]

Hi,

I think in your case (when you configured "QueryEntity"), have not
necessary to copy classe (schema.jar) to a server. Ignite will by use
binary[1] format, and execute SQL (or other query) without deserialization.

But I definitly do not understand why it does not work...
You can to clarify are all data structures created as are you think or not.
Please, check it by using H2 debug console[2].

[1]: https://apacheignite.readme.io/docs/binary-marshaller
[2]:
https://apacheignite.readme.io/v1.7/docs/performance-and-debugging#using-h2-debug-console

On Tue, Nov 29, 2016 at 7:17 AM, rishi007bansod <ri...@gmail.com>
wrote:

> I have added warehouse.java containing class warehouse to package schema.
> Thats why I wrote schema.warehouse. Query I am executing is SELECT * from
> warehouse w WHERE w.w_id = 1 and entry corresponding to w_id = 1 is present
> in warehouse cache. schema.jar
> <http://apache-ignite-users.70518.x6.nabble.com/file/n9252/schema.jar>
> this is my jar file.
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Getting-null-query-output-after-using-
> QueryEntity-tp9217p9252.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>



-- 
Vladislav Pyatkov

Re: Package jar file path for sql Query Entity

[Vladislav Pyatkov <vl...@gmail.com>]

Hi,

Ignite stores date as it specify in marshaller. Binary marshaller was
configured by default.
In case, if Binary marshaller was specified, all internal works will be
processed in binary view (hence do not need to store java classes on
server).
If you want to use binary view in own code, you should use "withKeepBinary"
cache method[1].
If your classes do not implement Binarylizable, the marshaller will get
values through reflection and builds binary view.
Is that clear explanation?

[1]:
https://apacheignite.readme.io/docs/binary-marshaller#binaryobject-cache-api

On Thu, Dec 1, 2016 at 5:02 PM, rishi007bansod <ri...@gmail.com>
wrote:

> Thanks. After importing same package on server and client side solved my
> problem(initially i wrote class in client node instead of importing it).
>
> But, I am still unclear about how ignite stores data
> case I  : In both Binary and serialized format, and de-serializes data when
> required
> case II : Only in binary format, and then there is no need of
> de-serialization
>
> Can you please explain what is default behavior of ignite for storing
> data(is it case I or case II). Also I have configured cache from xml file
> that I have attached and I have used binarylizable interface so does this
> mean my objects are stored in binary format only?
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Getting-null-query-output-after-using-
> QueryEntity-tp9217p9331.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>



-- 
Vladislav Pyatkov

Re: Package jar file path for sql Query Entity

[rishi007bansod <ri...@gmail.com>]

Thanks. After importing same package on server and client side solved my
problem(initially i wrote class in client node instead of importing it). 

But, I am still unclear about how ignite stores data 
case I  : In both Binary and serialized format, and de-serializes data when
required
case II : Only in binary format, and then there is no need of
de-serialization

Can you please explain what is default behavior of ignite for storing
data(is it case I or case II). Also I have configured cache from xml file
that I have attached and I have used binarylizable interface so does this
mean my objects are stored in binary format only?



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Getting-null-query-output-after-using-QueryEntity-tp9217p9331.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.