Re: Unit testing of persistence & durable memory

Thanks Dmitriy! Is it possible to start Ignite instance in the tests if needed or is it only needed for basic isolated method tests? D. On Wed, Feb 7, 2018 at 6:24 AM, Dmitry Pavlov wrote: > Hi Igniters, > > Recently new unit tests suite was added to TC run chain, it is

Re: Next Steps: GA Grid: Request to contribute GA library to Apache Ignite

Denis, Thank's for following up.. Please let me know once the paperwork has been completed.. In addition, I agree with releasing GA Grid as part of ML framework in Ignite 2.5. Just let me know if you require additional information beyond what I have provided. Regards, Turik Campbell --

Re: Eviction policies with persistence

Thanks folks. I’ll improve the doc by 2.4 release: IGNITE-7645 - Clarify eviction policy documentation — Denis > On Feb 6, 2018, at 11:25 PM, Alexey Goncharuk > wrote: > > Denis, > > Yes, if there are no

[jira] [Created] (IGNITE-7645) Clarify eviction policy documentation

Denis Magda created IGNITE-7645: --- Summary: Clarify eviction policy documentation Key: IGNITE-7645 URL: https://issues.apache.org/jira/browse/IGNITE-7645 Project: Ignite Issue Type: Task

Re: HelloWorld!

Hello Yaroslav, Welcome to the Ignite community! Please subscribe to both dev and user lists: https://ignite.apache.org/community/resources.html#mail-lists Get familiar with Ignite development process described here: https://cwiki.apache.org/confluence/display/IGNITE/Development+Process

Re: Removing "fabric" from Ignite binary package name

Anton, I don’t get how the hadoop editions are related to this task. The project is not named as “data fabric” for a while. Check up the site or docs. The “fabric” word is being removed from all over the places and needs to be removed from the editions’ names. As for the hadoop future, my

Re: Abandoned Patch Available JIRA tickets

Anyway, your suggestion requires to have self-disciplined committers that will be keeping track of the tickets they promised to review. I’m ready to propose a guideline here but the committers have to be committed to that. Otherwise, I’ll just waste my time. — Denis > On Feb 7, 2018, at 1:41

Re: Apache Ignite 2.4 release

Agree on both, the performance fix and the spark data frames. Let's get them into the release. However, Raymond is right. We should know how long the performance fix will take. If it adds another month to the development, we should include it into the next release. I am hoping that it can be done

Re: Apache Ignite 2.4 release

Hello, Igniters. Please, consider including IGNITE-7337 - Spark Data Frames: support saving a data frame in Ignite [1] in the 2.4 release. It seems we can merge it into the master in a day or few. [1] https://issues.apache.org/jira/browse/IGNITE-7337 В Ср, 07/02/2018 в 08:35 -0800, Denis

Re: Apache Ignite 2.4 release

I’m voting for the blocker addition into the release. Sergey K. how will it affect your testing cycles? Do you need to re-run everything from scratch and how many days you need? — Denis > On Feb 6, 2018, at 11:29 PM, Alexey Goncharuk > wrote: > > Guys, > >

[jira] [Created] (IGNITE-7644) Add an utility to export all key-value data from a persisted partition

Alexey Goncharuk created IGNITE-7644: Summary: Add an utility to export all key-value data from a persisted partition Key: IGNITE-7644 URL: https://issues.apache.org/jira/browse/IGNITE-7644

[GitHub] ignite pull request #3488: IGNITE-7605: Add more SQL parser tests for COPY c...

GitHub user gg-shq opened a pull request: https://github.com/apache/ignite/pull/3488 IGNITE-7605: Add more SQL parser tests for COPY command You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7605

Re: HelloWorld!

Hi! Please get familiar with Ignite development process described here: https://cwiki.apache.org/confluence/display/IGNITE/Development+Process Subscribe to both dev and user lists: https://ignite.apache.org/community/resources.html#mail-lists <

[GitHub] ignite pull request #3487: IGNITE-7535: Implement CHARSET option in COPY ......

GitHub user gg-shq opened a pull request: https://github.com/apache/ignite/pull/3487 IGNITE-7535: Implement CHARSET option in COPY ... FORMAT CSV command You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: Removing "fabric" from Ignite binary package name

Anton, We already had a discussion about this: http://apache-ignite-developers.2346864.n4.nabble.com/ignite-spark-module-in-Hadoop-Accelerator-td12343.html While I'm personally very much for getting rid of two separate editions, we didn't come to consensus there. -Val On Wed, Feb 7, 2018 at

[GitHub] ignite pull request #3485: IGNITE-7586: Added COPY command into the JDBC exa...

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

Re: HelloWorld!

I would like to get acquainted with the product and contribute to its development. I am middle-level developer and I would take some simple task to join the community. 2018-02-07 18:22 GMT+03:00 Alexey Kuznetsov : > Hello! > > Do you have questions about Ignite? > Or

Re: Stop nodes after test by default - IGNITE-6842

Thank you all, I'll add this comment's for JIRA ticket, if you don't mind. ср, 7 февр. 2018 г. в 15:16, Dmitry Pavlov : > Yes, this solution allows to cover both cases: > a) not stopped node from previous test and > b) allows to remove useless code that stops Ignite nodes

[GitHub] ignite pull request #3468: IGNITE-7508: Fix contention on system property ac...

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

Re: HelloWorld!

Hello! Do you have questions about Ignite? Or willing to contribute? :) On Wed, Feb 7, 2018 at 7:46 PM, Yaroslav Lymar wrote: > Hello anybody! > -- Alexey Kuznetsov

[GitHub] ignite pull request #3486: Ignite 7263

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

Unit testing of persistence & durable memory

Hi Igniters, Recently new unit tests suite was added to TC run chain, it is PDS unit test suite. See https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_IgnitePdsUnitTests and corresponding suite in code org.apache.ignite.testsuites.IgnitePdsUnitTestSuite This suite contain

[GitHub] ignite pull request #3485: IGNITE-7586: Added COPY command into the JDBC exa...

GitHub user gg-shq opened a pull request: https://github.com/apache/ignite/pull/3485 IGNITE-7586: Added COPY command into the JDBC example. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7586

HelloWorld!

Hello anybody!

[GitHub] ignite pull request #2558: IGNITE-6217 Add benchmark to compare JDBC drivers...

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

Re: Stop nodes after test by default - IGNITE-6842

Yes, this solution allows to cover both cases: a) not stopped node from previous test and b) allows to remove useless code that stops Ignite nodes from each test. ср, 7 февр. 2018 г. в 15:13, Anton Vinogradov : > Maxim, > > We discussed with Dima privately, and decided

Re: Stop nodes after test by default - IGNITE-6842

Maxim, We discussed with Dima privately, and decided 1) We have to assert that there is no alive nodes at GridAbstractTest's beforeTestsStarted 2) We have to kill all alive nodes (without force) at GridAbstractTest's afterTestsStopped 3) In case of any exceptions at #2 we have to see test error

[GitHub] ignite pull request #3484: IGNITE-7451: Make Linear SVM for multi-classifica...

GitHub user zaleslaw opened a pull request: https://github.com/apache/ignite/pull/3484 IGNITE-7451: Make Linear SVM for multi-classification Added model, trainer and tests for them You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #3483: IGNITE-7436 Username/password authentication for ...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/3483 IGNITE-7436 Username/password authentication for thin clients You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #3482: IGNITE-7538 Introduce new test project for Ignite...

GitHub user vveider opened a pull request: https://github.com/apache/ignite/pull/3482 IGNITE-7538 Introduce new test project for Ignite 2.0+ with Java 8 / Java 9 compatibility You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #3481: IGNITE-7638: Test created to reproduce FullPageId...

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/3481 IGNITE-7638: Test created to reproduce FullPageIdTable You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7638

[GitHub] ignite pull request #3419: IGNITE-6917: SQL: implement COPY command for effi...

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

Re: Stop nodes after test by default - IGNITE-6842

> Let's just add stopAllGrids(flase) to GridAbstractTest 's afterTestsStopped method body. Can't agree with it becase implicit silent shutdown of nodes from test framework may cause a lot of bugs introduced to Ignite. I think stop+test fail should occur. In that case author of incorrect test or

Re: Stop nodes after test by default - IGNITE-6842

Hi all, > I've made some research about this problem and i think that in general we > should move stopAllGrids method in GridAbstractTest class to > afterTestsStopped method with some changes. Am I right? Let's just add stopAllGrids(flase) to GridAbstractTest 's afterTestsStopped method body. >

Re: Apache Ignite 2.4 release

Thanks for the clarification Dmitry. Sent from my iPhone > On 7/02/2018, at 11:13 PM, Dmitry Pavlov wrote: > > Hi Raymond, > > Minor releases were discussed already at dev list. Community does not > support minor releases. In case of emergency fix is required, full

Re: Stop nodes after test by default - IGNITE-6842

Hi Igniters, IMO nodes that survive between tests is not general practice and I'm not sure is a best practice. I suggest to mark such tests with some method overriden from AbstractTest. About cancel flag, please note stopAllGrids(boolean cancel) cancel=false allows to wait of checkpoint ends in

Re: Apache Ignite 2.4 release

Hi Raymond, Minor releases were discussed already at dev list. Community does not support minor releases. In case of emergency fix is required, full release process has to be followed for next release, e.g. for 2.5. Exactly that type of release was 2.2, it was emergency release for fix

Re: Removing "fabric" from Ignite binary package name

Denis, Petr, I checked PR and found we have *overcomplicated* logic with "fabric" and "hadoop" postfixs. Do we really need to assembly 2 editions? "Hadoop" edition still valued? My proposal is to get rid of "hadoop" edition and replace it with instruction of how to use "fabric" edition instead.

Re: Stop nodes after test by default - IGNITE-6842

Hi Maxim, Regarding your first question, the use of afterTestsStopped is not enough to stop all nodes, since each individual test (method) can start custom set of notes during its operation, and this very test should stop all those nodes. If you delegate closing to afterTestsStopped this will

[GitHub] ignite pull request #3480: IGNITE-7643: broken javadoc.

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

Re: Abandoned Patch Available JIRA tickets

Periodic punches can frustrate committers, and also it's unpleasant for contributors. Most IP->PA transitions are commented with something like "John Doe, this awesome feature is ready and needs your review." Maybe it's better to adopt following rule of thumb? If the change is clean and

Re: Text query with persistence

Thanks Alexey, I'll take a look on it! 07.02.2018 11:48, Alexey Goncharuk пишет: Hi Dmitriy, We do have a ticket for this [1], however, I am not sure it will be completed any time soon. As for the rebuilding indexes at the node startup, we already have an internal routine for this (see

Re: Text query with persistence

Hi Dmitriy, We do have a ticket for this [1], however, I am not sure it will be completed any time soon. As for the rebuilding indexes at the node startup, we already have an internal routine for this (see GridQueryIndexing#rebuildIndexesFromHash). The only thing we need to implement is skipping

[GitHub] ignite pull request #3480: IGNITE-7643: broken javadoc.

GitHub user ybabak opened a pull request: https://github.com/apache/ignite/pull/3480 IGNITE-7643: broken javadoc. fixed You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7643 Alternatively you can

Text query with persistence

Hi guys, We have Apache Lucene based full text search that creates in-memory indexes. It's a nice feature, but it seems absolutely useless with persistence as indexes are dropped on node restart. Probably we need a configuration flag and\or API call to rebuild them, or persist somehow. Do

[jira] [Created] (IGNITE-7643) Broken javadoc in partitioned dataset

Yury Babak created IGNITE-7643: -- Summary: Broken javadoc in partitioned dataset Key: IGNITE-7643 URL: https://issues.apache.org/jira/browse/IGNITE-7643 Project: Ignite Issue Type: Task