[jira] [Created] (IGNITE-10725) Push Initial Commit to repository

2018-12-17 Thread Ilya Kasnacheev (JIRA)
Ilya Kasnacheev created IGNITE-10725: Summary: Push Initial Commit to repository Key: IGNITE-10725 URL: https://issues.apache.org/jira/browse/IGNITE-10725 Project: Ignite Issue Type:

Re: Continuous queries and duplicates

2018-12-17 Thread Piotr Romański
Hi all, sorry for answering so late. I would like to use SqlQuery because I can leverage indexes there. As it was already mentioned earlier, the partition update counter is exposed through CacheQueryEntryEvent. Initially, I thought that the partition update counter is something what's persisted

[jira] [Created] (IGNITE-10723) Investigate failures related to enabling tests (IGNITE-1094)

2018-12-17 Thread Vyacheslav Koptilin (JIRA)
Vyacheslav Koptilin created IGNITE-10723: Summary: Investigate failures related to enabling tests (IGNITE-1094) Key: IGNITE-10723 URL: https://issues.apache.org/jira/browse/IGNITE-10723

[jira] [Created] (IGNITE-10724) Publish Abbreviation Plugin source to supplimentary repo

2018-12-17 Thread Ilya Kasnacheev (JIRA)
Ilya Kasnacheev created IGNITE-10724: Summary: Publish Abbreviation Plugin source to supplimentary repo Key: IGNITE-10724 URL: https://issues.apache.org/jira/browse/IGNITE-10724 Project: Ignite

[jira] [Created] (IGNITE-10726) Web console: error in console after configuration import

2018-12-17 Thread Ilya Borisov (JIRA)
Ilya Borisov created IGNITE-10726: - Summary: Web console: error in console after configuration import Key: IGNITE-10726 URL: https://issues.apache.org/jira/browse/IGNITE-10726 Project: Ignite

Re: Is it time to move forward to JUnit4 (5)?

2018-12-17 Thread Павлухин Иван
Hi Oleg, Now concerns about junit3 elimination are clear for me. And I agree that it is worth to do it. By the way is it possible to access tests which have problems running under junit4? I would like to take a look. Also a clarifying bit regarding next migration steps is needed. Sorry if it was

Re: What is the best approach to extend Thin Client functionality?

2018-12-17 Thread Denis Magda
Hello Anton, Is this for TensorFlow only or for ML algorithms Ignite supplies out of the box? Also, do you need C++ for the training phase? -- Denis On Mon, Dec 17, 2018 at 2:02 AM dmitrievanth...@gmail.com < dmitrievanth...@gmail.com> wrote: > Currently ML/TensorFlow module requires an

[jira] [Created] (IGNITE-10727) [ML] InfModel and Model merging

2018-12-17 Thread Alexey Platonov (JIRA)
Alexey Platonov created IGNITE-10727: Summary: [ML] InfModel and Model merging Key: IGNITE-10727 URL: https://issues.apache.org/jira/browse/IGNITE-10727 Project: Ignite Issue Type:

Re: Abbreviation code-style requirement.

2018-12-17 Thread Павлухин Иван
Dmirity, Thank you! Permissions works for me. I will spend a while using a newly built plugin on my machine and then will publish it to the wiki and write back. пн, 17 дек. 2018 г. в 15:40, Dmitriy Pavlov : > > Hi Ivan, > > I've merged your PR and added permissions to the wiki, please check. >

[jira] [Created] (IGNITE-10722) Abbr-plugin: refactoring inside write action error

2018-12-17 Thread Ivan Pavlukhin (JIRA)
Ivan Pavlukhin created IGNITE-10722: --- Summary: Abbr-plugin: refactoring inside write action error Key: IGNITE-10722 URL: https://issues.apache.org/jira/browse/IGNITE-10722 Project: Ignite

Re: Is it time to move forward to JUnit4 (5)?

2018-12-17 Thread Павлухин Иван
Hi Oleg, The things become challenging. Truly I do not see any trivial solution so far. Could you please outline main problems which we are facing today? And how many tests are affected? Some clarifying questions: 1. I know that setup->test->teardown threading was changed for junit4 tests, but

[jira] [Created] (IGNITE-10709) New inspections introduced in 2018+ IntelliJ IDEA version must be disabled on TC configuration

2018-12-17 Thread Maxim Muzafarov (JIRA)
Maxim Muzafarov created IGNITE-10709: Summary: New inspections introduced in 2018+ IntelliJ IDEA version must be disabled on TC configuration Key: IGNITE-10709 URL:

[jira] [Created] (IGNITE-10710) Document new REST API for baseline topology command.

2018-12-17 Thread Andrey Novikov (JIRA)
Andrey Novikov created IGNITE-10710: --- Summary: Document new REST API for baseline topology command. Key: IGNITE-10710 URL: https://issues.apache.org/jira/browse/IGNITE-10710 Project: Ignite

[jira] [Created] (IGNITE-10712) Control.sh add ability to get cluster metrics

2018-12-17 Thread Sergey Antonov (JIRA)
Sergey Antonov created IGNITE-10712: --- Summary: Control.sh add ability to get cluster metrics Key: IGNITE-10712 URL: https://issues.apache.org/jira/browse/IGNITE-10712 Project: Ignite Issue

[jira] [Created] (IGNITE-10715) Remove boilerplate of settings 'TcpDiscoveryVmIpFinder' in tests

2018-12-17 Thread Vyacheslav Daradur (JIRA)
Vyacheslav Daradur created IGNITE-10715: --- Summary: Remove boilerplate of settings 'TcpDiscoveryVmIpFinder' in tests Key: IGNITE-10715 URL: https://issues.apache.org/jira/browse/IGNITE-10715

[jira] [Created] (IGNITE-10716) Rest clients should call ctx.security().onSessionExpired(subjid) on disconnect to avoid the possible leaking of the memory

2018-12-17 Thread Andrey Aleksandrov (JIRA)
Andrey Aleksandrov created IGNITE-10716: --- Summary: Rest clients should call ctx.security().onSessionExpired(subjid) on disconnect to avoid the possible leaking of the memory Key: IGNITE-10716 URL:

Re: Set 'TcpDiscoveryVmIpFinder' as default IP finder for tests instead of 'TcpDiscoveryMulticastIpFinder'

2018-12-17 Thread Vyacheslav Daradur
Andrey Mashenkov, at first sight, I have not seen any problems with .NET platform. I believe we need carefully configure ports in platform's examples, additional actions should not be required. On Mon, Dec 17, 2018 at 2:35 PM Vyacheslav Daradur wrote: > > The task [1] is done. > >

[jira] [Created] (IGNITE-10711) [ML] [Umbrella] Provide metrics to evaluate the quality of model

2018-12-17 Thread Aleksey Zinoviev (JIRA)
Aleksey Zinoviev created IGNITE-10711: - Summary: [ML] [Umbrella] Provide metrics to evaluate the quality of model Key: IGNITE-10711 URL: https://issues.apache.org/jira/browse/IGNITE-10711

[jira] [Created] (IGNITE-10713) [ML] Refactor examples with accuracy calculation and another metrics usage

2018-12-17 Thread Aleksey Zinoviev (JIRA)
Aleksey Zinoviev created IGNITE-10713: - Summary: [ML] Refactor examples with accuracy calculation and another metrics usage Key: IGNITE-10713 URL: https://issues.apache.org/jira/browse/IGNITE-10713

[jira] [Created] (IGNITE-10714) MVCC TX: JTA transaction manager.

2018-12-17 Thread Igor Seliverstov (JIRA)
Igor Seliverstov created IGNITE-10714: - Summary: MVCC TX: JTA transaction manager. Key: IGNITE-10714 URL: https://issues.apache.org/jira/browse/IGNITE-10714 Project: Ignite Issue Type:

Re: Set 'TcpDiscoveryVmIpFinder' as default IP finder for tests instead of 'TcpDiscoveryMulticastIpFinder'

2018-12-17 Thread Vyacheslav Daradur
The task [1] is done. 'TcpDiscoveryVmIpFinder' is default IP finder in tests now. The IP finder is initialized on per tests class level to avoid hidden affecting among tests, it means the test methods in the common test class will use the same IP finder. You don't need to set up

What is the best approach to extend Thin Client functionality?

2018-12-17 Thread dmitrievanthony
Currently ML/TensorFlow module requires an ability to expose some functionality to be used in C++ code. As far as I understand, currently Ignite provides an ability to work with it from C++ only through the Thin Client. The list of operations supported by it is very limited. What is the best

Re: Abbreviation code-style requirement.

2018-12-17 Thread Павлухин Иван
Hi, I did some investigation regarding scala support and it seems that version used today (3.0.0) was build without scala support. If nobody minds I suggest to build a new version without scala as well. Also there is a thing that bothers me a little. IDEA throws exception in log when a name is

Re: What is the best approach to extend Thin Client functionality?

2018-12-17 Thread Igor Sapego
Hello, First of all, it would help to know what is the functionality you need, to give you an answer. Can you scribed required API? Best Regards, Igor On Mon, Dec 17, 2018 at 1:02 PM dmitrievanth...@gmail.com < dmitrievanth...@gmail.com> wrote: > Currently ML/TensorFlow module requires an

Re: Broken layout of Ignite javadoc on web

2018-12-17 Thread Dmitriy Pavlov
I see the same, browsers checked: Edge & Chrome. I guess it is not a layout is broken, but a style missing. Unfortunately, I don't know how to fix. Probably we should start research from ignite/pom.xml:191 ${basedir}/assembly/docfiles/javadoc.css пн, 17 дек. 2018 г. в 14:32, Павлухин Иван : >

Re: Code inspection

2018-12-17 Thread Maxim Muzafarov
Dmitry, It seems to me that we have two independent issues here. 1. An `Unexpected error during build messages processing in TeamCity` error message which is related to TC agent configuration. Suppose, server.log will provide us more details about it. I have to access there. 2. A new set of

[jira] [Created] (IGNITE-10717) Behaviour of Binary Marshaller not consistent with Deployment Mode

2018-12-17 Thread Gert Dubois (JIRA)
Gert Dubois created IGNITE-10717: Summary: Behaviour of Binary Marshaller not consistent with Deployment Mode Key: IGNITE-10717 URL: https://issues.apache.org/jira/browse/IGNITE-10717 Project: Ignite

Re: Page eviction for in-memory mode with enabled MVCC

2018-12-17 Thread Roman Kondakov
Ivan, probably you are right. The main usage of in-memory cache with allowed evictions is a caching layer for third party stores. And the fact that page eviction is not a transactional process by the nature, forces user to use workarounds (i.e. explicit locking) to prevent evictions of the

Broken layout of Ignite javadoc on web

2018-12-17 Thread Павлухин Иван
Hi, I noticed that Ignite javadoc layout on web for latest versions has some problems. For example, I see no links near the "Class" at heading of the page [1]. Here is a screenshot [2]. Do you see the same? I was able to build javadoc on my machine. With current configuration I see the same

Re: Abbreviation code-style requirement.

2018-12-17 Thread Dmitriy Pavlov
Hi Ivan, I've merged your PR and added permissions to the wiki, please check. I still feel we need to migrate code to ASF repo. I will try to do something for that. Sincerely, Dmitriy Pavlov пн, 17 дек. 2018 г. в 13:44, Павлухин Иван : > Hi, > > I did some investigation regarding scala

Re: Apache Ignite TeamCity Bot - muted tests

2018-12-17 Thread Dmitrii Ryabov
Dmitriy, with ignore annotations we will need to check forgotten tests manually. Thats bad, but we will save some machine time in common runs. пн, 17 дек. 2018 г. в 17:06, Dmitriy Pavlov : > > Investigation parameters: Can leave as empty > Unmute: Manual (don't use auto because of flaky tests) >

Re: What is the best approach to extend Thin Client functionality?

2018-12-17 Thread Ilya Kasnacheev
Hello! We absolutely have C++ thick client and can implement very complex API on top of it. However, there is also push towards thin clients currently since they're easier to get working. So naturally you have to decide according to your use cases. Bonus points if you find a way to go with

Re: Apache Ignite TeamCity Bot - muted tests

2018-12-17 Thread Anton Vinogradov
Great feature! Could you please explain how to have a deal with it? How should I mite/unmute tests for now? On Fri, Dec 14, 2018 at 6:50 PM Dmitriy Pavlov wrote: > We have IgniteIgnore, so we can use it. It seems behavior is the same. We > need just to understand in which case we can get issue

Re: Apache Ignite TeamCity Bot - muted tests

2018-12-17 Thread Dmitrii Ryabov
Anton, In the "Mute" column you can find link to the test on TeamCity. On this page you can see test details like run history and current mutes. Here you should be able to unmute existing mutes. пн, 17 дек. 2018 г. в 16:21, Anton Vinogradov : > > Great feature! > > Could you please explain how to

Re: Apache Ignite TeamCity Bot - muted tests

2018-12-17 Thread Dmitriy Pavlov
Investigation parameters: Can leave as empty Unmute: Manual (don't use auto because of flaky tests) Text: https://issues.apache.org/jira/browse/IGNITE-N But anyway, I hope in the nearest future best way to mute test will be to ignore it using: @IgniteIgnore or @Ignore or Assume.that() In

Re: Broken layout of Ignite javadoc on web

2018-12-17 Thread Павлухин Иван
Dmitriy, Yep, it looks like the problem is inside assembly/docfiles/javadoc.css I will try to dig into some time later on a spare time. Of course, if nobody fixes the problem earlier. пн, 17 дек. 2018 г. в 15:18, Dmitriy Pavlov : > > I see the same, browsers checked: Edge & Chrome. I guess it is

Re: Place Ignite Abbrev Plugin to ASF Ignite supplementary git repo

2018-12-17 Thread Dmitriy Pavlov
Hi Igniters, I've created an empty repository : New repository ignite-abbrev-plugin.git was created, as requested by dpavlov. You may view it at: https://gitbox.apache.org/repos/asf/ignite-abbrev -plugin.git Alex G., could you please prepare a PR with your initial changes from

Re: Apache Ignite TeamCity Bot - muted tests

2018-12-17 Thread Anton Vinogradov
Dmitrii, My question was mostly about how to mute test properly. On Mon, Dec 17, 2018 at 4:27 PM Dmitrii Ryabov wrote: > Anton, > > In the "Mute" column you can find link to the test on TeamCity. On > this page you can see test details like run history and current mutes. > Here you should be

[jira] [Created] (IGNITE-10718) [ML] Merge XGBoost and Ignite ML Trees together

2018-12-17 Thread Anton Dmitriev (JIRA)
Anton Dmitriev created IGNITE-10718: --- Summary: [ML] Merge XGBoost and Ignite ML Trees together Key: IGNITE-10718 URL: https://issues.apache.org/jira/browse/IGNITE-10718 Project: Ignite

Re: Is it time to move forward to JUnit4 (5)?

2018-12-17 Thread oignatenko
Hi Ivan, Per my cursory check of the code currently in master, we have 239 test classes that couldn't migrate (that's probably about 500 or something test cases). For comparison, over 1600 classes migrated without problems. This is to answer your questions about how many tests are affected by

Re: How to begin to contribute

2018-12-17 Thread Dmitriy Pavlov
Hi Michael, I'm trying to reach you in https://issues.apache.org/jira/browse/IGNITE-7153 mentions. To proceed with patch according to https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-SubmittingforReview we need to set the ticket to Patch Available state. If

[jira] [Created] (IGNITE-10721) Documentation: Fix UUID thin client format description

2018-12-17 Thread Igor Sapego (JIRA)
Igor Sapego created IGNITE-10721: Summary: Documentation: Fix UUID thin client format description Key: IGNITE-10721 URL: https://issues.apache.org/jira/browse/IGNITE-10721 Project: Ignite

[jira] [Created] (IGNITE-10720) Decrease time to save metadata during checkpoint

2018-12-17 Thread Anton Kalashnikov (JIRA)
Anton Kalashnikov created IGNITE-10720: -- Summary: Decrease time to save metadata during checkpoint Key: IGNITE-10720 URL: https://issues.apache.org/jira/browse/IGNITE-10720 Project: Ignite

Re: Thin clients all in one

2018-12-17 Thread Alexey Kosenchuk
Hi Stepan, 1) About UUID... UUID binary encoding must be defined in the Binary Protocol specification (https://apacheignite.readme.io/docs/binary-client-protocol-data-format#section-uuid-guid-) So, it's the issue against the spec first. Regarding the clients.. Python client uses Python

[jira] [Created] (IGNITE-10719) [ML] LEarningEnvironmentBuilder is not passed in makeBagged

2018-12-17 Thread Artem Malykh (JIRA)
Artem Malykh created IGNITE-10719: - Summary: [ML] LEarningEnvironmentBuilder is not passed in makeBagged Key: IGNITE-10719 URL: https://issues.apache.org/jira/browse/IGNITE-10719 Project: Ignite

Re: Apache Ignite TeamCity Bot - muted tests

2018-12-17 Thread Anton Vinogradov
>> In this case, we will not need TeamCity mutes anymore. Sounds great! On Mon, Dec 17, 2018 at 5:23 PM Dmitrii Ryabov wrote: > Dmitriy, > > with ignore annotations we will need to check forgotten tests > manually. Thats bad, but we will save some machine time in common > runs. > пн, 17 дек.

RE: Pre-touch for Ignite off-heap memory

2018-12-17 Thread Stanislav Lukyanov
I don’t think these two issues require to be solved together, although I agree there is some connection. I guess we agree that pre-touch should a be off by default. Similarly, lazy data region initialization from IGNITE-9113 can be on by default. We can have two boolean properties controlling

Re: Code inspection

2018-12-17 Thread Andrey Mashenkov
Maxim, Looks ok. Let's apply IGNITE-10682. All, Also, I'd like to publish idea.logs into artefacts by default. This will give us more details for investigation in future if any failure will occurs. It will costs 1-10 kB. On Mon, Dec 17, 2018 at 3:21 PM Maxim Muzafarov wrote: > Dmitry, > > It