Re: Near cache can be used with SQL Database

[Navneet Kumar]

Hi Val,
Thank you so much for providing the information. In another use case my
application client (written in C++) will look up a records from Near Cache.
Is it fine doing via ODBC interface?



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Near-cache-can-be-used-with-SQL-Database-tp9805p9858.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: LoadCache Performance decreases with the size of the cache

[vkulichenko]

I would recommend to use one of the non-empty constructors for QueryIndex,
they all set SORTED as default. Frankly, I would remove the one that is
without parameters, it doesn't make much sense and error-prone.

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/LoadCache-Performance-decreases-with-the-size-of-the-cache-tp9645p9856.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Old AWS SDK version, why?

[zshamrock]

Why I ask. It is not only matter of depending on the latest version, but for
AWS, in the specific case, it probably even causes the error.

When EC2 instance is configured with instance profile, as described here,
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-roles-for-amazon-ec2.html,
so new credentials are issued and periodically are renewed. 

And this is the error we see in the log from time to time (when running
Ignite in the clustered mode):

/ERROR [tcp-client-disco-reconnector-#5%%] o.a.i.s.d.t.TcpDiscoverySpi
[null] - Failed to get registered addresses from IP fi
nder on start (retrying every 2000 ms).
org.apache.ignite.spi.IgniteSpiException: Failed to list objects in the
bucket: 
at
org.apache.ignite.spi.discovery.tcp.ipfinder.s3.TcpDiscoveryS3IpFinder.getRegisteredAddresses(TcpDiscoveryS3IpFinder.java:168)
~[ignite-aws-1.7.0.ja
r!/:1.7.0]
at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.registeredAddresses(TcpDiscoverySpi.java:1600)
~[ignite-core-1.7.0.jar!/:1.7.0]
at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.resolvedAddresses(TcpDiscoverySpi.java:1549)
~[ignite-core-1.7.0.jar!/:1.7.0]
at
org.apache.ignite.spi.discovery.tcp.ClientImpl.joinTopology(ClientImpl.java:475)
[ignite-core-1.7.0.jar!/:1.7.0]
at
org.apache.ignite.spi.discovery.tcp.ClientImpl.access$900(ClientImpl.java:118)
[ignite-core-1.7.0.jar!/:1.7.0]
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$Reconnector.body(ClientImpl.java:1175)
[ignite-core-1.7.0.jar!/:1.7.0]
at
org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
[ignite-core-1.7.0.jar!/:1.7.0]
Caused by: com.amazonaws.services.s3.model.AmazonS3Exception: The provided
token has expired. (Service: Amazon S3; Status Code: 400; Error Code:
ExpiredToken; 
Request ID: EFDFC0BD8F4421AA)
at
com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:1307)
~[aws-java-sdk-core-1.10.50.jar!/:na]
at
com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:894)
~[aws-java-sdk-core-1.10.50.jar!/:na]
at
com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:597)
~[aws-java-sdk-core-1.10.50.jar!/:na]
at
com.amazonaws.http.AmazonHttpClient.doExecute(AmazonHttpClient.java:363)
~[aws-java-sdk-core-1.10.50.jar!/:na]
at
com.amazonaws.http.AmazonHttpClient.executeWithTimer(AmazonHttpClient.java:329)
~[aws-java-sdk-core-1.10.50.jar!/:na]
at
com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:308)
~[aws-java-sdk-core-1.10.50.jar!/:na]
at
com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:3595)
~[aws-java-sdk-s3-1.10.29.jar!/:na]
at
com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:3548)
~[aws-java-sdk-s3-1.10.29.jar!/:na]
at
com.amazonaws.services.s3.AmazonS3Client.listObjects(AmazonS3Client.java:647)
~[aws-java-sdk-s3-1.10.29.jar!/:na]
at
com.amazonaws.services.s3.AmazonS3Client.listObjects(AmazonS3Client.java:626)
~[aws-java-sdk-s3-1.10.29.jar!/:na]
at
org.apache.ignite.spi.discovery.tcp.ipfinder.s3.TcpDiscoveryS3IpFinder.getRegisteredAddresses(TcpDiscoveryS3IpFinder.java:128)
~[ignite-aws-1.7.0.ja
r!/:1.7.0]
... 6 common frames omitted/

Which probably could be due to S3 library is not being worked properly with
EC2 instance profile. So, using the latest S3 AWS SDK, would be a good thing
to try, whether this indeed was fixed in the new version.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Old-AWS-SDK-version-why-tp9824p9855.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: JCache and CacheManager.getCache

[vkulichenko]

It is supported if you provide key and value classes in CacheConfiguration,
but this is possible only in code, not in XML.

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/JCache-and-CacheManager-getCache-tp9847p9853.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: JCache and CacheManager.getCache

[Juan Velez]

So the CacheManager.getCache(String, Class, Class) is not supported then?

Thanks - J
> On 03 Jan, 2017, at 9:05 AM, vkulichenko  
> wrote:
> 
> Can you show the trace?
> 
> -Val
> 
> 
> 
> --
> View this message in context: 
> http://apache-ignite-users.70518.x6.nabble.com/JCache-and-CacheManager-getCache-tp9847p9848.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: JCache and CacheManager.getCache

[vkulichenko]

You don't need to provide types to get a cache. Just do this:

Cache cache = cacheManager.getCache("myCache");

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/JCache-and-CacheManager-getCache-tp9847p9851.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: JCache and CacheManager.getCache

[Juan Velez]

public class Test {

public static void main(String[] args) throws IOException {
CacheManager cacheManager = 
Caching.getCachingProvider().getCacheManager(new 
ClassPathResource("ignite-config-simple.xml").getURI(), null);
Cache cache = cacheManager.getCache("myCache", 
Integer.class, MyObject.class);
}
}

Exception in thread "main" java.lang.ClassCastException
at org.apache.ignite.cache.CacheManager.getCache(CacheManager.java:203)
at Test.main(Test.java:15)


ignite-config-simple.xml

http://www.springframework.org/schema/beans;
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
   xsi:schemaLocation="http://www.springframework.org/schema/beans
   
http://www.springframework.org/schema/beans/spring-beans.xsd;>





















> On 03 Jan, 2017, at 9:05 AM, vkulichenko  
> wrote:
> 
> Can you show the trace?
> 
> -Val
> 
> 
> 
> --
> View this message in context: 
> http://apache-ignite-users.70518.x6.nabble.com/JCache-and-CacheManager-getCache-tp9847p9848.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Old AWS SDK version, why?

[Denis Magda]

CC-ing dev@ list.

Created the ticket to update all 3rd party dependencies for our cloud based IP 
finders (AWS, GCE and JClouds).
https://issues.apache.org/jira/browse/IGNITE-4519 


Is there anyone in community who are interested in handling this?

—
Denis

> On Jan 2, 2017, at 12:11 PM, vkulichenko  
> wrote:
> 
> This is just a version ignite-aws module was developed on, and I don't think
> newer versions were ever tested. However, I believe it should work with
> 1.11.76. Can you try it out and let us know if it does?
> 
> -Val
> 
> 
> 
> --
> View this message in context: 
> http://apache-ignite-users.70518.x6.nabble.com/Old-AWS-SDK-version-why-tp9824p9825.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.

JCache and CacheManager.getCache

[juanavelez]

I am trying to obtain a Cache using JCache's
CacheManager.getCache("myCache", Integer.class, MyObject.class) but it fails
with a ClassCastException (can't convert from Object to Integer). The cache
is configured in an ignite configuration xml file, but I don't see a way to
set the types for the key and value. How is the correct way to obtain an
existing cache which has been configured using the spring/xml approach by
using the JCache api?

Thanks - J



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/JCache-and-CacheManager-getCache-tp9847.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Error with ignite-rest-http

[Gaurav Bajaj]

Hi,

Update : I checked and it libs/connector-layer is not standard ignite
folder. It was created for something internal.
So basically it was Jetty Server version mismatch. Thanks Nikolai and
dkarachentsev
for your help.

Regards,
Gaurav

On Tue, Jan 3, 2017 at 1:47 PM, Gaurav Bajaj  wrote:

> Hello Nikolai,
>
> Based on the hint provided on the thread, I did simple File search for
> "jetty" and found that in Ignite/libs directory, I have connector-layer
> folder and it have Jetty Server jars with different version
> "jetty-util-7.3.0.v20110203.jar". Removing them did that trick. Ignite
> starts up now without any error.
> Thanks a lot. I will still find out why they are there in
> libs/connector-layer folder.
>
>
> Best Regards,
> Gaurav
>
> On Tue, Jan 3, 2017 at 1:38 PM, Nikolai Tikhonov 
> wrote:
>
>> Sorry, I'm missed that you don't use ignite as maven dependency in your
>> project but running it how standalone server. Could you please show which
>> modules in your C:\Users\D-NX29AE\Project\Software\shielding-gridgain-e
>> nterprise-fabric-7.5.26\libs folder? (output dir commond in console)
>>
>> On Tue, Jan 3, 2017 at 3:34 PM, Gaurav Bajaj 
>> wrote:
>>
>>> Hello Nikolai,
>>>
>>> Sorry I am confused, where do I run this command? On my IntelliJ
>>> workspace?
>>>
>>> On Tue, Jan 3, 2017 at 1:22 PM, Nikolai Tikhonov 
>>> wrote:
>>>
 Hi,

 It's really like on jar hell. You can use maven dependency tree which
 allows to find conflict:

 *mvn dependency:tree -Dverbose -Dincludes=jetty-server*

 On Tue, Jan 3, 2017 at 2:30 PM, dkarachentsev <
 dkarachent...@gridgain.com> wrote:

> It looks like you have another version of Jetty in classpath. Do you
> have
> IGNITE_HOME environment variable set?
>
>
>
> --
> View this message in context: http://apache-ignite-users.705
> 18.x6.nabble.com/Error-with-ignite-rest-http-tp9835p9838.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>


>>>
>>
>

Re: Error with ignite-rest-http

[Gaurav Bajaj]

Hello Nikolai,

Based on the hint provided on the thread, I did simple File search for
"jetty" and found that in Ignite/libs directory, I have connector-layer
folder and it have Jetty Server jars with different version
"jetty-util-7.3.0.v20110203.jar". Removing them did that trick. Ignite
starts up now without any error.
Thanks a lot. I will still find out why they are there in
libs/connector-layer folder.


Best Regards,
Gaurav

On Tue, Jan 3, 2017 at 1:38 PM, Nikolai Tikhonov 
wrote:

> Sorry, I'm missed that you don't use ignite as maven dependency in your
> project but running it how standalone server. Could you please show which
> modules in your C:\Users\D-NX29AE\Project\Software\shielding-gridgain-
> enterprise-fabric-7.5.26\libs folder? (output dir commond in console)
>
> On Tue, Jan 3, 2017 at 3:34 PM, Gaurav Bajaj 
> wrote:
>
>> Hello Nikolai,
>>
>> Sorry I am confused, where do I run this command? On my IntelliJ
>> workspace?
>>
>> On Tue, Jan 3, 2017 at 1:22 PM, Nikolai Tikhonov 
>> wrote:
>>
>>> Hi,
>>>
>>> It's really like on jar hell. You can use maven dependency tree which
>>> allows to find conflict:
>>>
>>> *mvn dependency:tree -Dverbose -Dincludes=jetty-server*
>>>
>>> On Tue, Jan 3, 2017 at 2:30 PM, dkarachentsev <
>>> dkarachent...@gridgain.com> wrote:
>>>
 It looks like you have another version of Jetty in classpath. Do you
 have
 IGNITE_HOME environment variable set?



 --
 View this message in context: http://apache-ignite-users.705
 18.x6.nabble.com/Error-with-ignite-rest-http-tp9835p9838.html
 Sent from the Apache Ignite Users mailing list archive at Nabble.com.

>>>
>>>
>>
>

Re: Error with ignite-rest-http

[Nikolai Tikhonov]

Sorry, I'm missed that you don't use ignite as maven dependency in your
project but running it how standalone server. Could you please show which
modules in your C:\Users\D-NX29AE\Project\Software\shielding-gridgain-
enterprise-fabric-7.5.26\libs folder? (output dir commond in console)

On Tue, Jan 3, 2017 at 3:34 PM, Gaurav Bajaj  wrote:

> Hello Nikolai,
>
> Sorry I am confused, where do I run this command? On my IntelliJ workspace?
>
> On Tue, Jan 3, 2017 at 1:22 PM, Nikolai Tikhonov 
> wrote:
>
>> Hi,
>>
>> It's really like on jar hell. You can use maven dependency tree which
>> allows to find conflict:
>>
>> *mvn dependency:tree -Dverbose -Dincludes=jetty-server*
>>
>> On Tue, Jan 3, 2017 at 2:30 PM, dkarachentsev > > wrote:
>>
>>> It looks like you have another version of Jetty in classpath. Do you have
>>> IGNITE_HOME environment variable set?
>>>
>>>
>>>
>>> --
>>> View this message in context: http://apache-ignite-users.705
>>> 18.x6.nabble.com/Error-with-ignite-rest-http-tp9835p9838.html
>>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>>>
>>
>>
>

Re: Error with ignite-rest-http

[Gaurav Bajaj]

Hello Nikolai,

Sorry I am confused, where do I run this command? On my IntelliJ workspace?

On Tue, Jan 3, 2017 at 1:22 PM, Nikolai Tikhonov 
wrote:

> Hi,
>
> It's really like on jar hell. You can use maven dependency tree which
> allows to find conflict:
>
> *mvn dependency:tree -Dverbose -Dincludes=jetty-server*
>
> On Tue, Jan 3, 2017 at 2:30 PM, dkarachentsev 
> wrote:
>
>> It looks like you have another version of Jetty in classpath. Do you have
>> IGNITE_HOME environment variable set?
>>
>>
>>
>> --
>> View this message in context: http://apache-ignite-users.705
>> 18.x6.nabble.com/Error-with-ignite-rest-http-tp9835p9838.html
>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>>
>
>

Re: Error with ignite-rest-http

[Gaurav Bajaj]

Hi,

Thanks for quick reply. I don't have IGNITE_HOME setup in my environment
variables.
Please not I am using ignite.bat to start IGNITE instance. I am using
Windows 7.
Also I don't have another Jetty instance which I have installed or
configured.

On Tue, Jan 3, 2017 at 12:30 PM, dkarachentsev 
wrote:

> It looks like you have another version of Jetty in classpath. Do you have
> IGNITE_HOME environment variable set?
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Error-with-ignite-rest-http-tp9835p9838.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Re: Error with ignite-rest-http

[Nikolai Tikhonov]

Hi,

It's really like on jar hell. You can use maven dependency tree which
allows to find conflict:

*mvn dependency:tree -Dverbose -Dincludes=jetty-server*

On Tue, Jan 3, 2017 at 2:30 PM, dkarachentsev 
wrote:

> It looks like you have another version of Jetty in classpath. Do you have
> IGNITE_HOME environment variable set?
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Error-with-ignite-rest-http-tp9835p9838.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Re: Near cache can be used with SQL Database

[dkarachentsev]

Yes, it's possible. You may start from here [1].

[1] http://apacheignite.gridgain.org/docs/odbc-driver



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Near-cache-can-be-used-with-SQL-Database-tp9805p9840.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Affinity

[Anil]

Thank you Nikolai.

I will wait for Sergi's response. Thanks to both of you.

Re: Error with ignite-rest-http

[dkarachentsev]

It looks like you have another version of Jetty in classpath. Do you have
IGNITE_HOME environment variable set? 



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Error-with-ignite-rest-http-tp9835p9838.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Near cache can be used with SQL Database

[Navneet Kumar]

Hi Val,
I am trying to use ODBC interface to fetch records from Local cache. is it
possible?



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Near-cache-can-be-used-with-SQL-Database-tp9805p9837.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

回复：BinaryObject and String.intern

[shawn.du]

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 this message in context: http://apache-ignite-users.70518.x6.nabble.com/BinaryObject-and-String-intern-tp9826p9834.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
 

Error with ignite-rest-http

[GB]

Hi,

I am trying to enable ignite REST api support. For that, I have copied
"ignite-rest-http" from optional into lib. While starting the ignite server
I am getting "No Such Method error". I went through other threads and forums
but couldn't get the solution for it. Can someone help? Let me know if more
information is required.
Error is below :

C:\Users\D-NX29AE\Project\Software\shielding-gridgain-enterprise-fabric-7.5.26\bin>ignite.bat
[11:19:52]__  
[11:19:52]   /  _/ ___/ |/ /  _/_  __/ __/
[11:19:52]  _/ // (7 7// /  / / / _/
[11:19:52] /___/\___/_/|_/___/ /_/ /___/
[11:19:52]
[11:19:52] ver. 1.5.26#20160616-sha1:d8dedc64
[11:19:52] 2016 Copyright(C) Apache Software Foundation
[11:19:52]
[11:19:52] Ignite documentation: http://ignite.apache.org
[11:19:52]
[11:19:52] Quiet mode.
[11:19:52]   ^-- Logging to file
'C:\Users\D-NX29AE\Project\Software\shielding-gridgain-enterprise-fabric-7.5.26\work\log\ignite-7325081b.log'
[11:19:52]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false
or "-v" to ignite.{sh|bat}
[11:19:52]
[11:19:52] OS: Windows 7 6.1 x86
[11:19:52] VM information: Java(TM) SE Runtime Environment 1.8.0_60-b27
Oracle Corporation Java HotSpot(TM) Server VM 25.60-b23
[11:19:52] Configured plugins:
[11:19:52]   ^-- GridGain 7.5.26#20160616-sha1:ff88903b
[11:19:52]   ^-- 2016 Copyright(C) GridGain Systems
[11:19:52]
[11:19:53] Security status [authentication=off, tls/ssl=off]
[11:19:54,040][ERROR][main][IgniteKernal] Got exception while starting (will
rollback startup routine).
java.lang.NoSuchMethodError:
org.eclipse.jetty.util.log.StdErrLog.setProperties(Ljava/util/Properties;)V
at
org.apache.ignite.internal.processors.rest.protocols.http.jetty.GridJettyRestProtocol.(GridJettyRestProtocol.java:72)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at
org.apache.ignite.internal.processors.rest.GridRestProcessor.startHttpProtocol(GridRestProcessor.java:828)
at
org.apache.ignite.internal.processors.rest.GridRestProcessor.start(GridRestProcessor.java:448)
at
org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1496)
at
org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:861)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1737)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1590)
at
org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1043)
at
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:965)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:851)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:750)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:620)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:590)
at org.apache.ignite.Ignition.start(Ignition.java:347)
at
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)
[11:19:54] Ignite node stopped OK [uptime=00:00:02:467]
java.lang.NoSuchMethodError:
org.eclipse.jetty.util.log.StdErrLog.setProperties(Ljava/util/Properties;)V
at
org.apache.ignite.internal.processors.rest.protocols.http.jetty.GridJettyRestProtocol.(GridJettyRestProtocol.java:72)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at
org.apache.ignite.internal.processors.rest.GridRestProcessor.startHttpProtocol(GridRestProcessor.java:828)
at
org.apache.ignite.internal.processors.rest.GridRestProcessor.start(GridRestProcessor.java:448)
at
org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1496)
at
org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:861)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1737)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1590)
at
org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1043)
at
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:965)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:851)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:750)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:620)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:590)
at org.apache.ignite.Ignition.start(Ignition.java:347)
at
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)
Failed to start grid:
org.eclipse.jetty.util.log.StdErrLog.setProperties(Ljava/util/Properties;)V
Press any key to continue . . .



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Error-with-ignite-rest-http-tp9835.html
Sent from the 

Re: 答复: BinaryObject and String.intern

[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 this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/BinaryObject-and-String-intern-tp9826p9834.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

答复: BinaryObject and String.intern

[Shawn Du]

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 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-and-String-inter
n-tp9826p9827.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: 答复: class org.apache.ignite.binary.BinaryObjectException: Wrong value has been set

[dkarachentsev]

You may use BinaryObjectBuilder#setField(String, T, Class) to
explicitly set argument type.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/class-org-apache-ignite-binary-BinaryObjectException-Wrong-value-has-been-set-tp9829p9832.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

答复: class org.apache.ignite.binary.BinaryObjectException: Wrong value has been set

[Shawn Du]

Exactly!

 

Thanks.

Shawn

 

发件人: Nikolai Tikhonov [mailto:ntikho...@apache.org] 
发送时间: 2017年1月3日 16:05
收件人: user@ignite.apache.org
主题: Re: class org.apache.ignite.binary.BinaryObjectException: Wrong value has 
been set

 

Hi,

 

Is it possible that you build your object by binary builder and set null value 
for "product" field? In this case will be created metadata where type of field 
will be assigned Object and when we will create new object with non-null value 
(for example String) you got this exception.

 

Thanks,

Nikolay 

 

On Tue, Jan 3, 2017 at 10:56 AM, Shawn Du  > wrote:

Hi,

 

I met very strange issues.  With the same code, on one machine, it works fine, 
but on another cluster, it always failed with exception:

 

java.lang.RuntimeException: class 
org.apache.ignite.binary.BinaryObjectException: Wrong value has been set 
[typeName=streams, fieldName=product, fieldType=Object, 
assignedValueType=String] at

I met this issue before, I remembered that I fixed it by renaming a class 
field.  But this time, I can’t, for we create it dynamically with binary object.

 

Please help.

 

Thanks

Shawn

 

 

 

 

Re: class org.apache.ignite.binary.BinaryObjectException: Wrong value has been set

[Nikolai Tikhonov]

Hi,

Is it possible that you build your object by binary builder and set null
value for "product" field? In this case will be created metadata where type
of field will be assigned Object and when we will create new object with
non-null value (for example String) you got this exception.

Thanks,
Nikolay

On Tue, Jan 3, 2017 at 10:56 AM, Shawn Du  wrote:

> Hi,
>
>
>
> I met very strange issues.  With the same code, on one machine, it works
> fine, but on another cluster, it always failed with exception:
>
>
>
> java.lang.RuntimeException: class 
> org.apache.ignite.binary.BinaryObjectException:
> Wrong value has been set [typeName=streams, fieldName=product,
> fieldType=Object, assignedValueType=String] at
>
> I met this issue before, I remembered that I fixed it by renaming a class
> field.  But this time, I can’t, for we create it dynamically with binary
> object.
>
>
>
> Please help.
>
>
>
> Thanks
>
> Shawn
>
>
>
>
>
>
>