Re: Inserting data into Ignite thread is hung

[praveeng]

Hi,

We are getting this issue in production continuously.
I am attaching the thread dumps of my services (ignite client
-threaddump14168.txt file  and ignite servers- 3 files ).
can any one please analyze and suggest once how to fix this issue.

threaddump14168.txt
 
 
CAI.7z   

Thanks,
Praveen



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

Re: Durable memory with native persistence isssue

[debashissinha]

I am using tpcds to to benchmark ignite with above configuration . I generate
1gb of data for the table store_sales and then manually create the table and
indexes . Then from sql line I use copy from statement to load the data file
into the table. As per the tpcds matrix the no of rows processed is correct
but when I am doing a count(*) on the same table the record count is very
less.

It shows me record processed is 2880404
Whereas count(*) gives me only 18000 rows.

Thanks & Regards
Debashis Sinha



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

Re: Client node get stuck when reconnecting to cluster

[akurbanov]

Hello,

Partition map exchange is a cluster-wide operation that needs to be finished
before cluster becomes operational on a updated topology in your case. It
was triggered by node leaving cluster prior to start of the current one.

To find out the reason why it hangs please provide logs from nodes mentioned
in partition map exchange diagnostic message:

Coordinator node: /Exchange future waiting for coordinator response
[crd=09007637-a72e-4a68-940a-10392309eb64../
Node that failed to communicate exchange message:
/remaining=[1943a94c-caa2-4082-a04b-a06913489a60../

You can find them in your work directory
igniteWorkDir=H:\apache-ignite-fabric-2.4.0-bin\work under log subdirectory,
they should be named by default as ignite-09007637.log and
ignite-1943a94c.log or you might just grep for locNodeId= and find the
necessary files. 

Regards,
Anton






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

Re: Durable memory with native persistence isssue

[akurbanov]

Hello,

This seems to be not a performance-related question, the fact that you have
mismatch between inserted rows count and count(*) doesn't feel right and
seems to be the primary issue to resolve. Could you please give more detail
on how you are trying to load your data, what is your node configuration and
what API are you using to load data?

Do you observe unexpected entry count after fully loading data and how do
you count inserted rows?

Regards,
Anton



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

Re: cotinuousquery -> Requesting mapping from grid failed for [ platformId=1, typeId=1173251103]

[akurbanov]

Hello,

This issue seems to be raised as you didn't specify binary configuration for
your C# type. Since you create your entity via sqlline (actually it doesn't
matter where do you create it), Ignite knows nothing about C# type mapping
to Java type:
/Caused by: java.lang.ClassNotFoundException: Requesting mapping from grid 
failed 
 for [platformId=1, typeId=1173251103] /

Please follow the links for docs and samples to find out how to make it work
correctly:
1. https://apacheignite-net.readme.io/docs/platform-interoperability
Refer to simple name mapper (which ignores namespace) can be used to avoid
this problem. It should be configured both on .NET and Java sides, allow it
inside your xml configuration or the one that you prefer.

2. https://ptupitsyn.github.io/Ignite-Multi-Platform-Cluster  
Initially written for 1.7, 2.0+ version could be found on github:
https://github.com/ptupitsyn/ignite-multi-platform-demo/tree/ignite-2.0

Regards,
Anton



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

Re: odbc 2.7 columns issue

[wt]

Thanks Igor

I didn't think about the underscores in the names. Will try it in the
morning. Thanks for the tip, hopefully it will get me over the line for the
demo to the COO. 





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

Re: remote filter for ContinuousQuery on C#

[jcalahor]

that helped, thx!




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

cotinuousquery -> Requesting mapping from grid failed for [ platformId=1, typeId=1173251103]

[jcalahor]

H,

i'm getting exception on the server nodes when a new City record is added .
The c# code is below:

namespace ignite_test
{
class Program
{
  

class CityEventListener : ICacheEntryEventListener

{

public void OnEvent(IEnumerable>
evts)

{

foreach (var evt in evts)

Console.WriteLine(evt.Value);

}

}



static void Main(string[] args)
{
Ignition.ClientMode = true;
using (var ignite =
Ignition.Start(@"C:\apache_ignite\examples\config\example-ignite.xml"))
{
var persons = ignite.GetCache("City");

var localListener = new CityEventListener();
var qry = new ContinuousQuery(localListener);
{
qry.Filter = new RemoteFilter();
}
//var query = new SqlQuery("City", "select * from City where
id = 1");
var queryHandle = persons.QueryContinuous(qry);
//foreach (var entry in queryHandle.GetInitialQueryCursor())
  ///  Console.WriteLine("key={0}, val={1}", entry.Key,
entry.Value);
Console.ReadLine();
}


}
}
}




namespace ignite_shared
{
public class City
{
public City(int id, string name)

{
Name = name;
Id = id;
}

[QuerySqlField]
public int Id { get; set; }
[QuerySqlField]
public string Name { get; set; }
}

}

namespace ignite_shared
{
public class RemoteFilter : ICacheEntryEventFilter
{
public bool Evaluate(ICacheEntryEvent evt)
{
return true;
//return (evt.Value.Id == 1);
}
}
}



One i start the server node, i go into SQlLine and execute the following
command:
CREATE TABLE City (id int PRIMARY KEY, name VARCHAR) WITH
"template=replicated, CACHE_NAME=City, VALUE_TYPE=ignite_shared.City";

then
insert into City (id, name) values (1, 'Lima');


then I start the C# application with no issues, and then i do this on
sqlline:
insert into City (id, name) values (2, 'Quito');


Result (on server node):

[14:07:26,499][SEVERE][sys-#55][] Failure in Java callback
class org.apache.ignite.IgniteException: Platform
error:Apache.Ignite.Core.Binar
y.BinaryObjectException: Requesting mapping from grid failed for
[platformId=1,
typeId=1173251103] ---> Apache.Ignite.Core.Common.JavaException: class
org.apach
e.ignite.binary.BinaryObjectException: Requesting mapping from grid failed
for [
platformId=1, typeId=1173251103]
at
org.apache.ignite.internal.processors.platform.binary.PlatformBinaryP
rocessor.processInStreamOutStream(PlatformBinaryProcessor.java:126)
at
org.apache.ignite.internal.processors.platform.PlatformTargetProxyImp
l.inStreamOutStream(PlatformTargetProxyImpl.java:136)
at
org.apache.ignite.internal.processors.platform.callback.PlatformCallb
ackUtils.inLongOutLong(Native Method)
at
org.apache.ignite.internal.processors.platform.callback.PlatformCallb
ackGateway.continuousQueryListenerApply(PlatformCallbackGateway.java:377)
at
org.apache.ignite.internal.processors.platform.utils.PlatformUtils.ap
plyContinuousQueryEvents(PlatformUtils.java:556)
at
org.apache.ignite.internal.processors.platform.cache.query.PlatformCo
ntinuousQueryImpl.onUpdated(PlatformContinuousQueryImpl.java:200)
at
org.apache.ignite.internal.processors.cache.query.continuous.CacheCon
tinuousQueryHandler.notifyLocalListener(CacheContinuousQueryHandler.java:942)
at
org.apache.ignite.internal.processors.cache.query.continuous.CacheCon
tinuousQueryHandler.notifyCallback0(CacheContinuousQueryHandler.java:786)
at
org.apache.ignite.internal.processors.cache.query.continuous.CacheCon
tinuousQueryHandler.notifyCallback(CacheContinuousQueryHandler.java:727)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProces
sor.processNotification(GridContinuousProcessor.java:1618)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProces
sor.access$1800(GridContinuousProcessor.java:108)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProces
sor$8.onMessage(GridContinuousProcessor.java:1003)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invok
eListener(GridIoManager.java:1556)
at
org.apache.ignite.internal.managers.communication.GridIoManager.acces
s$4100(GridIoManager.java:125)
at
org.apache.ignite.internal.managers.communication.GridIoManager$GridC
ommunicationMessageSet.unwind(GridIoManager.java:2752)
at
org.apache.ignite.internal.managers.communication.GridIoManager.unwin
dMessageSet(GridIoManager.java:1516)
at
org.apache.ignite.internal.managers.communication.GridIoManager.acces
s$4400(GridIoManager.java:125)
at
org.apache.ignite.internal.managers.c

Re: npe: Failed to reinitialize local partition

[Ilya Kasnacheev]

Hello!

What is the cache template here, and where is it defined?

I don't see any changes to the test. Can you modify it so that it will
display your case?

Regard,
-- 
Ilya Kasnacheev


чт, 25 окт. 2018 г. в 5:31, wangsan :

> IgniteTwoRegionsRebuildIndexTest.java
> <
> http://apache-ignite-users.70518.x6.nabble.com/file/t1807/IgniteTwoRegionsRebuildIndexTest.java>
>
>
>
> The file is the test case.
> I use getOrCreateCache with name. But the cache template I have beed
> defined
> before.When reconnect ,It looks like the cache template not work.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Cluster freeze with SSL enabled and JDK 11

[Ilya Kasnacheev]

Hello!

I have tried to run the test with protocol "TLSv1.2", didn't see any
difference.

Regards,
-- 
Ilya Kasnacheev


ср, 24 окт. 2018 г. в 20:23, Loredana Radulescu Ivanoff :

> Hello again,
>
> I am working on getting the full SSL logs over to you, but I have one more
> question in between: TLS v1.3 is enabled by default in JDK 11, and my app
> is using TLS v1.2 specifically. There's a known issue that's recently
> addressed by the JDK related to TLS v1.3 half close policy, details here:
> https://bugs.java.com/view_bug.do?bug_id=8207009
>
> Would you be able to confirm whether your SSL test runs successfully when
> the connecting client/server use TLS v.12 specifically ?
>
> FYI, I have tried specifically disabling TLS v1.3 using both the
> "jdk.tls.client.protocols" and "jdk.tls.server.protocols" system
> properties, and also set "jdk.tls.acknowledgeCloseNotify" to true on both
> sides as indicated here - https://bugs.java.com/view_bug.do?bug_id=8208526
>
> Based on my explorations so far, I think this may be a JDK issue
> (specifically in the JSSE provider) that has not been addressed yet. Either
> way, do you think three is anything that could be done in Ignite to
> explicitly close the connection on both sides in a scenario like this ?
>
> What I can safely share on the SSL logs so far is this (both nodes get
> stuck, node 1 in failing to close the SSL connection, node 2 in waiting for
> partition exchange)
>
> Node 1:
>
> "2018-10-23 14:18:40.981 PDT|SSLEngineImpl.java:715|Closing inbound of
> SSLEngine
> javax.net.ssl|ERROR|3F|grid-nio-worker-tcp-comm-1-#26%%|2018-10-23
> 14:18:40.981 PDT|TransportContext.java:313|Fatal (INTERNAL_ERROR): closing
> inbound before receiving peer's close_notify (
> "throwable" : {
>   javax.net.ssl.SSLException: closing inbound before receiving peer's
> close_notify
>   at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:129)
>   at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:117)
>   at
> java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:308)
>   at
> java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:264)
>   at
> java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:255)
>   at
> java.base/sun.security.ssl.SSLEngineImpl.closeInbound(SSLEngineImpl.java:724)
>   at
> org.apache.ignite.internal.util.nio.ssl.GridNioSslHandler.shutdown(GridNioSslHandler.java:185)
>   at
> org.apache.ignite.internal.util.nio.ssl.GridNioSslFilter.onSessionClosed(GridNioSslFilter.java:223)
>   at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedSessionClosed(GridNioFilterAdapter.java:95)
>   at
> org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onSessionClosed(GridNioServer.java:3447)
>   at
> org.apache.ignite.internal.util.nio.GridNioFilterChain.onSessionClosed(GridNioFilterChain.java:149)
>   at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.close(GridNioServer.java:2689)
>   at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2002)
>   at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1764)
>   at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at java.base/java.lang.Thread.run(Thread.java:834)}
>
> )
> 2018-10-23 14:18:40.981 PDT|SSLSessionImpl.java:753|Invalidated session:
> Session(1540329505125|TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384)
> DEBUG 14:18:40,981-0700 [] communication.tcp.TcpCommunicationSpi: Unable
> to correctly close inbound data stream (will ignore) "
>
>
> Server 2
>
> "javax.net.ssl|DEBUG|46|tcp-disco-sock-reader-#4%%|2018-10-23 14:18:09.194
> PDT|SSLSocketOutputRecord.java:310|WRITE: TLS12 application_data, length = 1
> javax.net.ssl|DEBUG|46|tcp-disco-sock-reader-#4%%|2018-10-23 14:18:09.194
> PDT|SSLCipher.java:1727|Plaintext before ENCRYPTION (
>   : 01 .
> )
> javax.net.ssl|DEBUG|46|tcp-disco-sock-reader-#4%%|2018-10-23 14:18:09.194
> PDT|SSLSocketOutputRecord.java:324|Raw write (
>   : 17 03 03 00 19 00 00 00   00 00 00 00 A1 45 E5 C8  .E..
>   0010: 27 3D EE E2 89 4A 0F DD   B6 9A 2A A8 5F 6B'=...J*._k
> )
> WARN 14:18:10,585-0700 [*Initialization*]
> processors.cache.GridCachePartitionExchangeManager: Still waiting for
> initial partition map exchange "
>
> On Mon, Oct 22, 2018 at 12:31 AM Ilya Kasnacheev <
> ilya.kasnach...@gmail.com> wrote:
>
>> Hello!
>>
>> I would suggest regular (or DEBUG) Ignite logs + SSL debug logs.
>>
>>
>> https://docs.oracle.com/javase/7/docs/technotes/guides/security/jsse/ReadDebug.html
>>
>> Regards,
>> --
>> Ilya Kasnacheev
>>
>>
>> пт, 19 окт. 2018 г. в 20:58, Loredana Radulescu Ivanoff <
>> lradu...@tibco.com>:
>>
>>> Definitely - do you want debug logs, and if yes, should I enable them on
>>> all Ignite packages, or just for certain ones? Any other diagn

Re: Total Size seems to keep growing

[ilya.kasnacheev]

Hello!

After more experiments with your reproducer, I have filed an issue:
https://issues.apache.org/jira/browse/IGNITE-10011

Regards,



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

Re: Cache access blocked on destroy

[akurbanov]

Hello,

I would definitely suggest you to upgrade to latest Ignite versions as a
vast number of issues has been fixed since 1.9:
https://issues.apache.org/jira/browse/IGNITE-6035
https://issues.apache.org/jira/browse/IGNITE-2714
https://issues.apache.org/jira/browse/IGNITE-8531
https://issues.apache.org/jira/browse/IGNITE-8021
https://issues.apache.org/jira/browse/IGNITE-7319

Please pay attention to the last one, this seems to be exactly your use
case. A lot of things happen on both node and cluster levels when you call
cache.destroy(), since this is a minor exchange which involves all server
nodes where this cache exists, also a checkpoint along with write-ahead log
flush is performed. 

Anyway, could you please give more details on how exactly your issue is
meant to be reproduced (check the code on IGNITE-7319 if it is looks like
your case), provide some logs and thread dumps to analyze.

Regards,
Anton



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

Re: odbc 2.7 columns issue

[Igor Sapego]

Ok,

This is an another bug, related to escaped table names. See [1].

I'm working on it currently. Meanwhile you can use tables without
underscores in names as a workaround.

[1] - https://issues.apache.org/jira/browse/IGNITE-10009

Best Regards,
Igor


On Thu, Oct 25, 2018 at 10:13 AM wt  wrote:

> hi
>
> here is the odbc log file
>
> odbc.log
> 
>
> My server configuration
>
>xmlns="http://ignite.apache.org/schema/dotnet/IgniteConfigurationSection";>
> 
>   
> 
>   127.0.0.1:47500..47509
> 
>   
> 
> 
>maxSize="124288000"/>
>   
>  persistenceEnabled="true" maxSize="524288000" evictionThreshold="0.85"  />
>  maxSize="524288000" evictionThreshold="0.9"/>
>   
> 
>   
>
>
> i have 1 table i am trying to view
>
> {
>   "tablename": "ESG_Focus",
>   "fields": [
> {
>   "name": "COMPANYID",
>   "datatype": "java.lang.Integer"
> },
> {
>   "name": "ESG_FOCUS_ITEM",
>   "datatype": "java.lang.String"
> },
> {
>   "name": "ESG_FOCUS_VALUE",
>   "datatype": "java.lang.String"
> },
> {
>   "name": "ID",
>   "datatype": "java.util.UUID"
> },
> {
>   "name": "RECORD_VALID_FROM",
>   "datatype": "java.sql.Timestamp"
> },
> {
>   "name": "RECORD_VALID_TO",
>   "datatype": "java.sql.Timestamp"
> }
>   ],
>   "indexinfo": []
> }
>
>
>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Automated cache generation to clone a SQL schema?

[Alexey Kuznetsov]

Hi, sv!

Before ignite-2.0 & Web Console there was "Schema Import Utility"

See https://github.com/apache/ignite/tree/ignite-1.9/modules/schema-import

Code of that utility is written on Java.

It simply read metadata from JDBC and generate stuff.
You can write you own custom utility in a couple of days.

-- 
Alexey Kuznetsov

Re: Cache stats like number of cache hits, misses, reads, write, avg

[aealexsandrov]

Hi,

Try to set setMetrcis for both regionCfg and storageCfg too. Is it help?

BR,
Andrei 



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

Durable memory with native persistence isssue

[debashissinha]

Hi ,
I want to load 1tb of data in cache and have only 9gb of ram at my disposal.
I have three machines in cluster each having 9gb of memory. Please suggest
how can i achieve best performance using durable memory and native
persistence. 

I tried once but the number of rows inserted vs the count(*) from the same
table doesn't match. 

Please suggest

Thanks & Regards
Debashis Sinha



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

Re: Ignite locking when affinity is used.

[kotamrajuyashasvi]

Hi

MYCACHE is the name of the cache that is being used. We are observing the
below Exception in server logs: cache mode : TRANSACTIONAL , PESSIMISTIC ,
REPEATABLE_READ

[01:46:41,022][SEVERE][grid-timeout-worker-#135][GridDhtColocatedCache]
 Failed to acquire lock for request: GridNearLockRequest
[topVer=AffinityTopologyVersion [topVer=165, minorTopVer=0], miniId=1,
dhtVers=[null, null, null, null, null, null, null, null, null, null, null,
null, null, null, null, null, null, null, null, null, null, null, null,
null, null, null, null, null, null, null, null, null, null, null, null,
null, null, null, null, null, null, null, null, null, null, null, null,
null, null, null, null, null], subjId=d669161f-60d6-4d5d-89d2-31fbaf38c3ef,
taskNameHash=0, createTtl=-1, accessTtl=-1, flags=7, filter=null,
super=GridDistributedLockRequest
[nodeId=d669161f-60d6-4d5d-89d2-31fbaf38c3ef, nearXidVer=GridCacheVersion
[topVer=151116344, order=1540895195350, nodeOrder=159], threadId=557,
futId=8f77c6a7661-f7f675c6-2a1a-4f4f-9d74-054d7905822e, timeout=53696,
isInTx=true, isInvalidate=false, isRead=true, isolation=REPEATABLE_READ,
retVals=[true, true, true, true, true, true, true, true, true, true, true,
true, true, true, true, true, true, true, true, true, true, true, true,
true, true, true, true, true, true, true, true, true, true, true, true,
true, true, true, true, true, true, true, true, true, true, true, true,
true, true, true, true, true], txSize=0, flags=0, keysCnt=52,
super=GridDistributedBaseMessage [ver=GridCacheVersion [topVer=151116344,
order=1540895195350, nodeOrder=159], committedVers=null,
rolledbackVers=null, cnt=0, super=GridCacheIdMessage [cacheId=1737458824
class
org.apache.ignite.internal.transactions.IgniteTxTimeoutCheckedException:
Failed to acquire lock within provided timeout for transaction
[timeout=53696, 

Following are my concerns:

1. dhtVers=[null, null, null, null, null, null, null, null, null, null,
null, null, null, null, null, null, null, null, null, null, null, null,
null, null, null, null, null, null, null, null, null, null, null, null,
null, null, null, null, null, null, null, null, null, null, null, null,
null, null, null, null, null, null].  What does this mean or indicate ?

2. The transaction timeout set by us is 6. But the timeout in exception
message is : timeout=53696.
According to :
http://apache-ignite-users.70518.x6.nabble.com/Ignite-2-0-transaction-timeout-not-holding-up-td16462.html
: It means that in a transaction different nodes are involved in locking.
But in our logic we use affinity and all locks should happen with in same
partition/node due to same affinity key . Is it possible that lock is being
acquired on backup partition also and failed ?

Please let us know the possibilities for cause of this Exception.




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

Re: Cluster is not responsive after node segmentation and reconciliation

[Maxim.Pudov]

You definitely need to increase heap size to prevent OOM errors.
./ignite.sh -J-Xmx4g
If it doesn't help, provide full logs from all nodes.



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

Re: Web Console, multiple clusters connected: display of cluster names

[akurbanov]

Hello,

There is an issue and discussion on dev list for this:
https://issues.apache.org/jira/browse/IGNITE-6597
http://apache-ignite-developers.2346864.n4.nabble.com/Cluster-name-td15490.html

As a workaround you may use IGNITE_CLUSTER_NAME environment variable set for
all nodes in the cluster to a specific value. 

Regards,
Anton



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

Web Console, multiple clusters connected: display of cluster names

[sv]

If there is more than one cluster connected to the Web Console, is there a
way to control how each cluster is named in the dropdown for the clusters? 
Currently being displayed as, eg, "Cluster 57B0C9E1", which is not very
human-friendly.   Is there a way to control this through some cluster
parameters?





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

Re: Ignite locking when affinity is used.

[Evgenii Zhuravlev]

Hi,

Here is an Ignite Key-Value Transactions Architecture design duocment:
https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Key-Value+Transactions+Architecture#IgniteKey-ValueTransactionsArchitecture-Transactions

Evgenii

чт, 25 окт. 2018 г. в 9:56, kotamrajuyashasvi :

> Hi
>
> In my ignite project a key object of a cache has one of its fields as
> affinitykeymapped. The cache has 1 backup. Using transactional mode
> pessimistic and repeatable_read mode. When we acquire lock using
> cache.get()/put() etc.. is lock only acquired on primary node where the key
> is located or tries to lock the key on all nodes ? or just both primary and
> backup ?
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: odbc 2.7 columns issue

[wt]

hi

here is the odbc log file

odbc.log
  

My server configuration

  http://ignite.apache.org/schema/dotnet/IgniteConfigurationSection";>

  

  127.0.0.1:47500..47509

  


  
  


  

  


i have 1 table i am trying to view

{
  "tablename": "ESG_Focus",
  "fields": [
{
  "name": "COMPANYID",
  "datatype": "java.lang.Integer"
},
{
  "name": "ESG_FOCUS_ITEM",
  "datatype": "java.lang.String"
},
{
  "name": "ESG_FOCUS_VALUE",
  "datatype": "java.lang.String"
},
{
  "name": "ID",
  "datatype": "java.util.UUID"
},
{
  "name": "RECORD_VALID_FROM",
  "datatype": "java.sql.Timestamp"
},
{
  "name": "RECORD_VALID_TO",
  "datatype": "java.sql.Timestamp"
}
  ],
  "indexinfo": []
}







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