Yes, instead of utilizing custom comparators, just use "order by" clause in
your SQL query.
D.
On Thu, Nov 1, 2018 at 12:43 AM Mikael wrote:
> Hi!
>
> I don't think so but can't you use an index and an SQL query instead ?
>
> Mikael
>
> Den 2018-11-01 kl. 06:33, skrev Ignite Enthusiast:
>
> I
I also want to point out that Ignite has nightly builds, so you can try
them instead of doing your own build as well.
https://ignite.apache.org/download.cgi#nightly-builds
D.
On Thu, Aug 16, 2018 at 1:38 AM, Vladimir Ozerov
wrote:
> Hi,
>
> There were a lot of changes in the product since 2.3
I believe JDK9 is supported, but you need to add certain JVM parameters.
Vladimir, can you comment?
D.
On Fri, Aug 10, 2018, 07:31 KJQ wrote:
> As a note, I downgraded all of the Docker containers to use JDK 9 (9.0.4)
> and
> I still get the same problem running the SpringBoot 2 application.
Is it not possible to use TOAD with standard Ignite JDBC driver? I am not
sure if there should be any issues.
On Thu, Aug 2, 2018 at 9:42 AM, ApacheUser
wrote:
> Thanks Alex,
>
> We have large pool of developers who uses TOAD, just thought of making TOAD
> connect to Ignite to have similar
Thanks, Shamim. I will give it a read.
On Wed, Aug 1, 2018 at 12:26 AM, srecon wrote:
> Dear, Users.
> Yesterday the first portion of our new title The Apache Ignite Book had
> been published and available at https://leanpub.com/ignitebook . The full
> table of contents and the sample chapter
The Ignite 2.5 was released and can be downloaded from the Ignite website:
https://ignite.apache.org/download.html
D.
On Wed, May 30, 2018 at 6:34 AM, Stanislav Lukyanov
wrote:
> Most likely you've run into this bug:
> https://issues.apache.org/jira/browse/IGNITE-8210
>
> It was fixed in 2.5,
The Ignite 2.5 has been released and can be downloaded from the Ignite
website:
https://ignite.apache.org/download.html
D.
On Wed, May 30, 2018 at 6:33 AM, Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:
> Ray,
>
> Which Ignite version are you running on. You may be affected by [1] which
On Tue, Mar 27, 2018 at 10:53 PM, Deepesh Malviya
wrote:
I notice that affinity solution is still going to update millions of items
> but the updates are local instead of cluster-wide. Please let me know if my
> interpretation is wrong.
>
Yes.
> I see Ignite also support
Hi Fvyaba,
In order to avoid memory overhead per table, you should create all tables
as part of the same cache group:
https://apacheignite.readme.io/docs/cache-groups
D.
On Mon, Mar 26, 2018 at 7:26 AM, aealexsandrov
wrote:
> Hi Fvyaba,
>
> I investigated your
Hi,
Ignite is adding basic authentication capability for thin clients in the
upcoming 2.5 release - you will be able to provide user name and password
to connect to the cluster:
https://issues.apache.org/jira/browse/IGNITE-7436
You may already try it in the nightly builds:
Thanks, Denis. It should be added to the download page, I updated the
ticket.
On Sat, Mar 24, 2018 at 5:48 AM, Denis Magda <dma...@apache.org> wrote:
> Created a JIRA ticket for that:
> https://issues.apache.org/jira/browse/IGNITE-8040
>
> --
> Denis
>
> On Fri, Mar 2
Awesome! Finally instead of asking our users to build from the master, we
can provide a link to the nightly build instead.
Denis, can you please add these links to the website?
D.
On Thu, Mar 22, 2018 at 1:27 PM, Petr Ivanov wrote:
> It works, thanks!
>
>
> Here is
Why do we need to ask people to login to get a nightly build? Anyway to
open it to public without a login?
On Wed, Mar 21, 2018 at 10:45 PM, Dmitry Pavlov
wrote:
> Hi Raymond,
>
> You could sign up using valid email address. Please write to @dev list if
> link still is
On Thu, Mar 15, 2018 at 9:51 PM, StartCoding wrote:
> Hi Mike,
>
> Thanks for your quick response.
>
> I am afraid denormalizing will work for me because I have just given a
> simple example. There are 16 tables which in that case needs to be joined
> into single entity.
On Tue, Mar 20, 2018 at 2:09 PM, Vladimir Ozerov
wrote:
> Internally Ignite is key-value storage. It use key to derive partition it
> belongs to. By default the whole key is used. Alternatively you can use
> @AffinityKey annotation in cache API or "affinityKey" option in
The main advantage of Azul is support of large on-heap memory space without
garbage collection pauses. In case of Ignite, the primary storage is
off-heap, so garbage collection should not be an issue regardless.
However, if you still need to use Azul JVM, I would give it a shot. The
only
Hi Lawernce,
I believe Alexey Goncharuk was working on improving this scenario. Alexey,
can you provide some of your findings here?
D.
-- Forwarded message --
From: lawrencefinn
Date: Mon, Mar 5, 2018 at 1:54 PM
Subject: Re: Large durable caches
To:
Hi Steve,
The integration with Tableau was tested and verified:
https://apacheignite-sql.readme.io/docs/tableau
D.
On Mon, Mar 5, 2018 at 12:48 AM, steve.hostettler <
steve.hostett...@gmail.com> wrote:
> Hello,
>
> is there any best practice/recommendation on how to connect 3rd business
>
I also think that switching to LOG_ONLY mode should be good enough.
On Mon, Feb 26, 2018 at 6:58 AM, dmitriy.govorukhin <
dmitriy.govoruk...@gmail.com> wrote:
> Hi,
>
> I guess the problem in "setSwapPath(...)", it is not the path for
> persistence.
>
> Try to do something like this:
>
>
To my knowledge, the 2.4 release should have support for both persistence
mechanisms, native and 3rd party, working together. The release is out for
a vote already:
http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-2-4-0-RC1-td27687.html
D.
On Mon, Feb 26, 2018 at 2:43 AM,
Paolo, the release is out for a vote:
http://apache-ignite-developers.2346864.n4.nabble.
com/VOTE-Apache-Ignite-2-4-0-RC1-td27687.html
D.
On Tue, Feb 20, 2018 at 11:55 AM, Paolo Di Tommaso <
paolo.ditomm...@gmail.com> wrote:
> Hi folks,
>
> I was wondering what's the status of Ignite 2.4. Is
Hi Sergey,
The 2.4 release is about to be voted for. You can use the RC1 in the mean
time:
http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-2-4-0-RC1-td27687.html
D.
On Mon, Feb 19, 2018 at 6:43 AM, Mikhail
wrote:
> Hi Sergey,
>
> The
Hi Rajesh,
Please allow the community some time to test your code.
As far as testing single node vs. distributed, when you have more than one
node, Ignite will split your data set evenly across multiple nodes. This
means that when running the query, it will be executed on each node on
smaller
On Fri, Feb 2, 2018 at 2:59 PM, Luqman Ahmad wrote:
> Please subscribe me.
>
If your message has been delivered to the user@ list, you must be already
subscribed.
D.
Rajesh, can you please show your query here together with execution plan?
D.
On Thu, Feb 1, 2018 at 8:36 AM, Rajesh Kishore
wrote:
> Hi Andrey
> Thanks for your response.
> I am using native ignite persistence, saving data locally and as of now I
> don't have
Great to see such a busy schedule!
Ignite community is unstoppable :)
D.
On Thu, Feb 1, 2018 at 3:19 PM, Tom Diederich
wrote:
> Igniters,
>
> The following is a list of upcoming events in February. To view this list
> from the Ignite events page, click here
>
Hi Michael, were you able to apply the suggestions. It would be nice if you
would share your results with the community.
D.
On Mon, Jan 8, 2018 at 6:42 PM, Michael Jay <841519...@qq.com> wrote:
> Thank you, Alexey. I'll try you advice and let you know the result later.
> Thanks again.
>
>
>
>
Hi,
Were you able to resolve the issue? If yes, it would be nice to share it
with the community.
D.
On Thu, Dec 21, 2017 at 12:49 AM, dkarachentsev
wrote:
> Hi Indranil,
>
> These measurements are not fully correct, for example select count(*) might
> use only
Hi Tejas,
Were you able to resolve your issue? If yes, it would be nice to share it
with the community.
D.
On Wed, Dec 20, 2017 at 11:09 PM, Denis Magda wrote:
> Why are you giving only 5GB of RAM to every node then (referring to your
> data region configuration)? You
Cross-sending to dev@.
Alexey,
This issue is marked to be fixed for 2.4 which is planned to be released in
a couple of weeks. Do you think you will be able to close this issue before
the release?
D.
On Mon, Dec 18, 2017 at 9:51 AM, Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:
>
Hi Kamil,
Have you been able to resolve your issue? If yes, it would be great if you
could share it with the community.
Thanks,
D.
-- Forwarded message --
From: mcherkasov
Date: Mon, Dec 18, 2017 at 9:27 AM
Subject: Re: How to speedup activation on a
Hi,
Is there a reason why you do not want to use the C++ client that comes with
Ignite?
https://apacheignite-cpp.readme.io/docs/transactions
D.
On Mon, Jan 8, 2018 at 2:12 AM, kotamrajuyashasvi <
kotamrajuyasha...@gmail.com> wrote:
> Hi
>
> I would like to perform Ignite Transaction
Hi Naveen,
Affinity mapping is a critical portion of Ignite data distribution and
cannot be changed. For more information, please refer to this
documentation: https://apacheignite.readme.io/docs/affinity-collocation
D.
On Wed, Dec 6, 2017 at 9:20 PM, Naveen wrote:
>
Naresh, several questions:
1. How are you accessing data, with SQL or key-value APIs?
2. Are you accessing data locally on the server or remotely from a
client? If remotely, then you might want to enable near caching.
D.
On Thu, Nov 9, 2017 at 3:01 PM, naresh.goty
Hi Michael, do you have any update for the issue?
On Thu, Nov 2, 2017 at 5:14 PM, Michael Cherkasov <
michael.cherka...@gmail.com> wrote:
> Hi Tobias,
>
> Thank you for explaining how to reproduce it, I'll try your instruction. I
> spend several days trying to reproduce the issue,
> but I
Denis,
We should definitely print out a thorough warning if HashMap is passed into
a bulk method (instead of SortedMap). However, we should make sure that we
only print that warning once and not ever time the API is called.
Can you please file a ticket for 2.4?
D.
On Thu, Oct 26, 2017 at 11:05
KR, any chance you can provide a reproducer? It would really help us
properly debug your issue. If not, can we get a copy of your configuration?
On Thu, Oct 12, 2017 at 10:31 AM, KR Kumar wrote:
> Hi AG,
>
> Thanks for responding to the thread. I have tried with 2.3 and
Hi Dop,
I am not sure Apache Ignite community will be able to provide support
beyond what you see on the user@ and dev@ lists today. If you need
something beyond that, I would advise you to contact commercial vendors,
like GridGain.
D.
On Tue, Oct 3, 2017 at 6:58 AM, Dop Sun
On Tue, Oct 3, 2017 at 4:19 AM, Ray wrote:
> Hi Alexey
>
> My cache configuration is as follows.
> cacheConfig.setName("DailyAggData")
> cacheConfig.setIndexedTypes(classOf[A], classOf[B])
> cacheConfig.setSqlSchema("PUBLIC")
> aggredCacheConfig.setBackups(2)
>
To add to Andrey's example, here is how you would use IgniteAtomicSequence
to make IDs unique across the whole distributed cluster:
*public static class CustomSQLFunctions {*
*@QuerySqlFunction*
*public static long nextId(String seqName, long initVal) {*
*return
On Mon, Sep 18, 2017 at 8:01 AM, rick_tem wrote:
> I see that as a huge problem. Certainly one of the functions of Ignite is
> to
> be faster than the database, but if it fails to meet all of the
> requirements
> of what a database will do for you, what is the point of
Lucky,
We would like to see the output of the "EXPLAIN" command for the query that
takes a long time, so we could make suggestions. Can you post it here?
D.
On Fri, Sep 15, 2017 at 11:50 PM, Lucky wrote:
> Hi , Yakov Zhdanov
> Actually I did not run H2 console, I run
On Thu, Sep 14, 2017 at 10:02 PM, iostream wrote:
> I have used Informix DB before. In Informix string comparisons such as -
>
> SELECT * from Person where fName = "ABC";
>
> return rows even if the column value has trailing spaces. The Informix
> engine internally trims
On Thu, Sep 14, 2017 at 7:10 PM, iostream wrote:
>
> 1. Whether Ignite does not TRIM strings internally when doing comparisons?
>
I don't think Ignite trims strings for comparison. You should use TRIM()
function explicitly when inserting or comparing strings.
> 2. Is
Hi Chaitanya,
Sorry to see you go :(
Please follow the unsubscribe link here:
https://ignite.apache.org/community/resources.html#mail-lists
D.
On Wed, Sep 13, 2017 at 2:26 PM, chaitanya kulkarni <9...@gmail.com>
wrote:
> Unsubscribe
>
On Mon, Sep 11, 2017 at 6:54 PM, aa...@tophold.com
wrote:
> Thanks Alexey! what we real want, we deploy service on each Cache Node.
> those service will use data from its' local cache.
>
> Client will call those remote service, Client should only call the
> service on
Great!
I think the next task should be to explain expiration vs eviction. I am
seeing too many questions on it as well. At this point, I am also confused
about how it really works.
D.
On Fri, Sep 8, 2017 at 10:18 AM, Denis Magda wrote:
> Unbelievable! So many years went by
Cross-sending to user@ as well.
On Tue, Sep 5, 2017 at 10:44 PM, kotamrajuyashasvi <
kotamrajuyasha...@gmail.com> wrote:
> Hi
>
> I'm using ignite with cassandra as persistent store. I have a POJO class
> mapped to cassandra table. I have used
> ignite-cassandra-store/KeyValuePersistenceSettings
On Tue, Sep 5, 2017 at 10:51 AM, mcherkasov wrote:
> I think javadoc is the best source for this:
>
> /**
> * Flag indicating that Ignite should wait for write or commit replies
> from all nodes.
> * This behavior guarantees that whenever any of the atomic or
not support it out of the box, but you may wish to look at the
3rd party solutions, e.g. the one provided by GridGain -
https://docs.gridgain.com/docs/data-snapshots
>
>
> *From:* Dmitriy Setrakyan [mailto:dsetrak...@apache.org]
> *Sent:* Tuesday, September 5, 2017 3:09 PM
>
ion you witnessed.
All enterprise users explicitly specify which network address to bind to,
just like you did. This helps avoid any kind of magic in production.
>
>
> Thanks,
> Raymond.
>
>
>
> *From:* Dmitriy Setrakyan [mailto:dsetrak...@apache.org]
> *Sent:* Tuesd
unlike above?
>
Yes, exactly. My suggestions will ensure that you explicitly bind to the
same address every time.
>
> Thanks,
>
> Raymond.
>
>
>
> *From:* Dmitriy Setrakyan [mailto:dsetrak...@apache.org]
> *Sent:* Tuesday, September 5, 2017 11:17 AM
> *To:* us
On Mon, Sep 4, 2017 at 3:37 PM, Raymond Wilson
wrote:
> Hi,
>
>
>
> I definitely have not had more than one server node running at the same
> time (though there have been more than one client node running on the same
> machine).
>
>
>
> I suspect what is happening is
Hi Raymond,
Sorry for the initial confusion. The consistent ID is the combination of
the local IP and port. You DO NOT need to do anything special to configure
it.
If you had different folders created under the work folder, you probably
had more than one node running at the same time. Can you
On Mon, Aug 28, 2017 at 5:23 AM, agura wrote:
When persistence store is enabled the data pages that can't be stored in
> the memory will be evicted to the persistence store.
Andrey, this is not how Ignite persistence works.
When the persistence is enabled, all the data will
James,
I think you will find this documentation useful:
https://apacheignite.readme.io/docs/getting-started
D.
On Sun, Sep 3, 2017 at 8:32 PM, James <2305958...@qq.com> wrote:
> First, I really appreciate a help from Dmitriy.
>
> My company assigns me to work on a big product using Ignite.
eed add new getAll method on API, otherwise best alternative is
> use custom ComputeJob or affinityCall.
>
> Thanks,
> Semyon
>
> On Tue, Aug 29, 2017 at 7:20 AM, Dmitriy Setrakyan <dsetrak...@apache.org>
> wrote:
>
>> Andrey,
>>
>> I am not sure I
Denis, I think you provided an incorrect link to the ticket. Here is the
correct link:
https://issues.apache.org/jira/browse/IGNITE-3478
D.
On Wed, Aug 30, 2017 at 5:50 PM, Denis Magda wrote:
> Hi,
>
> The docs are still valid - SQL operations are not fully transactional
Cross sending to dev@
Igniters, up until version 1.9, the nested fields were supported by
flattening the names. Do we still support it? I cannot seem to find
documentation for it.
D.
On Thu, Aug 31, 2017 at 7:12 AM, takumi wrote:
> This is a part of the real code
On Sat, Sep 2, 2017 at 5:11 AM, userx wrote:
> Hi all,
>
> Regarding question 2, let me put it this way.
>
> Like ignite has eviction policy for RAM described at
> https://apacheignite.readme.io/docs/evictions
> Is there an eviction policy for a persistent store ? Say for a
On Sun, Sep 3, 2017 at 12:35 AM, dkarachentsev
wrote:
> Hi,
>
> Just to clarify my words a bit. When persistence is enabled, all memory
> data
> are stored on disk with all durability guarantees. But it is also allows
> you
> to store in cache more data than you can
Hi James,
My answers are inline...
On Sun, Sep 3, 2017 at 3:41 AM, James <2305958...@qq.com> wrote:
> I am searching one solution to my case. I just found Apache Ignite
> Yesterday. It appears a good solution. But I am not sure. I need your
> suggestions.
>
> My data is stored in MySQL. It is
On Tue, Aug 29, 2017 at 7:00 PM, userx wrote:
> Hi All,
>
> 1) Like the conventional configuration of
> https://apacheignite.readme.io/docs/memory-configuration#
> section-memory-policies
> where in we could limit the size of the memory, how do we define a
> configuration
On Fri, Sep 1, 2017 at 1:41 PM, Denis Mekhanikov
wrote:
> Regarding your second question: looks like you don't actually need
> persistence. Its purpose is the opposite: to save cache data between
> restarts.
> If you use persistence to store more data than RAM available,
; bunch of nulls in the result map as I expect most of the keys to be
> rejected by the filter.
>
> Overall, invokeAll() is not what one would call *efficient* (the key word
> in my original question) way of filtering.
>
> Thanks!
> Andrey
>
> --
>
Andrey,
Good to hear from you. Long time no talk.
I don't think invokeAll has only update semantics. You can definitely use
it just to look at the keys and return a result. Also, as you mentioned,
Ignite compute is a viable option as well.
The reason that predicates were removed from the get
Love the idea. Let's add Testing Ignite Apps page on Readme. Denis, I don't
think we need many snippets, just a few.
As far as Maven archetype, Yakov, is the only purpose of it to load a
project, so users can add tests to it?
D.
On Fri, Aug 25, 2017 at 8:51 AM, Denis Magda
On Sat, Aug 5, 2017 at 10:17 PM, iostream wrote:
> Suppose I have 10 Person entries in the disk, out of which only 5 are
> in-memory. Now if I run a SQL query which is expected to count the number
> of
> entries in Person cache, will the query run only on the disk or RAM
Thanks, Turik, very interesting!
On Mon, Aug 7, 2017 at 8:58 PM, techbysample wrote:
> Igniters,
>
> Check out the new GA Grid(Beta) project here:
>
> https://github.com/techbysample/gagrid
>
> GA Grid (Beta) is a distributive in memory Genetic Algorithm (GA) component
> for
On Fri, Aug 4, 2017 at 11:54 AM, kotamrajuyashasvi <
kotamrajuyasha...@gmail.com> wrote:
> Hi
>
> Thanks for the response. When I put cacheKeyConfiguration in ignite
> configuration, the affinity was working. But when I call Cache.Get() in
> client program I'm getting the following error.
>
>
Chris,
After looking at your code, the only slow down that may have occurred
between 1.9 and 2.0 is the actual cache "get(...)" operation. As you may
already know, Ignite 2.0 has moved data off-heap completely, so we do not
cache data in the deserialized form any more, by default. However, you
It is not clear to me what this issue is. Ranjit, can you explain what this
is critical to you?
On Tue, May 9, 2017 at 9:55 AM, Ranjit Sahu wrote:
> When will that be ?
>
> On Tue, 9 May 2017 at 10:10 PM, Andrey Gura wrote:
>
>> No, it isn't fixed yet.
Cédric,
Can you clarify why not create 1 continuous query and listen to all the
changes for all the keys?
D.
On Thu, Apr 13, 2017 at 8:00 AM, ctranxuan
wrote:
> Well, actually we were interesting in having continuous queries listening
> multi-tenant caches.
>
>
This question has already been answered here:
http://stackoverflow.com/questions/43551422/javaspaces-like-patterns-in-ignite/
D.
On Fri, Apr 21, 2017 at 2:11 PM, Sean Winship
wrote:
> I've used GigaSpaces in the past and I'd like to know if I can use Ignite
> in a
On Wed, Apr 19, 2017 at 10:16 PM, woo charles
wrote:
> When I call addData() in streamer. this data will send & buffer in server
> node. is that correct?
> If I correct, this data will buffer in random server node or only the one
> it directly connected?
>
addData()
On Wed, Feb 8, 2017 at 4:57 PM, Denis Magda wrote:
> Cross-posting to the dev list.
>
> Igniters, what if we make “storeKeepBinary” = true by default in Ignite
> 2.0? Presently, the user has to tweak the configuration manually.
>
>
Makes sense to me.
Hi Massayuki,
Ignite itself does not have a concept of a NameNode. It goes directly to
the cluster node responsible for storing the data based on a key's hashcode.
The only time when a NameNode would come into a play, is when Hadoop HDFS
is configured as an underlying write-through file system.
Thanks Denis!
Lea, I just want to clarify that if you manually pick Denis' commit, it
will likely fix your issue, but it will not be an official Ignite release
and will not have undergone the regular testing and QA cycle that all
Ignite releases generally go through.
D.
On Tue, Mar 28, 2017 at
If you use the same (or default) configuration for the affinity, then the
same key in different caches will always end up on the same node. This is
guaranteed.
D.
On Thu, Feb 23, 2017 at 8:09 AM, Andrey Mashenkov <
andrey.mashen...@gmail.com> wrote:
> Val,
>
> Yes, with same affinity function
+ user list
On Tue, Dec 20, 2016 at 12:30 PM, hemanta wrote:
> Hi,
>
> I am starting Ignite as standalone program embedded in my java application
> via Spring configuration. It works great however my application stucks and
> never finishes. I have added some shutdown
Val, do we have this documented?
> On Aug 11, 2016, at 10:18 AM, vkulichenko
> wrote:
>
> Ravi,
>
> You have to use the same version of ignite-hibernate as the ignite-core (the
> latest is 1.7). The ignite-hibernate module is not deployed to Maven central
>
ith completely clear
Ignite configuration in github and a proper description on it. I really
miss the benchmark results personally, they added a lot of clarity about
how to run and configure the project for performance.
>
> Ralph
>
> On Jul 21, 2016, at 12:55 PM, Dmitriy Setrakyan <dsetra
I am not a C++ expert, but can you please explain why you would like to
change all methods on the BinaryType to static? Is it the same way in Java?
On Fri, Jul 22, 2016 at 9:00 AM, Igor Sapego wrote:
> Hello Igniters and Ignite users,
>
> As there is going to be Ignite 2.0
On Mon, Jul 18, 2016 at 10:44 PM, Sergi Vladykin
wrote:
> Subquery in FROM clause should work with distributed joins enabled.
> Subquery expressions (in SELECT, WHERE, etc...) must always be collocated.
>
Thanks, Sergi! This definitely helps. Is it going to be possible
Hello Igniters,
ApacheCon Europe is coming November, 2016. I just submitted 3 talks on
Apache Ignite:
- Apache Ignite - Path to Converged Data Platform
- Shared Memory Layer and Faster SQL for Spark Applications
- Apache Ignite - JCache and Beyond
If you are a user or a developer of Apache
I highly doubt these marshallers will be more compact than Ignite binary
marshaller. Have you tested it?
On Thu, Jul 14, 2016 at 4:01 PM, Lin wrote:
> Hi all,
>
> I would like to find a more compacted marshaller to save the network
> bandwidth in Ignite clusters.
> From the
We are currently working on adding insert/update/delete commands to Ignite.
Here is the ticket you can follow:
https://issues.apache.org/jira/browse/IGNITE-2294
Thanks,
D.
On Thu, Jul 14, 2016 at 6:58 AM, Denis Magda wrote:
> Hi,
>
> Please properly subscribe to the
On Wed, Jul 13, 2016 at 11:23 AM, tracel wrote:
> thanks dsetrakyan,
>
> Why use System.out.println()?
>
I want to make sure that there is no overhead associated with log.info().
Can you check?
> I have added the System.out.println(), and keep the log.info() just
Can you replace log.info() with System.out.println() in your test?
On Wed, Jul 13, 2016 at 10:21 AM, tracel wrote:
> I have an Ignite (1.5.0.final) cache client node started in a Tomcat
> 8.0.32,
> the client node connects to a server node started on the same machine.
Just checked it out, looks awesome! Very nice and easy way to configure,
manage, and query Ignite clusters.
On Tue, Jun 28, 2016 at 1:41 AM, Alexey Kuznetsov
wrote:
> Igniters!
>
> I'd like to announce that we just pushed Ignite Web Console Beta 2 to
> master branch and
sly, one needs DNS
> integration which happens to be a best-practice anyway.
>
> Pires
>
> On Thu, Apr 28, 2016 at 4:45 PM Dmitriy Setrakyan <dsetrak...@apache.org>
> wrote:
>
>> Ignite does not have any specific Kubernetes integration, however, if it
>> supports TCP/
lexander.boud...@gmail.com> wrote:
>> I don't need access to TC console, I need to have my pull requests tested.
>> Take care,
>> Alexandre "Sasha" Boudnik
>>
>> call me via Google Voice:
>> 1(405) BUDNIKA
>> 1(405) 283-6452
>>
>>
I just realized that I don’t have a link either. Anton, do you mind adding
the link to TC to the community dropdown on the website?
On Mon, Jun 27, 2016 at 10:28 AM, Alexandre Boudnik <
alexander.boud...@gmail.com> wrote:
> Hello,
>
> In order to use Ignite's TeamCity, could you provide myself
On Thu, Jun 23, 2016 at 10:39 PM, Denis Magda wrote:
> Hi Binti,
>
> Probably the issue is related to the fact that you’re working with the
> cache inside of CacheStore.writeAll method. Have you tried to use
> PESSIMISTIC/REPEATABLE_READ mode? Is the situation the same?
It's a known issue: apache site puts links to a nearest site for user (I
>>> suppose it based on IP address) and does it incorrect.
>>>
>>> On Mon, Jun 20, 2016 at 8:37 AM, Dmitriy Setrakyan <
>>> dsetrak...@apache.org>
>>> wrote:
>>>
>&g
Worked for me just now. Can you try again?
On Sun, Jun 19, 2016 at 2:59 AM, Christos Erotocritou wrote:
> Hey guys,
>
> The links on the website seem to be broken, can someone check this?
>
> https://ignite.apache.org/download.html#binaries <
>
Great news, Christos!
Unfortunately I don’t know many people in London, otherwise would
definitely pass the word.
D.
On Fri, Jun 17, 2016 at 7:03 AM, Christos Erotocritou wrote:
> Hello Igniters!
>
> We’re excited to launch the official Apache Ignite London meetup -
>
Please send an email to user-subscr...@ignite.apache.org and follow easy
steps in the reply.
On Mon, May 23, 2016 at 7:07 AM, Ponnuraman, Agneeswaran <
agneeswaran.ponnuraman...@nielsen.com> wrote:
>
>
Compute grid jobs will execute more than once if the server crashed in the
middle of execution. In that case, the job will be failed over and started
from scratch.
If you want exactly once guarantee, then assign IDs to your computations or
events and store them in a cache. This way, if the event
Murthy, would setting a simple TTL for entries work for you?
Here is more info:
https://apacheignite.readme.io/docs/expiry-policies
D.
On Fri, May 13, 2016 at 2:03 PM, Murthy Kakarlamudi
wrote:
> Hi,
>What are my options to refresh ignite cache from underlying persistent
1 - 100 of 187 matches
Mail list logo