[ANNOUNCE] Apache Ignite 3.0.0-alpha4 is released!

Igniters, I'm happy to announce that the 4th alpha version of Ignite 3 is out! On top of the functionality that was previously released, Alpha 4 adds the following major features: - Object mappings for table views - DDL - Transactional API and protocol Code examples have been added

[ANNOUNCE] Apache Ignite 3.0.0-alpha3 is released!

Igniters, I'm happy to announce that the third alpha version of Ignite 3 is out! On top of the functionality that was previously released, Alpha 3 adds the following major features: - New SQL engine based on Apache Calcite with implemented JDBC driver. - Persistence implementation based

[ANNOUNCE] Apache Ignite 3.0.0-alpha2 is released!

Igniters, I'm happy to announce that Ignite 3 project reached a significant milestone, as we release the 2nd alpha version of the product. On top of the functionality that was previously released, Alpha 2 adds the following major features: - Replication infrastructure based on Raft. - New

Re: Looking for feedback on the Ignite 3.0.0 Alpha

rt/getting-started-guide >>> >>> On Wed, Jan 13, 2021 at 1:29 PM Stephen Darlington < >>> stephen.darling...@gridgain.com> wrote: >>> >>>> What is the link to the Getting Started Guide? >>>> >>>> On 13 Jan 2021, at 03:55, Vale

Re: Looking for feedback on the Ignite 3.0.0 Alpha

wrote: > When will the stable version of 3.0 get released? thanks. > > Valentin Kulichenko wrote: > > I'm excited to announce that the first alpha build of the Ignite 3 is > > out and available for download! > > > > Ignite 3 is the new project that was initiated by t

Re: Looking for feedback on the Ignite 3.0.0 Alpha

The meetup has been scheduled, please RSVP here: https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/275722317/ -Val On Wed, Jan 13, 2021 at 11:21 AM Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Link to the Getting Started Guide: > https://ignite.apache.or

Re: Looking for feedback on the Ignite 3.0.0 Alpha

Link to the Getting Started Guide: https://ignite.apache.org/docs/3.0.0-alpha/quick-start/getting-started-guide -Val On Tue, Jan 12, 2021 at 7:55 PM Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Igniters, > > I'm excited to announce that the first alpha build

Looking for feedback on the Ignite 3.0.0 Alpha

Igniters, I'm excited to announce that the first alpha build of the Ignite 3 is out and available for download! Ignite 3 is the new project that was initiated by the Ignite community last year. Please refer to this page if you want to learn more:

[ANNOUNCE] Apache Ignite 3.0.0-alpha1 Released

[1] https://ignite.apache.org [2] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+3.0 Regards, Valentin Kulichenko Apache Ignite PMC

Re: Ignite in-memory + other SQL store without fully loading all data into Ignite

Hi Courtney, Thanks for your feedback! To cut the story short, Ignite implements page memory architecture. All data is split into fixed-sized pages and any page can reside either both in memory and on disk or on disk only. Since the in-memory layer and persistence layer are natively integrated -

Live coding session next week

Igniters, On Tuesday next week (Nov 17), Denis Magda and I will conduct a live coding session, where we will implement a primitive Ignite-like distributed database from scratch. We will demonstrate major components required for such a system, show how they interact with each other and how they

Re: [DISCUSSION] Renaming Ignite's product category

My vote is for the "distributed memory-first database". It clearly states that Ignite is a database (which is true at this point), while still emphasizing the in-memory computing power endorsed by the platform. The "in-memory computing platform" is an ambiguous term and doesn't really reflect

Ignite 3.0 meetups

Igniters, As was discussed before, we've scheduled two meetups devoted to Ignite 3.0: - Sep 15 (in English): https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/272675408/ - Sep 17 (in Russian): https://www.meetup.com/Moscow-Apache-Ignite-Meetup/events/272675398/ I will

Webinar: Key Deployment Strategies for Database Acceleration

Igniters, This Wednesday at 10am Pacific Time, I will be conducting a webinar devoted to different deployment strategies that can be used with Apache Ignite. I will talk about how Ignite can be used as a cache, as a data grid, how it can be integrated with databases and other data sources, etc.

Virtual Ignite meetup tomorrow!

Fellow Igniters, I know many of you have to stay at home these days. I have good news for you: this doesn't mean that you can't attend Ignite meetups, as we're switching to a virtual format. The virus is not going to stop us :) Tomorrow I will be talking about some of the behind-the-scenes

Re: Ignite Thin Client Continuous Query

Igor, I just think that we're dealing with a trade off here, and that if we implement CQ for thin client, we will either end with a client that is not "thin" anymore, or semantics and guarantees of CQ would change so drastically that it would be a completely different feature. Either way, it's a

Re: IndexingSpi#remove not called on key migration

Zbyszek, I don't there is an issue. You start two nodes with one backup, therefore eviction never happens. You basically have a fully replicated dataset at this point. Try to start a third node, you should start getting remove() callbacks then. Indexes on backups are needed for failover. If

Re: Get TTL of the specific (K,V) entry

Cross-posting to dev. Igniters, This actually makes sense to me. Why don't we add IgniteCache#ttl(K key) method that would return current TTL for the key? Looks like this is already provided by GridCacheMapEntry#ttl() method, so we only need to properly expose it to public API. Am I right? If

Re: Spark data frames integration merged

Revin, I doubt IgniteRDD#getPrefferredLocations has any affect on data frames, but this is an interesting point. Nikolay, as a developer of this functionality, can you please comment on this? -Val On Wed, Jan 3, 2018 at 1:22 PM, Revin Chalil wrote: > Thanks Val for the

Re: BinaryObjectImpl.deserializeValue with specific ClassLoader

Ticket is still open. Vladimir, looks like it's assigned to you. Do you have any plans to work on it? https://issues.apache.org/jira/browse/IGNITE-5038 -Val On Wed, Jan 3, 2018 at 1:26 PM, Abeneazer Chafamo wrote: > Is there any update on the suggested

Spark data frames integration merged

Igniters, Great news! We completed and merged first part of integration with Spark data frames [1]. It contains implementation of Spark data source which allows to use DataFrame API to query Ignite data, as well as join it with other data frames originated from different sources. Next planned

Re: Affinity key for specific node

Mikael, You can also use a replicated cache then. This will give you both: all data available on service node as well as failover in case of failure (you will not lose any data as long as there is at least one node available). -Val On Tue, Dec 5, 2017 at 11:35 PM, Mikael

Re: Caused by: class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to find SQL table for type: UserAppInfo

You did not set CacheConfiguration#indexedTypes property. See documentation for more details: https://apacheignite.readme.io/docs/cache-queries#query-configuration-by-annotations -Val On Sat, Dec 2, 2017 at 12:24 AM, kcheng.mvp wrote: > by the way, here is my maven

Re: Deserialization error with Ignite 2.3.0

Andrey, This ticket seems to be about the same issue: https://issues.apache.org/jira/browse/IGNITE-6944 Can you please take a look and provide your thoughts? -Val On Tue, Nov 7, 2017 at 4:02 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > *cross-posting to dev* >

Re: Deserialization error with Ignite 2.3.0

*cross-posting to dev* Hi Chris, This is a regression due to this fix: https://issues.apache.org/jira/browse/IGNITE-6485. For some reason, since 2.3 it is looking for readResolve/writeReplace methods only in exact class that is being serialized, but not in the whole hierarchy. *Andrey G*, since

Re: Ignite 2.0.0 GridUnsafe unmonitor

I like the idea to print out a warning if unsorted map is provided. The fact that there are tons of other ways to get a deadlock doesn't mean that we should ignore this case which is actually very common. -Val On Tue, Oct 31, 2017 at 12:34 PM, Dmitry Pavlov wrote: >

Re: Ignite Events Remote Filter

Alexey, Yes, seems to be the case. Unsubscription happens if *local listener* returns false not remote filter. -Val On Fri, Oct 27, 2017 at 3:12 AM, Alexey Kukushkin wrote: > Also, I ran our CacheEventsExample and I confirm the remote filter is NOT > unsubscribed

Re: Conflicting cross-version suffixes in: org.scalatest:scalatest, com.twitter:chill, org.apache.spark:spark-unsafe, org.apache.spark:spark-tags

+dev list Igniters, I'm looking at this and it seems to be a bug. We have this dependency in spark-2.10 module POM: org.json4s json4s-core_2.11 3.5.0 Would replacing it with json4s-core_2.10 be enough to fix? -Val On Thu, Oct 5, 2017 at 5:16 PM, manuelmourato

Re: Failure to deserialize simple model object

Guys, Does anyone has ideas? -Val On Mon, Aug 14, 2017 at 4:33 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Cross-posting to dev > > Folks, > > I'm confused by the issue discussed in this thread. > > Here is the scenario: > - Start server nod

Re: Failure to deserialize simple model object

Cross-posting to dev Folks, I'm confused by the issue discussed in this thread. Here is the scenario: - Start server node with a cache with POJO store configured. There is one type declared, read-through enabled. - Start client node and execute get() for a key that exists in underlying DB. -

Webinar: Building Consistent and Highly Available Distributed Systems with Apache Ignite

Igniters, This Wednesday (August 2nd at 11am PT), I will host a webinar where I will go through different Apache Ignite features and capabilities that allow to build consistent and highly available distributed systems. More information here:

Re: Failed to wait for initial partition map exchange

Usually it's caused by GC or network issues. First, I would recommend to check if you're not running out of memory, and then collect and investigate GC logs: https://apacheignite.readme.io/docs/jvm-and-system-tuning#debugging-memory-usage-issues-and-gc-pauses -Val On Tue, Apr 18, 2017 at 2:10

Re: [GridCachePartitionExchangeManager] Pending transaction deadlock detection futures

cross-posting to dev list. Guys, Does anyone have an idea why client mode in Visor affects behavior? I thought we already forced client mode there, no? Alexey, you should know the answer. Can you please take a look at this thread? -Val On Tue, Mar 28, 2017 at 7:02 AM, ght230

Re: Can I let Ignite to do rebalance at a particular time?

Cross-posting to dev. Guys, Is there any reason for such implementation? Does it ever makes sense to trigger rebalancing on only one node? I think rebalance() method should broadcast automatically and do the job on all nodes. Just in case, we can also add localRebalance() method. This will be

Re: Same Affinity For Same Key On All Caches

Adding back the dev list. Folks, Are there any opinions on the problem discussed here? Do we really need FairAffinityFunction if it can't guarantee cross-cache collocation? -Val On Thu, Mar 2, 2017 at 2:41 PM, vkulichenko wrote: > Hi Alex, > > I see your point.

Re: Binary objects and cache store

+1 -Val 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. > > — > Denis > > On Feb 7, 2017, at

Re: Ignite Shutdown Hook

Hi, I'm not sure I understand the problem... Where is the application stuck? Did you look at thread dump? -Val 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

Re: NullPointerException on ScanQuery

Hi Andrey, Do you have an idea what is causing the NPE in the first place? What is null? I didn't quite get it from the thread. -Val On Tue, Dec 20, 2016 at 2:14 AM, Andrey Gura wrote: > Hi, > > As I wrote already I don't see any race for stable topology. Problems > are

Re: Memory Overhead per entry in Apache Ignite

Hi, Ignite does introduce some overhead to every entry, mostly because of its distributed nature. This is a tradeoff for having all the features provided by Ignite. 200 bytes per entry sounds correct, not taking indexing into account. See this page for details:

Re: Failed to find configuration in: file:////tmp/shared.xml

Hi, I responded you on StackOverflow: http://stackoverflow.com/questions/40891171/zookeeper-based-ignite-discovery-in-zeppelin-config-xml-not-working-even-after -Val On Wed, Nov 30, 2016 at 3:24 AM, pawantlor wrote: > I am using zookeeper based discovery for ignite

Re: Data in cache per node

Andrew, I don't see why you think that the memory usage is different. Can you clarify this? -Val On Wed, Nov 30, 2016 at 12:52 AM, Andrew Dzyuba wrote: > No, all entries are similar and have approximately same size. One entry is > row of plane file and look like: >

"Tuning Apache Ignite for Optimal Performance" webinar

Ignite Users, In couple of weeks (Nov 30) I'm going to conduct a webinar about performance tuning of Apache Ignite: https://www.gridgain.com/resources/webinars/tuning-apacher-ignitetm-optimal-performance Feel free to attend and ask tough questions :) -Val

Re: BinaryObject pros/cons

t every read of a string field in SQL results in > decoding overhead. > > Vladimir. > > On Fri, Oct 28, 2016 at 6:07 AM, Valentin Kulichenko < > valentin.kuliche...@gmail.com> wrote: > >> Cross-posting this to dev list. >> >> Vladimir, >> >> To be

Re: BinaryObject pros/cons

Cross-posting this to dev list. Vladimir, To be honest, I don't see much difference between null values for objects and zero values for primitives. From BinaryObject semantics standpoint, both are default values for corresponding types. These values will be returned from the BinaryObject.field()

Re: CacheWriter#writeAll javadocs inconsistent with implementations ?

Hi Kristian, I looked through your pull request and left my comments in the ticket. Before continuing the work, please go though the page [1], write a 'Hi!' email to the dev list with your JIRA username so that they can add you to the contributors list, and then assign the ticket to yourself.

Re: Why there are no official 1.6.0 and 1.7.0 ignite docker images on Docker Hub?

Crossposting to dev list. Igniters, Is there anyone who can create image for the recently released 1.7? -Val On Sat, Aug 6, 2016 at 2:18 PM, zshamrock wrote: > Why there is no official 1.6.0 and 1.7.0 ignite docker images on Docker Hub >

Re: Ignite instance hangs during restart in client mode

Crossposting to dev@. Folks, This is not the first time I see this issue. Is there a way to detect it and throw an exception? -Val On Fri, Feb 19, 2016 at 2:42 PM, vkulichenko wrote: > Hi Vinay, > > Yes, you should always create the configuration object from

Re: SchedulerFuture.nextExecutionTime() throws ArrayIndexOutOfBoundsException

Hi Steve, This happened because the pattern is invalid. It should be "{55, *} 53 3/5 * * *" (note the second parameter in curly braces). There is an exception because of this which immediately completes the future. Calling nextExecutionTime() on a completed future leads to this exception, which

Re: TcpDiscoveryVmIpFinder's isShared property

Yakov, JavaDoc is OK, but it seems to me that the confusion is caused by the fact that setShared() method is placed on the IpFinderAdapter, while it actually makes sense only for VmIpFinder. Can we deprecate it and always return false from isShared() method for JDBC, S3 and others? -Val On Mon,

Re: TcpDiscoveryVmIpFinder's isShared property

Andrey, Setting shared=true for TcpDiscoveryVmIpFinder means that nodes can discover each other only within one JVM, when all nodes use the same instance of IP finder. The shared "storage" in this case is just a local collection. We use this heavily in unit tests, for example.

Re: Stupide question about Queue ?

will start a separate thread on dev@ about this. [1] https://apacheignite.readme.io/docs/persistent-store -Val On Thu, Jan 14, 2016 at 11:16 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Created ticket for queue swapping feature: > https://issues.apache.org

Re: Leaks in the ContinuousQuery Notification

Hi wychoi, What kind of leak do you have and how do you detect it? Starting with 1.5, continuous queries support failover, so they maintain the update queues on backup nodes to make sure listener is notified even if primary node crashes. These queues are eventually cleaned up after updates are

Re: Serialization issue with Ignite 1.5 built from master (357d791)

Alex, I don't like this. I think both marshallers should behave in the same way and this behavior should be consistent with Java serialization spec. I hardly believe that classes like in Paulo's example will be used for communication with .NET/C++. And I would prefer to have such restrictions for

Re: SQL Performance indexing performance on-heap vs off-heap

Sergi, Can you please clarify what reasons for performance degradation you meant? Does it worth additional investigation or this is a known issue? -Val On Wed, Sep 16, 2015 at 7:42 PM, Dmitriy Setrakyan wrote: > > > On Thu, Sep 17, 2015 at 2:00 AM, Sergi Vladykin