Re: IGNITE-4212 (Ignite Benchmarking Simplification and Automation)

> >> Ignite binaries, preferably they need to be added to auto-generated > >> README.txt. *Anton*, is it feasible to do? > >> > >> Finally, when apply the reviews notes please build and share Ignite > >> binaries with your patch. Want to see the new project st

Re: How to improve SQL testing

Hi, If there are no objections, I'd like implement this feature. Oleg On Tue, Jan 31, 2017 at 12:07 AM, Denis Magda wrote: > Hi, > > That’s true that the utility/testing framework needs to be as flexible as > possible. If the community can’t reuse an existing one let’s make

Re: IGNITE-4212 (Ignite Benchmarking Simplification and Automation)

*, please review modifications in the build procedures. > > — > Denis > > > On Jan 31, 2017, at 3:12 AM, Oleg Ostanin <oosta...@gridgain.com> wrote: > > > > Hi Denis, > > > > Yes, we have included Ignite Yardstick source files with its pom.xml in > > Ignit

Re: IGNITE-4212 (Ignite Benchmarking Simplification and Automation)

https://drive.google.com/open?id=0B9teTzJ9iIvHckl6eVQ3N0R4a3c On Fri, Feb 10, 2017 at 12:43 AM, Oleg Ostanin <oosta...@gridgain.com> wrote: > I've fixed README.txt and created new DEVNOTES.txt. Also renamed sample > benchmark configuration file to benchmark-sample.properties. &

Re: Apache Ignite 1.9

; >>> Sergey > > > > > >>> > > > > > >>> > > > > > >>> > > > > > >>> 2017-02-09 23:58 GMT+03:00 Denis Magda <dma...@apache.org>: > > > > > >>> > > > > > >&

Re: IGNITE-4212 (Ignite Benchmarking Simplification and Automation)

Hi. I just discovered that some functionality does not work correctly. I will present fixed version later. On Fri, Feb 10, 2017 at 12:43 AM, Oleg Ostanin <oosta...@gridgain.com> wrote: > https://drive.google.com/open?id=0B9teTzJ9iIvHckl6eVQ3N0R4a3c > > On Fri, Feb 10, 2017 at

Re: IGNITE-4212 (Ignite Benchmarking Simplification and Automation)

I'm sorry, there wasn't any problem with the build, it was local problem on my machine. On Fri, Feb 10, 2017 at 11:54 AM, Oleg Ostanin <oosta...@gridgain.com> wrote: > Hi. > > I just discovered that some functionality does not work correctly. I will > present fixed version late

[GitHub] ignite pull request #1333: Ignite 3292

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

[GitHub] ignite pull request #1333: Ignite 3292

Github user oleg-ostanin closed the pull request at: https://github.com/apache/ignite/pull/1333 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[GitHub] ignite pull request #1324: Ignite 3292 fixed

Github user oleg-ostanin closed the pull request at: https://github.com/apache/ignite/pull/1324 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

IGNITE-4212 (Ignite Benchmarking Simplification and Automation)

Hello Igniters! I'm working on ticket IGNITE-4212 "Ignite Benchmarking Simplification and Automation" and I'd like to ask your opinion about ignite-yardstick: where do you think is the most appropriate place to put a compiled ignite-yardstick module in the apache-ignite binary assembly? We can put

[GitHub] ignite pull request #1324: Ignite 3292 fixed

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/1324 Ignite 3292 fixed log file looks like this: ... <15:02:48> Preloading started. <15:02:48> Preloading:atomic-index 0(+0) <15:02:48>

request an access to jira project

Hello Ignite community! My name is Oleg and I want to contribute to Apache Ignite. I want to start with this issue - IGNITE-4058. Please, provide me access to jira project, my username oleg-ostanin. Thanks.

[GitHub] ignite pull request #1317: IGNITE-3292 Yardstick: add logging of preloading ...

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/1317 IGNITE-3292 Yardstick: add logging of preloading progress You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite

Re: request an access to jira project

And again thank you! Best regards Oleg On Fri, Dec 2, 2016 at 8:35 AM, Dmitriy Setrakyan <dsetrak...@apache.org> wrote: > Done. Feel free to assign the ticket to yourself. > > On Fri, Dec 2, 2016 at 8:26 AM, Oleg Ostanin <oosta...@gridgain.com> > wrote: > > &g

Re: request an access to jira project

Thank you! My username is oleg-ostanin. Best regards Oleg On Fri, Dec 2, 2016 at 6:37 AM, Dmitriy Setrakyan <dsetrak...@apache.org> wrote: > Oleg, > > Welcome to the Ignite community! > > You should just register for Apache Jira here: > https://issues.apache.org/jira/se

Re: IGNITE-4212 (Ignite Benchmarking Simplification and Automation)

016 at 12:37 AM, Oleg Ostanin <oosta...@gridgain.com> > wrote: > > > Hello Igniters! > > I'm working on ticket IGNITE-4212 "Ignite Benchmarking Simplification and > > Automation" and I'd like to ask your opinion about ignite-yardstick: > where > &

[GitHub] ignite pull request #1365: Ignite 3292

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

Re: IGNITE-4212 (Ignite Benchmarking Simplification and Automation)

I mean removing those configs from binary assembly, not from repository. On Tue, Dec 27, 2016 at 4:28 PM, Oleg Ostanin <oosta...@gridgain.com> wrote: > Hello Igniters. > I think it would be better to remove some configuration files from > benchmarks/config: > > ignite

Re: IGNITE-4212 (Ignite Benchmarking Simplification and Automation)

;> there’re > >>>>>>> not, I would agree on this and get down to the implementation. > >>>>>>> > >>>>>>> — > >>>>>>> Denis > >>>>>>> > >>>>>>>>

[GitHub] ignite pull request #1317: IGNITE-3292 Yardstick: add logging of preloading ...

Github user oleg-ostanin closed the pull request at: https://github.com/apache/ignite/pull/1317 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[GitHub] ignite pull request #1838: Ignite gg 11423 from20

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/1838 Ignite gg 11423 from20 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-11423-from20 Alternatively you

[GitHub] ignite pull request #1840: Ignite gg 11423 from20

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/1840 Ignite gg 11423 from20 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-11423-from20 Alternatively you

Re: .sha Release Distribution Policy

Hi, Denis Yes, we have a ticket that already takes this into account: https://issues.apache.org/jira/browse/IGNITE-5817 I think we can create both sha-256 and sha-512 checksums. Best regards Oleg On Thu, Aug 17, 2017 at 1:51 AM, Denis Magda wrote: > Igniters, especially the

[GitHub] ignite pull request #2310: removed excluding ML sources from assembly file

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/2310 removed excluding ML sources from assembly file You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.1

[GitHub] ignite pull request #2308: IGNITE-5762 skipping lgpl and examples deploy

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/2308 IGNITE-5762 skipping lgpl and examples deploy You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5762

[GitHub] ignite pull request #2286: IGNITE-5740 created new benchmark for load transa...

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/2286 IGNITE-5740 created new benchmark for load transaction You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5740

сhecksum algorythm

Hi, We need to decide what сhecksum algorythm we should use for signing release artifacts. Currently we use md5 and sha-1. sha-1 will be replaced by sha-256 soon. Should we keep md5 or use only sha-256?

Re: [VOTE] Apache Ignite 2.1.0 RC2

Hi Vyacheslav Yes, we changed build procedure, please look in the DEVNOTES.txt. On Wed, Jul 19, 2017 at 12:53 PM, Vyacheslav Daradur wrote: > Hi guys. > I've downloaded apache-ignite-2.1.0-src.zip, unpack it and execute "mvn > package -DskipTests" > result is succes, but

[GitHub] ignite pull request #2338: IGNITE-5807 added new profile to fix artifacts si...

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/2338 IGNITE-5807 added new profile to fix artifacts signing, edited DEVNOT… …ES.txt You can merge this pull request into a Git repository by running: $ git pull https://github.com

[GitHub] ignite pull request #2310: removed excluding ML sources from assembly file

Github user oleg-ostanin closed the pull request at: https://github.com/apache/ignite/pull/2310 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[GitHub] ignite pull request #1886: Ignite 2.0 temp for fix hibernate upload

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/1886 Ignite 2.0 temp for fix hibernate upload You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.0-temp-for-fix

[GitHub] ignite pull request #1889: Ignite 5120

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

release procedure

Hi, I'd like to start a discussion about Apache Ignite release procedure. I'm working on ticket Ignite-5249 "The release build procedure should be placed on the CI/CD server and available to run for the release engineer." https://issues.apache.org/jira/browse/IGNITE-5249 Currently we have

Re: release procedure

ons expressed in this email are those of the author, > and do not necessarily represent the views of any company the author > might be affiliated with at the moment of writing. > > > On Sun, Aug 6, 2017 at 5:37 AM, Oleg Ostanin <oosta...@gridgain.com> > wrote: > > Hi, > &

[GitHub] ignite pull request #1954: ignite-gg-12199 added new variable CLEAN_WORK_DIR...

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/1954 ignite-gg-12199 added new variable CLEAN_WORK_DIR in config files You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: Suggested changes for Apache Ignite Release procedure

+1 I have assigned the ticket to myself and I did some preliminary investigations in this matter. It seems to me the most complicated part will be configuring tasks in such way that release commiter could use it without exposing his credentials for Git, SVN and Maven. I suggest we create an

[GitHub] ignite pull request #1954: ignite-gg-12199 added new variable CLEAN_WORK_DIR...

Github user oleg-ostanin closed the pull request at: https://github.com/apache/ignite/pull/1954 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[GitHub] ignite pull request #1838: Ignite gg 11423 from20

Github user oleg-ostanin closed the pull request at: https://github.com/apache/ignite/pull/1838 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[GitHub] ignite pull request #2801: removed excluding ML from examples/src

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/2801 removed excluding ML from examples/src You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite remove-ml-excluding

Re: Adding sqlline tool to Apache Ignite project

Another build with sqlline included: https://ci.ignite.apache.org/viewLog.html?buildId=881120=artifacts=IgniteRelease_XxxFromMirrorIgniteRelease3PrepareVote#!1rrb2,-wpvx2aopzexz,1esn4zrslm4po,-h8h0hn9vvvxp On Sun, Oct 8, 2017 at 5:11 PM, Denis Magda wrote: > No more doubts

Re: Adding sqlline tool to Apache Ignite project

must have for the ticket resolution. > > Denis > > On Monday, October 9, 2017, Anton Vinogradov <avinogra...@gridgain.com> > wrote: > > > Any plans to have ignitesql.bat? > > > > On Mon, Oct 9, 2017 at 5:29 PM, Oleg Ostanin <oosta...@gridgain.com > >

[GitHub] ignite pull request #2861: Ignite 5608

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

Re: Adding sqlline tool to Apache Ignite project

ooks good to me. Please consider the notes left in the ticket. I want us > to prepare a script for Windows, review the language for help notice and > errors, put together documentation. Prachi will be able to help with the > editing and documentation. > > — > Denis > > > On Oct

[GitHub] ignite pull request #2868: IGNITE 6648

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

Re: New API docs look for Ignite.NET

Great news, thanks a lot! On Tue, Sep 5, 2017 at 11:47 AM, Pavel Tupitsyn wrote: > DocFX takes around 30 seconds on my machine. > > > if you already tried that > Yes, everything is done on my side, see JIRA ticket [4] and preview [5] > above. > > On Tue, Sep 5, 2017 at

Re: [DISCUSSION] Urgent Ignite bug fix release

We created the release build procedure on Apache CI server according to this ticket: https://issues.apache.org/jira/browse/IGNITE-5249 We also changed the checksum calculation method: https://issues.apache.org/jira/browse/IGNITE-5817 Oleg On Thu, Sep 7, 2017 at 9:49 AM, 李玉珏@163

[GitHub] ignite pull request #2498: IGNITE-6155 added new jvm flag for printing gc da...

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/2498 IGNITE-6155 added new jvm flag for printing gc date stamps You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite

[GitHub] ignite pull request #2585: Ignite 6237

Github user oleg-ostanin closed the pull request at: https://github.com/apache/ignite/pull/2585 ---

[GitHub] ignite pull request #2585: Ignite 6237

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

[GitHub] ignite pull request #2586: IGNITE-6237 created script for signing and upload...

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/2586 IGNITE-6237 created script for signing and uploading artifacts to rem… …ote staging. You can merge this pull request into a Git repository by running: $ git pull https://github.com

[GitHub] ignite pull request #2590: IGNITE-5817 Changed checksum calculation methods

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/2590 IGNITE-5817 Changed checksum calculation methods (cherry picked from commit 28fb8c8) You can merge this pull request into a Git repository by running: $ git pull https://github.com

[GitHub] ignite pull request #2539: Ignite 5817 x

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/2539 Ignite 5817 x You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5817-x Alternatively you can review

[GitHub] ignite pull request #2879: IGNITE-6660 fixed Python Redis example (print sta...

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/2879 IGNITE-6660 fixed Python Redis example (print statements) You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite

[GitHub] ignite pull request #2902: IGNITE-6708 Remove ignite-compatibility from opti...

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/2902 IGNITE-6708 Remove ignite-compatibility from optional directory You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #2901: IGNITE-6706 Remove ignite-sqlline module from opt...

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/2901 IGNITE-6706 Remove ignite-sqlline module from optioanl directory You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #2911: IGNITE-6718 skipped upload sqlline and compatibil...

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/2911 IGNITE-6718 skipped upload sqlline and compatibility modules into ma… …ven central You can merge this pull request into a Git repository by running: $ git pull https://github.com

Re: Can not build from source code

I've just checked master branch (by the way it's 2.4.0-SNAPSHOT now), everything works fine on java 1.8 and maven 3.5.0. I've also cleaned maven local repo. On Mon, Nov 27, 2017 at 4:17 AM, kcmvp wrote: > I still run into the same issue > > > > -- > Sent from:

[GitHub] ignite pull request #3142: IGNITW-7093 added plugin to build test.jar to ign...

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/3142 IGNITW-7093 added plugin to build test.jar to ignite-compatibility po… …m.xml You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain

[GitHub] ignite pull request #3058: Ignite 6927

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

[GitHub] ignite pull request #2926: IGNITE-6751 skipped upload ignite-dev-utils modul...

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/2926 IGNITE-6751 skipped upload ignite-dev-utils module into maven repository You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache

[GitHub] ignite pull request #2920: IGNITE 6726

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

[GitHub] ignite pull request #4210: IGNITE-8322 changed default value for preloading ...

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/4210 IGNITE-8322 changed default value for preloading option to 'false' You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #3942: Ignite 8337

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

[GitHub] ignite pull request #4548: IGNITE-9234 fixed javadocs

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/4548 IGNITE-9234 fixed javadocs You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9234 Alternatively you can

[GitHub] ignite pull request #4323: Ignite 8322 fix

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/4323 Ignite 8322 fix You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8322-fix Alternatively you can review

[GitHub] ignite pull request #3825: IGNITE-8274 Changed invoking java in sqlline.sh

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/3825 IGNITE-8274 Changed invoking java in sqlline.sh You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8274

[GitHub] ignite pull request #3884: Ignite 8322

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

[GitHub] ignite pull request #4877: IGNITE-5534 added method to activate cluster

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/4877 IGNITE-5534 added method to activate cluster You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5534

[GitHub] ignite pull request #4812: IGNITE-9309 added runLocal

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/4812 IGNITE-9309 added runLocal You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9309-b Alternatively you can

[GitHub] ignite pull request #4811: Ignite 9492 qaoo

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/4811 Ignite 9492 qaoo You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9492-qaoo Alternatively you can review

[GitHub] ignite pull request #4824: IGNITE-9682 changed updatePartitionFullMap() meth...

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/4824 IGNITE-9682 changed updatePartitionFullMap() method to update map in … …parallel You can merge this pull request into a Git repository by running: $ git pull https://github.com

[GitHub] ignite pull request #4812: IGNITE-9309 added runLocal

Github user oleg-ostanin closed the pull request at: https://github.com/apache/ignite/pull/4812 ---

[GitHub] ignite pull request #5498: IGNITE-10403 added parent guava dependency in pom...

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/5498 IGNITE-10403 added parent guava dependency in pom.xml You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10403

[GitHub] ignite pull request #4783: Ignite 9309 a

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/4783 Ignite 9309 a You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9309-a Alternatively you can review

Add user defined attributes to all GridClient messages.

Hello, Igniters! Recently we added the possibility of sending user defined attributes from clients, and check those attributes in a custom authenticator implementation[1]. However in some cases it's not working well for GridClient because currently the attributes are only added to TOPOLOGY

Re: [DISCUSSION] Improvement in control.sh configuration.

I'm currently working on ticket https://issues.apache.org/jira/browse/IGNITE-12832 It's not exactly what had been suggested but it will allow to pass some custom properties to the client configuration and to pass parameters without length limitations using .properties file. -- Sent from:

contribution permissions

Hello Ignite Community! My name is Oleg. I want to contribute to Apache Ignite and want to start with this issue - IGNITE-12832, my JIRA username oleg-a-ostanin. Any help on this will be appreciated. Thanks!

Re: new connection event

will mean that something (or > somebody) wrong is trying to connect, possibly using a wrong port or hoping > that SSL is disabled. > > Maybe we need a simple warning. I guess we already have it, actually. Don't > we? > > Regards, > -- > Ilya Kasnacheev > > > вт, 11 авг. 20

new connection event

Hello igniters! I wonder if we can add a new event for a failed ssl connection? Considering security hazards it can be quite helpful to get notifications in case someone unauthorized is trying to connect to the cluster. I've created a small pull-request to illustrate a possible solution.

[jira] [Created] (IGNITE-4478) Part of IGNITE-4212

Oleg Ostanin created IGNITE-4478: Summary: Part of IGNITE-4212 Key: IGNITE-4478 URL: https://issues.apache.org/jira/browse/IGNITE-4478 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-4481) Part of IGNITE-4212

Oleg Ostanin created IGNITE-4481: Summary: Part of IGNITE-4212 Key: IGNITE-4481 URL: https://issues.apache.org/jira/browse/IGNITE-4481 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-4822) Editing default JVM options defined in Ignite-Yardstick property files.

Oleg Ostanin created IGNITE-4822: Summary: Editing default JVM options defined in Ignite-Yardstick property files. Key: IGNITE-4822 URL: https://issues.apache.org/jira/browse/IGNITE-4822 Project

[jira] [Created] (IGNITE-4894) Yardstick-Cassandra

Oleg Ostanin created IGNITE-4894: Summary: Yardstick-Cassandra Key: IGNITE-4894 URL: https://issues.apache.org/jira/browse/IGNITE-4894 Project: Ignite Issue Type: New Feature

[jira] [Created] (IGNITE-5740) Transactional load benchmark

Oleg Ostanin created IGNITE-5740: Summary: Transactional load benchmark Key: IGNITE-5740 URL: https://issues.apache.org/jira/browse/IGNITE-5740 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-5762) Skip deploy lgpl modules into repositiry

Oleg Ostanin created IGNITE-5762: Summary: Skip deploy lgpl modules into repositiry Key: IGNITE-5762 URL: https://issues.apache.org/jira/browse/IGNITE-5762 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-5807) Fixing signing artifacts

Oleg Ostanin created IGNITE-5807: Summary: Fixing signing artifacts Key: IGNITE-5807 URL: https://issues.apache.org/jira/browse/IGNITE-5807 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-5833) Changing maven goal from "install" to "package" for building from sources

Oleg Ostanin created IGNITE-5833: Summary: Changing maven goal from "install" to "package" for building from sources Key: IGNITE-5833 URL: https://issues.apache.org/jira/browse/IGNITE-5833

[jira] [Created] (IGNITE-5177) Failed javadoc generation for web-agent

Oleg Ostanin created IGNITE-5177: Summary: Failed javadoc generation for web-agent Key: IGNITE-5177 URL: https://issues.apache.org/jira/browse/IGNITE-5177 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-5596) Exchange time measurement

Oleg Ostanin created IGNITE-5596: Summary: Exchange time measurement Key: IGNITE-5596 URL: https://issues.apache.org/jira/browse/IGNITE-5596 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-6648) ML javadoc is missing in 2.2 binary release

Oleg Ostanin created IGNITE-6648: Summary: ML javadoc is missing in 2.2 binary release Key: IGNITE-6648 URL: https://issues.apache.org/jira/browse/IGNITE-6648 Project: Ignite Issue

[jira] [Created] (IGNITE-6192) Ignite-ML does not compile

Oleg Ostanin created IGNITE-6192: Summary: Ignite-ML does not compile Key: IGNITE-6192 URL: https://issues.apache.org/jira/browse/IGNITE-6192 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-6155) Add GC Date Stamps to yardstick gc log

Oleg Ostanin created IGNITE-6155: Summary: Add GC Date Stamps to yardstick gc log Key: IGNITE-6155 URL: https://issues.apache.org/jira/browse/IGNITE-6155 Project: Ignite Issue Type

[jira] [Created] (IGNITE-6209) Build Ignite.NET NuGet packages for Apache-Ignite release on CI

Oleg Ostanin created IGNITE-6209: Summary: Build Ignite.NET NuGet packages for Apache-Ignite release on CI Key: IGNITE-6209 URL: https://issues.apache.org/jira/browse/IGNITE-6209 Project: Ignite

[jira] [Created] (IGNITE-6237) Script for signing and uploading artifacts to remote staging.

Oleg Ostanin created IGNITE-6237: Summary: Script for signing and uploading artifacts to remote staging. Key: IGNITE-6237 URL: https://issues.apache.org/jira/browse/IGNITE-6237 Project: Ignite

[jira] [Created] (IGNITE-6718) Skip deploy sqlline and compatibility modules into repositiry

Oleg Ostanin created IGNITE-6718: Summary: Skip deploy sqlline and compatibility modules into repositiry Key: IGNITE-6718 URL: https://issues.apache.org/jira/browse/IGNITE-6718 Project: Ignite

[jira] [Created] (IGNITE-6726) Licenses for Sqlline are missing

Oleg Ostanin created IGNITE-6726: Summary: Licenses for Sqlline are missing Key: IGNITE-6726 URL: https://issues.apache.org/jira/browse/IGNITE-6726 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-6978) Failed to move temp file to a regular WAL segment file

Oleg Ostanin created IGNITE-6978: Summary: Failed to move temp file to a regular WAL segment file Key: IGNITE-6978 URL: https://issues.apache.org/jira/browse/IGNITE-6978 Project: Ignite

[jira] [Created] (IGNITE-6751) Skip upload ignite-dev-utils module into maven repository

Oleg Ostanin created IGNITE-6751: Summary: Skip upload ignite-dev-utils module into maven repository Key: IGNITE-6751 URL: https://issues.apache.org/jira/browse/IGNITE-6751 Project: Ignite

[jira] [Created] (IGNITE-7344) Fix yardstick devnotes

Oleg Ostanin created IGNITE-7344: Summary: Fix yardstick devnotes Key: IGNITE-7344 URL: https://issues.apache.org/jira/browse/IGNITE-7344 Project: Ignite Issue Type: Improvement

  1   2   >