Re: Determining BinaryObject field type

[Pavel Vinokurov]

Dave,

I suppose there isn't way to delete the schema.
You could get the meta information about binary objects using Ignite#binary()
method.
For example ignite.binary().type("package.Employeee").fieldTypeName("name").



Thanks,
Pavel

2018-03-24 1:10 GMT+03:00 Dave Harvey :

> Once a BinaryObjectSchema is created, it is not possible to change the type
> of a field for a known field name.
>
> My question is whether there is any way to determine the type of that field
> in the Schema.
>
> We are hitting a case were the way we get the data out of a different
> database returns a TIMESTAMP, but our binary object wants a DATE. In
> this test case, I could figure out that, but in the general case,  I have a
> BinaryObject type name, and a field name, and an exception if I try to put
> the wrong type in that field.
>
> The hokey general solutions I have come up with are:
> 1) Parse the exception message to see what type it wants
> 2) Have a list of conversions to try for the source type, and step through
> them on each exception.
> 3) Get the field from an existing binary object of that type, and use the
> class of the result.   But there is the chicken/egg problem.
>
> I have found that I can create a cache on a cluster with persistence, with
> some type definition, then delete that cache, the cluster will remember the
> BinaryObjectSchema for that type, and refuse to allow me to change the
> field's type.  If I  don't remember the field's type, how can I
> build the binary object?
>
> Is there any way to delete the schema without nuking some of the
> binary-meta/marshaller files when the cluster is down?
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>



-- 

Regards

Pavel Vinokurov

Re: JTA transactions in Iginte

[Prasad Bhalerao]

Val,

Thank you for the response. As per your suggestion I will first test it
with write through approach before moving to JTA.

About JTA, I still have some doubts about how to use it.

As per the example given in this link
https://apacheignite.readme.io/v2.4/docs/transactions (Integration With JTA
section

),

I have few questions about following code.

1) As per the ignite doc, the transaction manager should be configured
suing TransactionConfiguration#setTxManagerFactory method and then this
transaction configuration should be set in ignite configuration.
  How do I get this transaction in my code?
  Does this code  "IgniteTransactions transactions =
ignite.transactions();" provides JTA transaction?
  How to and when to enlist jdbc data source in this transaction manager?

2) How to configure TMService bean ?

3) In following example how to enlist xa jdbc datasource in this
transaction? How xa resource for ignite cache is enlisted in transaction in
following example?



// Get an instance of JTA transaction manager.
TMService tms = appCtx.getComponent(TMService.class);

// Get an instance of Ignite cache.
IgniteCache cache = cache();

UserTransaction jtaTx = tms.getUserTransaction();

// Start JTA transaction.
jtaTx.begin();

try{
// Do some cache operations.
cache.put("key1",1);
cache.put("key2",2);

// Commit the transaction.
jtaTx.commit();
}
finally{
// Rollback in a case of exception.
if(jtaTx.getStatus()==Status.STATUS_ACTIVE)
jtaTx.rollback();
}


Thanks,
Prasad



On Tue, Mar 27, 2018 at 8:45 AM, vkulichenko 
wrote:

> Prasad,
>
> First, I'm not sure why you think write-though would be slower than using
> JTA. I'm probably missing something, but I believe you should at least test
> this before making decision.
>
> In any case, if you use JTA, Ignite would automatically enlist any cache
> operations into ongoing JTA transaction. You only need to do the following:
> - JTA transaction manager instance provided in Ignite's
> TransactionConfiguration is the same that starts transactions.
> - Cache operations are invoked within the same thread that started a
> transaction.
>
> Hope this helps.
>
> -Val
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Ignite integration with Tableau

[Igor Sapego]

Hello Swetha,
Also, is the node you are trying to connect to up and running?
Can you see anything in its log?

Best Regards,
Igor

On Wed, Mar 28, 2018 at 1:15 PM, Andrey Mashenkov <
andrey.mashen...@gmail.com> wrote:

> Hi Swetha,
>
> Would you please check if there is no network issue, dns name resolved
> correctly and 10800 port is not blocked by firewall?
> E.g. you can try to ping host and if it is ok then try connect to 
> bkcttplna0***:10800
> via telnet.
>
> On Wed, Mar 28, 2018 at 12:54 PM, Swetha  wrote:
>
>> Hi,
>>
>> Im trying to integrate Ignite and tableau..
>>
>> Steps i have followed:
>>
>> I have taken ODBC driver installer from this path
>> /Ignite_Home/platforms/cpp/bin/odbc/ignite-odbc-amd64.msi to my windows
>> local and installed.
>>
>> Now im able to find Apache Ignite in the list to add new DSN. I have
>> configured with below details
>>
>> DSN Name: LocalApacheIgniteDSN
>> Address: bkcttplna0***:10800
>> Schema Name: PUBLIC
>> Page Size: 1024
>> version:2.3.0
>>
>> In tableau ---> other ODBC---> selected LocalApacheIgniteDSN DSN and
>> clicked
>> connect.
>> Its unable to connect to server.
>>
>> Please let me know if im missing anything here...
>>
>>
>>
>>
>> --
>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>
>
>
>
> --
> Best regards,
> Andrey V. Mashenkov
>

Re: Any idea what this is ?

[Mikael]

Hi!

It behaves a bit different if I try to use 
BinaryConfiguration.SetClassNames, I added the following to the Ignite 
configuration, I hope that is the correct way to do it ?


http://www.springframework.org/schema/beans;
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
   xmlns:util="http://www.springframework.org/schema/util;
   xsi:schemaLocation="
    http://www.springframework.org/schema/beans
    http://www.springframework.org/schema/beans/spring-beans.xsd
    http://www.springframework.org/schema/util
http://www.springframework.org/schema/util/spring-util.xsd;>
    class="org.apache.ignite.configuration.IgniteConfiguration">

    
  class="org.apache.ignite.configuration.BinaryConfiguration">

    
   
org.usf.gateway.service.RtuServiceWrapper
   
    
  
    
    ... the rest of the configuration


Without the above I got the same as before:

13:01:03 [srvc-deploy-#50] ERROR: Failed to initialize service (service 
will not be deployed): RTU_1_10
org.apache.ignite.IgniteCheckedException: Cannot find metadata for 
object with compact footer: -389806882
    at 
org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:9908) 
[ignite-core-2.4.0.jar:2.4.0]
    at 
org.apache.ignite.internal.processors.service.GridServiceProcessor.copyAndInject(GridServiceProcessor.java:1422) 
~[ignite-core-2.4.0.jar:2.4.0]
    at 
org.apache.ignite.internal.processors.service.GridServiceProcessor.redeploy(GridServiceProcessor.java:1343) 
[ignite-core-2.4.0.jar:2.4.0]
    at 
org.apache.ignite.internal.processors.service.GridServiceProcessor.processAssignment(GridServiceProcessor.java:1932) 
[ignite-core-2.4.0.jar:2.4.0]
    at 
org.apache.ignite.internal.processors.service.GridServiceProcessor.onSystemCacheUpdated(GridServiceProcessor.java:1595) 
[ignite-core-2.4.0.jar:2.4.0]
    at 
org.apache.ignite.internal.processors.service.GridServiceProcessor.access$300(GridServiceProcessor.java:124) 
[ignite-core-2.4.0.jar:2.4.0]
    at 
org.apache.ignite.internal.processors.service.GridServiceProcessor$ServiceEntriesListener$1.run0(GridServiceProcessor.java:1577) 
[ignite-core-2.4.0.jar:2.4.0]
    at 
org.apache.ignite.internal.processors.service.GridServiceProcessor$DepRunnable.run(GridServiceProcessor.java:2008) 
[ignite-core-2.4.0.jar:2.4.0]
    at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 
[?:1.8.0_144]
    at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 
[?:1.8.0_144]

    at java.lang.Thread.run(Thread.java:748) [?:1.8.0_144]
Caused by: org.apache.ignite.binary.BinaryObjectException: Cannot find 
metadata for object with compact footer: -389806882
    at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:2008) 
~[ignite-core-2.4.0.jar:2.4.0]
    at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:284) 
~[ignite-core-2.4.0.jar:2.4.0]
    at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:183) 
~[ignite-core-2.4.0.jar:2.4.0]
    at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:162) 
~[ignite-core-2.4.0.jar:2.4.0]
    at 
org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:310) 
~[ignite-core-2.4.0.jar:2.4.0]
    at 
org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:99) 
~[ignite-core-2.4.0.jar:2.4.0]
    at 
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:82) 
~[ignite-core-2.4.0.jar:2.4.0]
    at 
org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:9902) 
[ignite-core-2.4.0.jar:2.4.0]

    ... 10 more

When I added the above to the configuration file I get this instead:

13:04:28 [srvc-deploy-#50] ERROR: Failed to initialize service (service 
will not be deployed): RTU_1_10
org.apache.ignite.IgniteCheckedException: Cannot find schema for object 
with compact footer [typeId=-389806882, schemaId=1942057561]
    at 
org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:9908) 
[ignite-core-2.4.0.jar:2.4.0]
    at 
org.apache.ignite.internal.processors.service.GridServiceProcessor.copyAndInject(GridServiceProcessor.java:1422) 
~[ignite-core-2.4.0.jar:2.4.0]
    at 
org.apache.ignite.internal.processors.service.GridServiceProcessor.redeploy(GridServiceProcessor.java:1343) 
[ignite-core-2.4.0.jar:2.4.0]
    at 
org.apache.ignite.internal.processors.service.GridServiceProcessor.processAssignment(GridServiceProcessor.java:1932) 
[ignite-core-2.4.0.jar:2.4.0]
    at 
org.apache.ignite.internal.processors.service.GridServiceProcessor.onSystemCacheUpdated(GridServiceProcessor.java:1595) 
[ignite-core-2.4.0.jar:2.4.0]
    at 
org.apache.ignite.internal.processors.service.GridServiceProcessor.access$300(GridServiceProcessor.java:124) 

Re: Determining BinaryObject field type

[David Harvey]

 I had stopped at BinaryObject, and didn't follow the indirection though
type() to BinaryType. I think I assumed that this had only information at
the higher level, and wouldn't drill down into the fields.
This also answers a question about how to enumerate the fields.

Thanks.
-DH

On Wed, Mar 28, 2018 at 3:10 AM, Pavel Vinokurov 
wrote:

> Dave,
>
> I suppose there isn't way to delete the schema.
> You could get the meta information about binary objects using Ignite#binary()
> method.
> For example ignite.binary().type("package.Employeee").
> fieldTypeName("name").
>
>
>
> Thanks,
> Pavel
>
> 2018-03-24 1:10 GMT+03:00 Dave Harvey :
>
>> Once a BinaryObjectSchema is created, it is not possible to change the
>> type
>> of a field for a known field name.
>>
>> My question is whether there is any way to determine the type of that
>> field
>> in the Schema.
>>
>> We are hitting a case were the way we get the data out of a different
>> database returns a TIMESTAMP, but our binary object wants a DATE. In
>> this test case, I could figure out that, but in the general case,  I have
>> a
>> BinaryObject type name, and a field name, and an exception if I try to put
>> the wrong type in that field.
>>
>> The hokey general solutions I have come up with are:
>> 1) Parse the exception message to see what type it wants
>> 2) Have a list of conversions to try for the source type, and step through
>> them on each exception.
>> 3) Get the field from an existing binary object of that type, and use the
>> class of the result.   But there is the chicken/egg problem.
>>
>> I have found that I can create a cache on a cluster with persistence, with
>> some type definition, then delete that cache, the cluster will remember
>> the
>> BinaryObjectSchema for that type, and refuse to allow me to change the
>> field's type.  If I  don't remember the field's type, how can I
>> build the binary object?
>>
>> Is there any way to delete the schema without nuking some of the
>> binary-meta/marshaller files when the cluster is down?
>>
>>
>>
>> --
>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>
>
>
>
> --
>
> Regards
>
> Pavel Vinokurov
>

Disclaimer

The information contained in this communication from the sender is 
confidential. It is intended solely for use by the recipient and others 
authorized to receive it. If you are not the recipient, you are hereby notified 
that any disclosure, copying, distribution or taking action in relation of the 
contents of this information is strictly prohibited and may be unlawful.

This email has been scanned for viruses and malware, and may have been 
automatically archived by Mimecast Ltd, an innovator in Software as a Service 
(SaaS) for business. Providing a safer and more useful place for your human 
generated data. Specializing in; Security, archiving and compliance. To find 
out more visit the Mimecast website.

Re: [2.4.0] Cluster unrecoverable after node failure

[Pavel Vinokurov]

Hi Jose,

>>
Caused by: class org.apache.ignite.spi.IgniteSpiException: Node with set up
BaselineTopology is not allowed to join cluster without one
>>

That is expected behavior. The "Crashed" node has the empty baseline. Nodes
with a old baseline could not connect to the cluster with empty baseline
topology.
So the node with data should start first.

Baseline topology described in following pages:
https://apacheignite.readme.io/docs/cluster-activation#section-baseline-topology
https://cwiki.apache.org/confluence/display/IGNITE/IEP-4+Baseline+topology+for+caches


Thanks,
Pavel

2018-03-24 17:59 GMT+03:00 joseheitor :

> Thanks Arseny - I really appreciate your assistance!
>
> The config files that I use are included in the attached archive.
> ignite-replicated.zip
>  t1652/ignite-replicated.zip>
>
> Let me know if you need anything else, or any clarification?
>
> Below (for your reference) the SQL commands that I use, to populate the
> database with test data:
>
> DROP TABLE PUBLIC.Person
> DROP TABLE PUBLIC.City
>
> CREATE TABLE PUBLIC.City (
>   id LONG PRIMARY KEY, name VARCHAR)
>   WITH "TEMPLATE=REPLICATED, BACKUPS=1, ATOMICITY=TRANSACTIONAL,
> WRITE_SYNCHRONIZATION_MODE=FULL_SYNC"
>
> CREATE TABLE PUBLIC.Person (
>   id LONG, name VARCHAR, city_id LONG, PRIMARY KEY (id, city_id))
>   WITH "TEMPLATE=REPLICATED, BACKUPS=1, ATOMICITY=TRANSACTIONAL,
> WRITE_SYNCHRONIZATION_MODE=FULL_SYNC"
>
> INSERT INTO PUBLIC.City (id, name) VALUES (1, 'Forest Hill')
> INSERT INTO PUBLIC.City (id, name) VALUES (2, 'Denver')
> INSERT INTO PUBLIC.City (id, name) VALUES (3, 'St. Petersburg')
> INSERT INTO PUBLIC.Person (id, name, city_id) VALUES (1, 'John Doe', 3)
> INSERT INTO PUBLIC.Person (id, name, city_id) VALUES (2, 'Jane Roe', 2)
> INSERT INTO PUBLIC.Person (id, name, city_id) VALUES (3, 'Mary Major', 1)
> INSERT INTO PUBLIC.Person (id, name, city_id) VALUES (4, 'Richard Miles',
> 2)
>
> SELECT p.name, c.name
> FROM PUBLIC.Person p, PUBLIC.City c
> WHERE p.city_id = c.id AND c.name = 'Denver'
>
> SELECT COUNT(*) FROM PUBLIC.Person
> SELECT COUNT(*) FROM PUBLIC.City
>
> DELETE FROM PUBLIC.Person WHERE name = 'Jane Roe'
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>



-- 

Regards

Pavel Vinokurov

Ignite integration with Tableau

[Swetha]

Hi,

Im trying to integrate Ignite and tableau.. 

Steps i have followed:

I have taken ODBC driver installer from this path
/Ignite_Home/platforms/cpp/bin/odbc/ignite-odbc-amd64.msi to my windows
local and installed.

Now im able to find Apache Ignite in the list to add new DSN. I have
configured with below details

DSN Name: LocalApacheIgniteDSN
Address: bkcttplna0***:10800
Schema Name: PUBLIC
Page Size: 1024
version:2.3.0

In tableau ---> other ODBC---> selected LocalApacheIgniteDSN DSN and clicked
connect.
Its unable to connect to server. 

Please let me know if im missing anything here...




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

Re: Ignite integration with Tableau

[Andrey Mashenkov]

Hi Swetha,

Would you please check if there is no network issue, dns name resolved
correctly and 10800 port is not blocked by firewall?
E.g. you can try to ping host and if it is ok then try connect to
bkcttplna0***:10800
via telnet.

On Wed, Mar 28, 2018 at 12:54 PM, Swetha  wrote:

> Hi,
>
> Im trying to integrate Ignite and tableau..
>
> Steps i have followed:
>
> I have taken ODBC driver installer from this path
> /Ignite_Home/platforms/cpp/bin/odbc/ignite-odbc-amd64.msi to my windows
> local and installed.
>
> Now im able to find Apache Ignite in the list to add new DSN. I have
> configured with below details
>
> DSN Name: LocalApacheIgniteDSN
> Address: bkcttplna0***:10800
> Schema Name: PUBLIC
> Page Size: 1024
> version:2.3.0
>
> In tableau ---> other ODBC---> selected LocalApacheIgniteDSN DSN and
> clicked
> connect.
> Its unable to connect to server.
>
> Please let me know if im missing anything here...
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>



-- 
Best regards,
Andrey V. Mashenkov

Re: Redis KEYS command?

[Andrey Mashenkov]

Hi,

As I understand, you need this command in SQL query, right?
AFAIK, there is no plans to add Redis dialect support.

If you need a way to achieve same results via SQL query (JDBC\ODBC for
example),
you can try to use custom SQL functions [1].


[1] https://apacheignite-sql.readme.io/docs/custom-sql-functions


On Tue, Mar 27, 2018 at 8:26 PM, joseheitor  wrote:

> Thanks for the suggestion Andrey.
>
> We are wishing to keep our code-base compatible with Redis, so not
> Ignite-specific code.
>
> But we do need support for the Redis KEYS command...
>
> Jose
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>



-- 
Best regards,
Andrey V. Mashenkov

Re: Redis KEYS command?

[aealexsandrov]

Hi Jose,

All availavle information about ingine/redis compatibility you can see here:

https://apacheignite.readme.io/docs/redis

If you are going tobe informed about the last information about future
integrations then you can read articleы from еру official site:

https://www.gridgain.com/search#!/?s=Redis

Best Regards,
Andrei 



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

Baseline Topology and Node Failure

[Dave Harvey]

The introduction in 2.4 of Baselines seems quite helpful.   If a node
restarts, it will avoid excessive rebalancing.
What is unclear from the documentation is what happens in the case  where a
node fails, and doesn't come back.   I'm assuming that in fact nothing
happens, except that the backups on that node are now offline, 
some backups may have been promoted to primaries, and the cluster continues
to function, but not rebalancing (but that does not appear to be stated).

My question is:  After this event is detected, and something decides to
replace the node, what  process should be used to ensure that the new node
replaces the old one.  Is it sufficient to simply set a new baseline
("--baseline set"), and the minimum amount of data movement will occur?  Or
is there something that needs to be done to get the  right node IDs, or
replace the old node with the new one?

It is unclear what triggers rebalancing, e.g., --baseline remove or just
--baseline set



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

Running heavy queries on Ignite cluster on backing store directly without impacting the cluster

[Naveen]

Hi

I am using ignite 2.3 with native persistence layer as backing store

We do have close to half to 1 billion records in each of the tables.

There are some adhoc requirements to query the tables with diffrent where
conditions, columns which we use in where clause may not have indexes, which
may take time to execute the query, but it should slow the down or crash the
cluster. We are not using eviction, all our data is residing in RAM.

My question is - shall we have any means to run the queries directly on
persistence store instead of on RAM, so that whatever queries we run will
not impact cluster ??

Hope you understood my requirement ?

Thanks
Naveen



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

Re: Error: class org.apache.ignite.IgniteException: Ignite instance with this name has already been started: igniteDual

[Naveen]

The reason I was creating a new client for every thread is I am using
datastreamer which has all the configurations/properties per client basis.
Thats why I am using a new client for each thread, it was working fine when
I used native persistence alone, now with this config XML which is used for
dual backing store - native and Oracle, which is failing in this case.

Thanks
naveen



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

Re: Assuring quorum

[Ariel Tubaltsev]

Makes sense.
Thank you.
Ariel



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

Re: Getting "BinaryObjectException: Failed to deserialize object" while trying to execute the application using multi node

[Michael Jay]

Hi, val. I just met with the same problem. Would you mind giving more
detailed solutions? thanks



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

Re: Getting "BinaryObjectException: Failed to deserialize object" while trying to execute the application using multi node

[vkulichenko]

Michael,

There is no much detail to add. Although it's technically possible to
serialize lambdas and anonymous classes, it's usually not recommended, as
they can reference some objects from outside. If these objects are not
serializable (or not intended to be serialized), you're likely to get errors
and performance issues that are not easy to isolate.

To be on safe side it's better to use static classes instead for anything
that is serialized and sent across network. That gives you full control and
therefore this approach is less error-prone.

-Val



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

Upgrade from 2.1.0 to 2.4.0 resulting in error within transaction block

[smurphy]

Code works in Ignite 2.1.0. Upgrading to 2.4.0 produces the stack trace
below. The delete statement that is causing the error is:

SqlFieldsQuery sqlQuery = new SqlFieldsQuery("delete from EngineFragment
where " + criteria());
fragmentCache.query(sqlQuery.setArgs(criteria.getArgs()));

The code above is called from within a transactional block managed by a
PlatformTransactionManager which is in turn managed by Spring's
ChainedTransactionManager. If the @Transactional annotation is removed from
the surrounding code, then the code works ok...

2018-03-28 15:50:05,748 WARN  [engine 127.0.0.1] progress_monitor_2 unknown
unknown {ProgressMonitorImpl.java:112} - Scan
[ec7af5e8-a773-40fd-9722-f81103de73dc] is unable to process!
javax.cache.CacheException: Failed to process key '247002'
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:618)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:557)
at
org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:382)
at
com.company.core.dao.ignite.IgniteFragmentDao.delete(IgniteFragmentDao.java:143)
at
com.company.core.dao.ignite.IgniteFragmentDao$$FastClassBySpringCGLIB$$c520aa1b.invoke()
at 
org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
at
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:720)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
at
org.springframework.dao.support.PersistenceExceptionTranslationInterceptor.invoke(PersistenceExceptionTranslationInterceptor.java:136)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at
org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:655)
at
com.company.core.dao.ignite.IgniteFragmentDao$$EnhancerBySpringCGLIB$$ce60f71c.delete()
at
com.company.core.core.service.impl.InternalScanServiceImpl.purgeScanFromGrid(InternalScanServiceImpl.java:455)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:302)
at
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)
at com.sun.proxy.$Proxy417.purgeScanFromGrid(Unknown Source)
at 
com.company.core.core.async.tasks.PurgeTask.process(PurgeTask.java:85)
at sun.reflect.GeneratedMethodAccessor197.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:302)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
at
org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:99)
at
org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:281)
at
org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:208)
at com.sun.proxy.$Proxy418.process(Unknown Source)
at
com.company.core.core.async.impl.ProgressMonitorImpl._runTasks(ProgressMonitorImpl.java:128)
at
com.company.core.core.async.impl.ProgressMonitorImpl.lambda$null$0(ProgressMonitorImpl.java:98)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at
com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly(TrustedListenableFutureTask.java:108)
at
com.google.common.util.concurrent.InterruptibleTask.run(InterruptibleTask.java:41)
at
com.google.common.util.concurrent.TrustedListenableFutureTask.run(TrustedListenableFutureTask.java:77)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at

Re: JTA transactions in Iginte

[vkulichenko]

Prasad,

1. JTA is an abstraction that is not related to Ignite, so exact details
would depend on how your application is organized. But basically you need to
do the following:
- Acquire the transaction manager (from a container, from Spring app context
or whatever you use for management of such things).
- Start a new JTA transaction (not Ignite transaction!).
- Invoke Ignite cache operations as well as other DB operations - all of
them would be enlisted into this transaction.
- Commit transaction.

2. TMService is just an example of a transaction manager (i.e. one of the
implementation of JTA abstraction). You're not required to use specifically
this one.

3. This happens automatically when you follow the process described in point
1 above, as long as Ignite is aware of transaction manager that is used
there. To achieve this, it needs to be provided via
TransactionConfiguration.

-Val



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

Re: Determining BinaryObject field type

[Pavel Vinokurov]

Dave,

There is one way to delete meta data.
You could find typeId using ignite.binary().type("package.Employeee").typeId()
and remove .bin files in all  *binary_meta* subfolders.
​

Ignite integration with Tableau

[Swetha]

Hi,

Im trying to integrate Ignite and tableau.. 

Steps i have followed:

I have taken ODBC driver installer from this path
/Ignite_Home/platforms/cpp/bin/odbc/ignite-odbc-amd64.msi to my windows
local and installed.

Now im able to find Apache Ignite in the list to add new DSN. I have
configured with below details

DSN Name: LocalApacheIgniteDSN
Address: bkcttplna0***:10800
Schema Name: PUBLIC
Page Size: 1024
version:2.3.0

In tableau ---> other ODBC---> selected LocalApacheIgniteDSN DSN and clicked
connect.
Its unable to connect to server. 

Please let me know if im missing anything here...




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

Re: LifeCycle STOPPED question

[Chris Berry]

Thank you!!



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