Re: IgniteSet implementation: changes required

Hi Pavel, We have 2 types of data structures, collocated and non-collocated. The difference between them is that the collocated set is generally smaller and will always end up on the same node. Users generally will have many colllocated sets. On the other hand, a non-collocated set can span

Re: TcpCommunicationSpi in dockerized environment

Sergey, The way I "solved" this problem was to modify both org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi#getNodeAddresses(TcpDiscoveryNode, boolean) and org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi#nodeAddresses(ClusterNode) to make sure the external IP addresses (the

[jira] [Created] (IGNITE-7662) Slow event listener's work

Ruslan Gilemzyanov created IGNITE-7662: -- Summary: Slow event listener's work Key: IGNITE-7662 URL: https://issues.apache.org/jira/browse/IGNITE-7662 Project: Ignite Issue Type: Wish

[jira] [Created] (IGNITE-7664) SQL: throw sane exception on unsupported SQL statements

Alexander Paschenko created IGNITE-7664: --- Summary: SQL: throw sane exception on unsupported SQL statements Key: IGNITE-7664 URL: https://issues.apache.org/jira/browse/IGNITE-7664 Project: Ignite

Re: Apache Ignite 2.4 release

Nikolay, To merge it to 2.4, you need to merge the change to ignite-2.4 release. Let's do this if we come to an agreement in the neighbor thread. -Val On Thu, Feb 8, 2018 at 8:21 PM, Nikolay Izhikov wrote: > Hello, Dmitriy. > > IGNITE-7337 are merged to master [1] > > Do

Re: Saving Spark Data Frames merged to master

I think it's OK to merge it to 2.4, especially since the release is delayed. This is a fairly small feature which is fully isolated from everything else, so there are no risks. At the same time, it makes data frames integration much more valuable. -Val On Fri, Feb 9, 2018 at 5:20 AM, Nikolay

Re: Removing "fabric" from Ignite binary package name

Anton, I don't think we necessarily need to remove 'fabric' word from every file in the project, we just need to rename the name of downloadable package. Is there any other place where 'fabric' is exposed to the user? If that's the case, it should not be a big change, no? -Val On Fri, Feb 9,

Re: Reworking Ignite site's "Features" menu

Eventually finished with the menu as agreed grooming the content and introducing the architecture section: https://issues.apache.org/jira/browse/IGNITE-7061 Those who are ready to review before I merge the changes, do the following: * switch to a special SVN branch: “svn switch

[jira] [Created] (IGNITE-7663) AssertionError/NPE on "CREATE SCHEMA"

Mikhail Cherkasov created IGNITE-7663: - Summary: AssertionError/NPE on "CREATE SCHEMA" Key: IGNITE-7663 URL: https://issues.apache.org/jira/browse/IGNITE-7663 Project: Ignite Issue Type:

Re: Ignite work directory usage?

Dmitry, I meant the persistence store itself, but just realized that we don't have a marshaller cache anymore, we use discovery messages instead. However, we still have the MarshallerMappingFileStore which is basically a persistence space created specifically for marshaller mappings. I think it

Re: IgniteSet implementation: changes required

Pavel, I'm a bit confused. In my understanding, issue exists because we have local in-memory maps which are used as the main source of truth about which structures currently exist. During restart, we lose all this data even if data structures cache(s) are persisted. Once we fix this, issue goes

Re: IgniteSet implementation: changes required

Hello, Valentin. Thank you for the reply. As mentioned in this conversation, for now we have at least two issues with IgniteSet: 1. Incorrect behavior after recovery from PDS [1]. 2. The data in the cache is duplicated on-heap [2], which is not documented and lead to heap/GC overhead when using

Re: Removing "fabric" from Ignite binary package name

> I don't think we necessarily need to remove 'fabric' word from every file > in the project, we just need to rename the name of downloadable package. Couldn’t say it better than you, Val. Thanks for pitching in :) This is exactly what the ticket is about. — Denis > On Feb 9, 2018, at 11:53

Re: Saving Spark Data Frames merged to master

Agree, it is ok to merge, since we are waiting for the page replacement (eviction) performance fix anyway. Spark data frames is a long-awaited feature by our users, so it does make sense to provide a complete support in 2.4. D. On Fri, Feb 9, 2018 at 2:55 PM, Denis Magda

[jira] [Created] (IGNITE-7666) "Failed to parse query exception" has no description to find error in query

Mikhail Cherkasov created IGNITE-7666: - Summary: "Failed to parse query exception" has no description to find error in query Key: IGNITE-7666 URL: https://issues.apache.org/jira/browse/IGNITE-7666

Re: Saving Spark Data Frames merged to master

+1 It wasn’t an undiscussed merge. The question was raised here before [1]. Anyway, Anton thanks for being on guard all the times! :) [1] http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-4-release-td26031i20.html#a26807

[jira] [Created] (IGNITE-7667) Improve services failover and load balancing

Valentin Kulichenko created IGNITE-7667: --- Summary: Improve services failover and load balancing Key: IGNITE-7667 URL: https://issues.apache.org/jira/browse/IGNITE-7667 Project: Ignite

[jira] [Created] (IGNITE-7668) Cover menu and main page references with GA labels

Denis Magda created IGNITE-7668: --- Summary: Cover menu and main page references with GA labels Key: IGNITE-7668 URL: https://issues.apache.org/jira/browse/IGNITE-7668 Project: Ignite Issue

Re: IgniteSet implementation: changes required

Hi all, Current set implementation has significant flaw: all set data are duplicated in onheap maps on _every_ node in order to make iterator() and size(). For me it looks like simple yet ineffective implementation. Currently, these maps are damaged by checkpointing/recovery, and we could patch

[jira] [Created] (IGNITE-7665) .NET: Target .NET Standard 2.0

Pavel Tupitsyn created IGNITE-7665: -- Summary: .NET: Target .NET Standard 2.0 Key: IGNITE-7665 URL: https://issues.apache.org/jira/browse/IGNITE-7665 Project: Ignite Issue Type: Improvement

[GitHub] ignite pull request #3494: IGNITE-7438 LSQR solver for Linear Regression

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3494 ---

[jira] [Created] (IGNITE-7661) SQL COPY: provide more tests for national Unicode characters (including surrogates and 0x10000+ range)

Kirill Shirokov created IGNITE-7661: --- Summary: SQL COPY: provide more tests for national Unicode characters (including surrogates and 0x1+ range) Key: IGNITE-7661 URL:

[GitHub] ignite pull request #3498: IGNITE-3111 .NET: Configure SSL without Spring

GitHub user apopovgg opened a pull request: https://github.com/apache/ignite/pull/3498 IGNITE-3111 .NET: Configure SSL without Spring You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3111

[GitHub] ignite pull request #3499: IGNITE-7253

GitHub user alexpaschenko opened a pull request: https://github.com/apache/ignite/pull/3499 IGNITE-7253 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7253 Alternatively you can review and apply

[jira] [Created] (IGNITE-7660) Refactor LSQR algorithm

Anton Dmitriev created IGNITE-7660: -- Summary: Refactor LSQR algorithm Key: IGNITE-7660 URL: https://issues.apache.org/jira/browse/IGNITE-7660 Project: Ignite Issue Type: Improvement

Re: Removing "fabric" from Ignite binary package name

Denis, You're proposing changes without viewing a code :) On Thu, Feb 8, 2018 at 10:07 PM, Denis Magda wrote: > Anton, > > What’s wrong if we just go ahead and: > - replace “fabric” with “ignite” > - replace “hadoop” with “ignite-hadoop" > > — > Denis > > > On Feb 8, 2018,

Re: Saving Spark Data Frames merged to master

Nikolay, 2.4 is almost ready to be released. We're fixing final issues to provide stable and fast release. Merging something to 2.4 except blockers is not possible at this phase of release process. Hope, 2.5, with your changes, will be released soon :) On Fri, Feb 9, 2018 at 7:19 AM, Nikolay

[jira] [Created] (IGNITE-7659) Reduce multiple Trainer interfaces to one

Anton Dmitriev created IGNITE-7659: -- Summary: Reduce multiple Trainer interfaces to one Key: IGNITE-7659 URL: https://issues.apache.org/jira/browse/IGNITE-7659 Project: Ignite Issue Type:

[GitHub] ignite pull request #3497: ignite-2.5.1.b1 - ZookeeperDiscoverySpi

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/3497 ignite-2.5.1.b1 - ZookeeperDiscoverySpi You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.5.1.b1

TcpCommunicationSpi in dockerized environment

Hello Ignite community, When testing Ignite in dockerized environment I faced the following issue with current TcpComminicationSpi implementation. I had several physical machines and each Ignite node running inside Docker container had at least two InetAddresses associated with it: one IP

Re: Ignite work directory usage?

Hi Val, Do you mean by > switching marshaller cache to persistence instead of using these files makes perfect sense to me, using 'metastore' for marshaller cache? Sincerely, Dmitriy Pavlov пт, 9 февр. 2018 г. в 1:05, Valentin Kulichenko < valentin.kuliche...@gmail.com>: > Sergey, > > These

[GitHub] ignite pull request #3448: IGNITE-7476 IGNITE-7519 needed for reproducer of ...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3448 ---

[GitHub] ignite pull request #3490: IGNITE-7540 Sequential checkpoints cause overwrit...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3490 ---

Re: Saving Spark Data Frames merged to master

Hello, Anton. I have no any objections. Seems like some kind of misunderstanding from my side. As far as I can understand mail from Dmitriy Setrakyan [1] He agreed to include IGNITE-7337 to 2.4. If the Ccommuntiy decides to postpone this feature in 2.5 release I'm fully OK with it. [1]