1. There is no such API. Seems like a weird error in documentation. We will
fix it. If you want to make 50 gets in parallel, I think it's better to run
50 clients with the current API. You can use the same client too, but it
may be slower, depending on how many nodes you have in a cluster.
2. What
Unfortunately, we do not have Mac agents, so we can not detect when
compilation on Mac OS is broken, so yeah...
Best Regards,
Igor
On Tue, Mar 14, 2023 at 2:48 PM Ivan Daschinsky wrote:
> An ignite odbc driver works well on linux and windows OSes, but it seems
> that it is impossible to
ff:* AW: IGNITE ODBC and ADODB Recordset problem fetching data
>
>
>
> Hi Igor,
>
> here are the odbc trace files. I tried with CursorLocation client and
> server.
>
> Hope it helps.
>
> Thank you in advance.
>
>
>
> Best Regards
>
> Guido
>
&
Hi,
Can you please enable ODBC tracing as described for example at [1]
and share a trace file? It is not clear from the error message what the
problem is.
[1] -
https://learn.microsoft.com/en-us/sql/odbc/admin/setting-tracing-options
Best Regards,
Igor
On Tue, Nov 15, 2022 at 2:29 PM
Great work
Best Regards,
Igor
On Wed, Nov 16, 2022 at 1:50 PM Ivan Daschinsky
wrote:
> The Apache Ignite Community is pleased to announce the release of
> Apache IGNITE python thin client (pyignite) 0.6.0.
>
> This new release is mostly the maintenance one. However, there are some
> new
Hi,
Sorry for the late reply, I somehow missed your message.
Yes, thick client starts a JVM with the whole Ignite inside, while thin
client does not and does not depend on JDK.
Actually, thick client is not only a client but can also be a C++ server
node.
You are right, NearCache is not
Hello,
No, it's not possible right now.
Best Regards,
Igor
On Fri, Feb 18, 2022 at 1:46 PM F.D. wrote:
> Hi,
> is it possible to launch a "distributed compute" from a thin client of
> node.js? If not, do you have a workaround about it?
>
> Thanks,
> F.D.
>
>
This is possible because when you add endpoints to client's configuration
it will use all of them when sending requests (it will send them to random
nodes though). So when you send a large batches of values there won't be
a single node bottleneck, when a single node deals with a great number
of
Hi,
I'm pretty much sure it happens because Ignite is quite demanding on RAM.
How much memory is available on your machine?
Also, is there any kind of stack trace to share?
Best Regards,
Igor
On Wed, Apr 21, 2021 at 2:46 PM rakshita04
wrote:
> Hi Team,
>
> We are using ignite on our C++
There is our DDL documentation, which describes in detail how one can create
indexes on existing table [1]. It can be used with both C++ using
SqlFieldsQuery
and ODBC.
Now regarding benefits of ODBC over C++ - there are definitely memory
benefits
if you are comparing ODBC and thick C++ client as
Guys, I just want to notify you that the issue is fixed and is included in
Ignite-2.10
Best Regards,
Igor
On Thu, Feb 18, 2021 at 3:41 AM 18624049226 <18624049...@163.com> wrote:
> Hello Ilya,
>
> https://issues.apache.org/jira/browse/IGNITE-14204
> 在 2021/2/18 上午12:14, Ilya Kasnacheev 写道:
>
>
at 4:47 AM 18624049226 <18624049...@163.com> wrote:
> Hello Igor,
>
> If start two nodes on two hosts and create a cluster, you can reproduce
> this problem. If start multiple server nodes on one host, it seems that
> there is no problem.
> Thin clients only need one.
> 在 202
Hi, I've tried to reproduce an issue you described and could not reproduce
it.
Can you share more details? How many nodes do you run? How many clients
are run? Do you run any other operations in parallel?
Best Regards,
Igor
On Wed, Feb 3, 2021 at 3:00 PM 18624049226 <18624049...@163.com>
I mean, mutex should be taken for the entire transaction of course.
Best Regards,
Igor
On Thu, Jan 14, 2021 at 7:49 PM Igor Sapego wrote:
> That's true. We need to implement async reading from client socket to
> handle cases like this one properly. Currently as a workaround I can
That's true. We need to implement async reading from client socket to
handle cases like this one properly. Currently as a workaround I can
only suggest guarding the whole client with mutex or create separate
clients for threads that do transactional operations.
I filed a ticket for the issue [1].
; > https://filebin.net/5fclxod62xi36gbb
>> > <https://filebin.net/5fclxod62xi36gbb>
>> >
>> > Regards,
>> >
>> > Wolfgang
>> >
>> > Am 27.11.20 um 4:21 PM schrieb Ilya Kasnacheev:
>> >
I've tried to answer your question in your following email.
Are there any other issues?
Best Regards,
Igor
On Fri, Nov 27, 2020 at 12:50 PM Ilya Kasnacheev
wrote:
> Hello!
>
> Can you please provide a complete reproducer, with main() and all that
> stuff?
>
> You can check out the
Hi,
Starting from your last question, it's Version3.
Now to the issue you are referring to. It definitely looks like a bug to
me. It's weird
that no one has found it earlier. Looks like no one uses SQLConnect? It is
weird that
We do not have a test for that either. Anyway I filed a ticket and
Hi,
It does not crash, it is just JVM uses system signals internally, you can
safely
ignore them or just ignore any signals coming from jvm.dll.
Best Regards,
Igor
On Thu, Nov 26, 2020 at 6:15 PM Ilya Kasnacheev
wrote:
> Hello!
>
> I think there should be some kind of guide on how to debug
Yes, it is possible. See [1]
[1] -
https://ignite.apache.org/releases/latest/cppdoc/structignite_1_1IgniteConfiguration.html#ad7f632214a786dfdf8dc6f5824749e8a
Best Regards,
Igor
On Wed, Nov 18, 2020 at 3:18 PM Wolfgang Meyerle <
wolfgang.meye...@googlemail.com> wrote:
> Hi,
>
> Is it possible
Do you keep an IgniteClient instance somewhere as a global/static variable?
If so, this may not be the best idea, just move it somewhere where it will
have a predictable lifetime and where it can be destroyed before main() is
finished.
Best Regards,
Igor
On Tue, Aug 4, 2020 at 2:19 AM Igor
Dana,
I think it makes sense to add the "Stop" method to the IgniteClient class,
but currently all connections should terminate successfully once
all the instances of the class are destructed.
Also, the message does not look like a real problem to me, more like a
warning. Does anyone have a clue
Hi Dana,
"char" type is not supported by Ignite as it may have different sign on
different platforms. You can use int8_t if you want to have a byte array,
or WriteString/ReadString if you want it to be a string.
Also, I've re-factored your BinaryType code a little bit so it's more
readable:
Hi,
C++ code is not built using maven, it uses atuotools or msvc instead.
see ignite/modules/platforms/cpp/DEVNOTES.txt for instructions.
And yes, it does not require internet connection to be built.
Best Regards,
Igor
On Thu, May 28, 2020 at 1:30 PM rakshita04
wrote:
> Hi , actually we
I personally think that this feature should be implemented in Ignite,
though maybe we should first start from Continuous Queries for thin
clients.
Best Regards,
Igor
On Mon, May 25, 2020 at 6:15 PM Pavel Tupitsyn wrote:
> Marty,
>
> Continuous queries are certainly planned for thin clients,
>
Which thin client are you referring to?
Best Regards,
Igor
On Mon, May 18, 2020 at 5:09 PM scriptnull
wrote:
> I would like to break down this question into two questions.
>
> 1. Can we have key-values with different expire times in the same cache? (I
> think the answer for this is yes,
Yes, you can. You just need to combine C++ PutGet example and ODBC example,
where from C++ you take a part that puts data in cache, and from ODBC you
take
the querying part.
Best Regards,
Igor
On Wed, Apr 8, 2020 at 6:32 PM Anthony wrote:
> Hello llya,
>
> I guess I may not describe my
I'm not very experienced in Python, but if no one else wants
to take a look, I'll do it.
Best Regards,
Igor
On Sat, Mar 28, 2020 at 2:04 AM Denis Magda wrote:
> Igniters,
>
> Is any of you is skillful enough to contribute improvements to our Python
> thin client? For instance, that's one of
There is no such option currently, AFAIK
Best Regards,
Igor
On Tue, Feb 25, 2020 at 3:02 PM Abhay Gupta wrote:
> Hi ,
>
>
>
> Do we have a way to have Autoincrement field in Database for use in Thin
> Client / UNIX ODBC . The Atomic sequence help is available with Java when
> JAVA ignite is
There are no such way in ODBC, but maybe SQL guys can suggest
some solution here.
Anyway this is weird, as software that uses ODBC can actually query
ODBC driver for the case of the returned SQL symbols, and our driver
clearly states that it uses upper case.
Best Regards,
Igor
On Tue, Feb 18,
at 12:40 AM Anthony wrote:
> Yes. I was using MSVC for both of them.
>
> BTW, are the project odbc and thin-client in the ignite needed? I did not
> build them because of some compiling issues.
>
> On Mon, Feb 10, 2020 at 5:54 AM Igor Sapego wrote:
>
>> The issue looks
std::string &
> Seems that the "cfg.jvmClassPath" was not set properly?
>
> I am not familiar with java environment, should i set some environmental
> variable?
>
> Thank you!
>
> Anthony
>
> On Fri, Feb 7, 2020 at 5:20 AM Igor Sapego wrote:
>
>> Hi
>>
Hi
And what is the value of "usrCp" argument?
For me the code works just fine.
Best Regards,
Igor
On Fri, Feb 7, 2020 at 12:22 AM Anthony wrote:
> Hello,
>
> I am new to ignite C++. I am using windows 10, VS community.
>
> I keep getting Access Violation when I am trying to run the following
Ivan,
You are right. Though now we have transactions support in thin client
protocol,
It is only now implemented for Java. Also, C++ thin client yet to support
SQL.
Best Regards,
Igor
On Sat, Nov 30, 2019 at 9:35 AM Ivan Pavlukhin wrote:
> Igor,
>
> Could you please elaborate whether C++
Hello,
It's strange, we have tested it and it should work.
Are you sure, the right config is used by all nodes?
Best Regards,
Igor
On Sun, Oct 13, 2019 at 6:10 PM 朱靓 <11852...@qq.com> wrote:
> Hi
>I am new to Ignite, and i will use C# save cache and fetch with python
> and C++. After
Hello,
Such function is not supported for now. You can raise a ticket
if it's something you'd like to have in Ignite.
Best Regards,
Igor
On Mon, Sep 16, 2019 at 6:00 PM codie wrote:
> Hello,
> I have two nodes running with a TCP Discovery Spi, one is a C++ Thick
> node and one is a Java
Denis,
No ideas here. I think, it is not possible right now from pure C++.
Best Regards,
Igor
On Sat, Sep 14, 2019 at 1:02 AM Denis Magda wrote:
> Igor,
>
> Any idea how to start a cache dynamically from C++ thick client passing
> near cache settings?
>
> Don't see how we can do it know
Hello Igniters,
Soon there will be Ignite 3.0, so I though this may be a good time
to speak about abandoning Visual Studio 2010 (msvc 10.0) support,
which will allow us to move to more modern features in Ignite C++.
Any thoughts or objections? Are there people which will be critically
affected
Hi,
There is probably some error in the call, if you'd give me an example of
how you call
the script I could try to help you. But why don't you use an msi installer?
It is easier
and more reliable way to install ODBC driver on windows.
Best Regards,
Igor
On Wed, Jul 3, 2019 at 5:28 PM ilyn
Well, it seems like you start two nodes on the same host, and as first
node occupies default thin client port (10800) the second node takes
the next one (10801).
I believe you use 127.0.0.1 or something like this for your thin client
host lists which effectively means 127.0.0.1:10800. So, your
sue be addressed? Thanks, Charlie
>
> On Mon, May 13, 2019 at 9:55 AM Igor Sapego wrote:
>
>> It seems like some encoding related issue to me.
>> Added a Jira ticket: [1].
>>
>> [1] - https://issues.apache.org/jira/browse/IGNITE-11845
>>
>> Best Regards,
There are no plans for thick client for python, but there are
plans for Compute for thin clients. I think, as a first step we may
add ability to call Java jobs from python. It will still require to write
some java code from a user, but it will accept and return values
data in python's native
Maybe, you could start with these threads: [1], [2]
[1] -
https://lists.freedesktop.org/archives/pkg-config/2007-August/000218.html
[2] - https://autotools.io/pkgconfig/file-format.html
Best Regards,
Igor
On Mon, May 20, 2019 at 4:57 PM mwilliamso58
wrote:
> bump
>
>
>
> --
> Sent from:
}
> }
> }
>
> Console Output:
> MYUUID='System.Byte[]' DotnetType='System.Byte[]' DBType='VARBINARY'
>
> Should be: (According to
> https://docs.microsoft.com/en-us/sql/odbc/reference/appendixes/sql-data-types?view=sql-server-2017
> )
> MYUUI
Hi,
Sorry for not replying from the start.
This is not intentional, and, I believe, should be fixed by the next
release.
Best Regards,
Igor
On Fri, May 17, 2019 at 4:12 PM mwilliamso58
wrote:
> bump
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
indeed the nanoseconds? Apparently a Python
> datetime can have differing precisions (perhaps depending on platform)...
>
>
> Kind regards,
>
> Stéphane Thibaud
>
>
> 2019年5月16日(木) 0:10 Igor Sapego :
>
>> I believe, it's OK to pass tuple for timestamp in python, but you
f that, I assumed
> that a tuple also had to be written in an update query.
>
>
> Kind regards,
>
> Stéphane Thibaud
>
> 2019年5月15日(水) 17:59 Igor Sapego :
>
>> Stéphane,
>>
>> Can you sharer a code line, how do you try to store timestamp value?
>>
>&
Stéphane,
Can you sharer a code line, how do you try to store timestamp value?
Best Regards,
Igor
On Tue, May 14, 2019 at 7:23 PM Denis Mekhanikov
wrote:
> Stéphane,
>
> Could you provide the code, that results in this exception?
> Do you try to insert the tuple as a single field via SQL?
It seems like some encoding related issue to me.
Added a Jira ticket: [1].
[1] - https://issues.apache.org/jira/browse/IGNITE-11845
Best Regards,
Igor
On Thu, May 2, 2019 at 1:15 AM Charles Rene
wrote:
> Hello,
>
> I'm having trouble using the Apache Ignite 2.7.0 Linux built ODBC driver.
>
That's right. This IEP has been only implemented for C++ thin for now.
Best Regards,
Igor
On Fri, Apr 26, 2019 at 2:05 PM kcheng.mvp wrote:
> Hi Igor,
>
> I just checked the jiras and found this IPE has not been implemented for
> *java thin client* yet ?
>
>
>
>
>
t; I am still on the design phrase of go thin client. once it's ready I will
> share the link. thanks.
> Thanks,
> Ken Cheng
>
>
> On Thu, Apr 25, 2019 at 10:02 PM Igor Sapego wrote:
>
>> Hello,
>>
>> Are you developing a Go thin client? Can you share a link?
Hello,
Are you developing a Go thin client? Can you share a link?
There is already one go client I'm aware of [1], is yours related somehow?
As for your question, thin client is given list of IPs and ports by a user.
During the start,
or in background thin client tries to establish connection
That's really weird. There should not be so much connections. Normally thin
client will open one TCP connection per node at max. In many cases, there
going to be only one connection.
Do you create IgniteClient in your application once, or do you start them
several
times? Could it be that your
You are welcome.
Best Regards,
Igor
On Tue, Mar 19, 2019 at 5:15 PM wt wrote:
> Thanks Igor
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
That's because Ignite's ODBC driver does not support all possible
connection/statement attributes.
You can try enabling ODBC logging [1], then repeat your actions and
send resulted logs to us, so we can see what is the attribute SQL server
tries to set that Ignite does not support.
[1] -
Hi,
Here you go: [1]
If you need binary release:
1. Click [APACHE IGNITE NIGHTLY RELEASE] #2 :: Assemble Binaries
2. Choose any success release (latest at the top).
3. Click "Artifacts" tab.
4. Click on "apache-ignite-2.8.0.XXX-bin.zip" to download nightly binary
release.
You can also
Jack,
You can use pointer semantics [1] to differ nulls from zeroes. It won't
work for primitive types (as int), but it is a rare case, really, that your
value is a primitive type. And even if you want to use value, that only
contains single int it is simple enough to make a class-wrapper.
By the way, since Ignite 2.8 Ignite is going to support both OpenSSL 1.0
and 1.1
Best Regards,
Igor
On Thu, Mar 14, 2019 at 12:18 PM Ilya Kasnacheev
wrote:
> Hello!
>
> You can do 'sudo make uninstall' instead of deleting headers manually.
> Otherwise, cheers!
>
> Regards,
> --
> Ilya
Hi Jack,
Design document is mostly for developers, not for users. It shows current
state of the master branch, so not every feature listed there as supported
actually presents in any Ignite release. You can try naightly builds [1]
though,
if you want try some new features before they get into
Are you sure you don't have OpenSSL 1.1 installed?
Best Regards,
Igor
On Tue, Mar 12, 2019 at 7:18 PM jackluo923
wrote:
> What is the specific SSL library version dependency to successfully compile
> the cpp binaries under Ubuntu 16.04. This particular dependency isn't
> mentioned anywhere in
Also, note, that since Ignite 2.8 we are going to support OpenSSL 1.1 as
well as 1.0.
Best Regards,
Igor
On Wed, Mar 13, 2019 at 12:12 PM Ilya Kasnacheev
wrote:
> Hello!
>
> My recommendation is to uninstall openssl-dev (or openssl-devel) of 1.1.0
> and install that of 1.0.0.
>
> Then
It's fine,
I'm glad it helped you.
Best Regards,
Igor
On Tue, Feb 12, 2019 at 6:23 PM F.D. wrote:
> Yes Igor, you're right. It's a my fault.
>
> Thank you,
>F. D.
>
>
> Il giorno mar 12 feb 2019, 13:35 Igor Sapego ha
> scritto:
>
>> Hi,
>>
&g
Hi,
This exception may happen when you try to register the same callback
several times. It should not happen when you call GetCompute().
Best Regards,
Igor
On Tue, Feb 12, 2019 at 2:37 PM F.D. wrote:
> Hi igniters,
>
> I'm trying to port my code from 2.6 to 2.7. And now when I try to get a
>
eError::IGNITE_SUCCESS)
> ctx.Get()->DestroyJvm();
>
>factoryLock.Leave();
> }
>
> And call it before the FreeLibrary(), now when I call the start I got a
> unknow error. Any ideas?
>
> Thanks,
>F.D.
>
>
> On Mon, Jan 28, 2019 at 5:
Hi,
Currently, Ignite on start creates JVM instance internally, but
it never stops it. Also, it currently can not work with already started
JVM.
So when you start Ignite the first time, it loads JVM, when you stop
and unload it, the JVM remains loaded in process memory. When
you start Ignite
Hi,
BinaryObject in C++ is not the same thing as in Java right now.
Currently C++ client do not support "BinaryObject" construction
and access. You may now only operate on actual serializable
objects, for which BinaryObject class template has been specialized.
You may find details and examples
Great job!
Forwarding to devlist.
Are there Node.js guys that can take a look?
Best Regards,
Igor
On Tue, Jan 22, 2019 at 10:47 PM thavlik
wrote:
> https://github.com/thavlik/ignite/tree/master/modules/platforms/nodejs
>
> https://issues.apache.org/jira/browse/IGNITE-11032
>
> Please let me
Yes, thick client always sends requests to the "right" node that actually
contains data.
Best Regards,
Igor
On Mon, Jan 21, 2019 at 9:20 AM summasumma wrote:
> Thanks Igor.
>
> One more clarification:
>
> Does Ignite client perform sharding by itself by selecting the
> node/partition across
No you should not have the same configs, but you need to have the same
configuration of the protocol, which is different for Java and C++ by
default
(I believe, you use Java server).
You may find details here [1].
[1] -
https://apacheignite-cpp.readme.io/docs/cross-platform-interoperability
It should start in client mode. Make sure that the right configuration file
is used.
Best Regards,
Igor
On Thu, Jan 17, 2019 at 12:40 PM summasumma wrote:
> Thanks Igor.
>
> I am trying to do an example putandget operation using the Ignite-c++
> client
> code from the following link:
>
Hi,
1. Async is not yet supported in C++ clients.
2. Continuous queries supported by thick C++ client.
3. Works through SQL, so supported by thick client.
4. SQL supported by thick client, and also planned for C++ thin client.
Best Regards,
Igor
On Mon, Jan 14, 2019 at 10:53 AM summasumma
That's right, Ignite C++ do not support messaging currently.
Best Regards,
Igor
On Tue, Jan 8, 2019 at 3:07 AM SamsonLai wrote:
> I have an ignite cluster that running on Java, all nodes (Java) within the
> cluster can send and receive Ignite messages. Now, I have to create another
> client
Hello,
Note that in Ignite 2.7 only OpenSSL 1.0 is supported.
Now, for your issue. It's weird and I have never faced that one by myself,
but according to MSDN [1] you need to link to shell32.dll.
[1] -
https://docs.microsoft.com/en-us/windows/desktop/api/shellapi/nf-shellapi-shfileoperationa
You are right, this document needs update. I'll file
a ticket for this task.
Best Regards,
Igor
On Fri, Nov 30, 2018 at 5:53 AM Ray wrote:
> Thank you for the reply Igor,
>
> After adding legacy_stdio_definitions.lib in the linker's input, I built
> the
> ODBC driver successfully.
>
> I want
By the way, you do know that there is a pre-built binary installer
in Ignite binary release, right? Or do you want to build ODBC by
yourself for some reason?
Best Regards,
Igor
On Thu, Nov 29, 2018 at 12:50 PM Igor Sapego wrote:
> This is a known issue of broken backward compatibility of M
This is a known issue of broken backward compatibility of MSVC.
See [1] for details and solution.
[1] -
https://apacheignite-sql.readme.io/docs/odbc-driver#section-building-on-windows
Best Regards,
Igor
On Thu, Nov 29, 2018 at 9:22 AM Ray wrote:
> Hi Igor,
>
> Thanks for the reply.
> I
Do you shut down C++ node properly prior killing the process?
Does this exceptions impacts cluster's functionality anyhow?
Best Regards,
Igor
On Wed, Nov 28, 2018 at 8:53 AM wangsan wrote:
> As I restart cpp client many times concurrently ，may be zkcluster(ignite)
> has some node path has
Can you explain your case in more detail? I'm not quite
understand what the problem is.
Best Regards,
Igor
On Tue, Nov 27, 2018 at 1:27 PM wangsan wrote:
> When client （c++ node） restart mulit times,
> The server and other client will throw this excption
>
> ERROR
Or do you use one of the thin clients? Can you specify which one?
Best Regards,
Igor
On Thu, Nov 22, 2018 at 12:54 PM Igor Sapego wrote:
> Hi,
>
> Do you use ODBC driver for connection?
>
> Best Regards,
> Igor
>
>
> On Wed, Nov 21, 2018 at 9:45 PM daya airody wro
Hi,
Do you use ODBC driver for connection?
Best Regards,
Igor
On Wed, Nov 21, 2018 at 9:45 PM daya airody wrote:
> We deployed Ignite on AWS.We have a single node cluster to begin with. Our
> Application is connecting as client.
>
> When I access one of the endpoints of our application, it
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,
Can you share an ODBC log please?
Best Regards,
Igor
On Wed, Oct 24, 2018 at 5:59 PM wt wrote:
> Hi
>
> Thank you for fixing the bug where in Excel i was not able to see the
> tables. I can now however there are no columns visible and it gives an
> error
> that the data source did not
No, I've never seen this error before. Seems like
some issue in configuration of your OS.
Do you have pkg-config installed?
Best Regards,
Igor
On Wed, Oct 24, 2018 at 2:17 PM wt wrote:
> those errors are gone but it looks like some ubuntu issue is now a problem.
> Have you seen this before?
Try removing AM_PROG_AR as well. I will fix the issue in future.
Best Regards,
Igor
On Wed, Oct 24, 2018 at 1:41 PM wt wrote:
> Hi Igor
>
> *I tried as a standard user and i get this*
>
> ubuntu@ip-10-112-47-3:/ignite2.7/ignite/modules/platforms/cpp$ libtoolize
> && aclocal && autoheader &&
Hello,
2.7 is not released yet, but you can get code from git repository
from the ignite-2.7 branch. Note however that there are still some
issues/missing features in this branch. You can see the current
state of the release in the appropriate thread on the devlist.
[1] -
The issue is fixed and is in master already.
You can wait for Ignite 2.7 release or check that the issue is
resolved with nightly release [1]
[1] -
https://ci.ignite.apache.org/project.html?projectId=Releases_NightlyRelease
Best Regards,
Igor
On Tue, Oct 16, 2018 at 10:42 AM wt wrote:
>
It looks like an error. I filed a ticket [1]. I'll try to fit to to 2.7
[1] - https://issues.apache.org/jira/browse/IGNITE-9891
Best Regards,
Igor
On Mon, Oct 15, 2018 at 10:46 AM wt wrote:
> here is the log file generated when opening a new odbc connection to ignite
> in excel.
>
>
Can you please collect and share logs with us?
You can find instructions on how to enable ODBC
log for example here: [1]
[1] -
https://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=BGOD_logging_logwin
Best Regards,
Igor
On Wed, Oct 10, 2018 at 5:46 PM wt wrote:
> i would
Hi,
Did your thick .net client connected to the cluster?
It should be visible in server node's logs.
Best Regards,
Igor
On Wed, Sep 12, 2018 at 1:58 PM Som Som <2av10...@gmail.com> wrote:
> the cache names list is empty then i call the method of non thin client
> butmy TestCache is stil
Guys,
Personally, I do not see any problems, why we can not implement
Continuous Queries for thin clients. This will require a decent amount
of work, and will not give such strong guaranties as thick clients
give (for example, on server crash thin client will get an exception and
will need to
Nice to hear.
Please, keep us updated about what QLIK thinks about the issue.
Thank you in advance
Best Regards,
Igor
On Mon, Sep 10, 2018 at 10:50 PM limabean wrote:
> Thank you very much for the thorough discussion/explanation and pending fix
> for public schemas. Much appreciated !
>
>
ith ordinary double quotes set.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пн, 10 сент. 2018 г. в 14:28, Igor Sapego :
>
>> Ilya,
>>
>> If we won't bother with quotes, then many other tools will stop working,
>> as cache-names-schemas MUST be quote
that the result will be quoted.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пт, 7 сент. 2018 г. в 15:38, Igor Sapego :
>
>> Well, ODBC applies quotes to all schemas. It makes sense to
>> check and not apply quotes to PUBLIC, but this won't help in
>> all other cases, wh
e that we have quotes around PUBLIC since it's
> supposed to be used quote-free. I will take a look.
>
> Regards,
>
> --
> Ilya Kasnacheev
>
>
> пт, 7 сент. 2018 г. в 14:07, Igor Sapego :
>
>> It happens, because ODBC returns schema name in quotes,
>
It happens, because ODBC returns schema name in quotes,
so seems like QLIK adds its own quotes around it, as it encounters
non standard characters (quotes).
I think, it is a QLIK's error, as our ODBC driver explicitly states, that no
additional quotes should be used around identifiers. And even
Hi,
It's weird. How do you see that?
Best Regards,
Igor
On Tue, Sep 4, 2018 at 5:26 PM F.D. wrote:
> Hi Igniters,
>
> I've my client (C++) and I want to send my computations (distritubuted
> closures) on a server. I want to prevent my client from participating in
> the calculation.
>
> I've
Which exactly ODBC driver are you talking about?
Best Regards,
Igor
On Mon, Sep 3, 2018 at 4:48 PM wt wrote:
> not sure if it helps but the odbc driver doesnt play nice with date fields
> and deals with them in binary format
>
> class org.apache.ignite.binary.BinaryInvalidTypeException
>
>
GetHashCode() method is not used for hashing in Ignite C++ any
more, as well as hashCode() method in Java. You can still find it
in legacy code, but since Ignite 2.1 this method is not used and
you can safely remove it.
By default, hashing algorithm in Ignite is now operates on byte-array
which
Filed a ticket: [1]
[1] - https://issues.apache.org/jira/browse/IGNITE-9293
Best Regards,
Igor
On Thu, Aug 16, 2018 at 3:28 AM Denis Magda wrote:
> Igor,
>
> I think it's reasonable to add the baseline topology APIs to C++. Can you
> plan this for the nearest releases?
>
> Pave, do you have
This is OK, you may ignore this message.
Configure scripts, generated by autoconf are trying to delete
"core" files during their work, as they expect that some operations
can generate coredump files on crash, so it prints this error when
it faces "core" directory. More details here: [1].
The
1 - 100 of 325 matches
Mail list logo
