[jira] [Created] (IGNITE-5408) JDBC driver should not require Class.forName() call

Vladimir Ozerov created IGNITE-5408: --- Summary: JDBC driver should not require Class.forName() call Key: IGNITE-5408 URL: https://issues.apache.org/jira/browse/IGNITE-5408 Project: Ignite

Persistent Store and IgniteServices

Hi guys, If persistent store feature is enabled, will IgniteServices survive cluster restrart? Thanks!

[jira] [Created] (IGNITE-5404) SQL temp table join does not work with typed arrays

Pavel Tupitsyn created IGNITE-5404: -- Summary: SQL temp table join does not work with typed arrays Key: IGNITE-5404 URL: https://issues.apache.org/jira/browse/IGNITE-5404 Project: Ignite

[jira] [Created] (IGNITE-5407) Web console: Wrong generation of marshaller on version switch

Vasiliy Sisko created IGNITE-5407: - Summary: Web console: Wrong generation of marshaller on version switch Key: IGNITE-5407 URL: https://issues.apache.org/jira/browse/IGNITE-5407 Project: Ignite

Request for contributor permissions

Hello everybody, Please give me contributor permissions. Alexey Ivanov

[jira] [Created] (IGNITE-5403) Test flakily fails

Stanilovsky Evgeny created IGNITE-5403: -- Summary: Test flakily fails Key: IGNITE-5403 URL: https://issues.apache.org/jira/browse/IGNITE-5403 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-5402) Errors related to multi-version support

Pavel Konstantinov created IGNITE-5402: -- Summary: Errors related to multi-version support Key: IGNITE-5402 URL: https://issues.apache.org/jira/browse/IGNITE-5402 Project: Ignite Issue

[jira] [Created] (IGNITE-5406) VisorExecutorConfiguration and VisroGridConfiguration should use IgniteConfiguration.sqlConnectorConfiguration insread of IgniteConfiguration.odbcConfiguration

Vladimir Ozerov created IGNITE-5406: --- Summary: VisorExecutorConfiguration and VisroGridConfiguration should use IgniteConfiguration.sqlConnectorConfiguration insread of IgniteConfiguration.odbcConfiguration Key: IGNITE-5406

[jira] [Created] (IGNITE-5405) Null values in comparator for EvictableEntry

Richa Bali created IGNITE-5405: -- Summary: Null values in comparator for EvictableEntry Key: IGNITE-5405 URL: https://issues.apache.org/jira/browse/IGNITE-5405 Project: Ignite Issue Type: Bug

[GitHub] ignite pull request #2078: Ignite gg 8.0.4.ea2 for tests

GitHub user EdShangGG opened a pull request: https://github.com/apache/ignite/pull/2078 Ignite gg 8.0.4.ea2 for tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-8.0.4.ea2 Alternatively you

[GitHub] ignite pull request #2080: IGNITE-5275

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

[GitHub] ignite pull request #2079: IGNITE-5233: JDBC thin Driver: implement metadata...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/2079 IGNITE-5233: JDBC thin Driver: implement metadata support You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: contention on DataStructure creation/removing

Hi all, Yakov pointed me that I didn't remove Reenrtrant Lock after it use. Data Structures' are stored in HashMap, so serialization and deserialization time depends on HashMap size and becomes very expensive without removing unused data structures. I added removing for unused Reenrtrant Locks

[GitHub] ignite pull request #2081: IGNITE-5379

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

[GitHub] ignite pull request #2071: IGNITE-5263: Replaced ODBC connection param "Cach...

Github user isapego closed the pull request at: https://github.com/apache/ignite/pull/2071 --- 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 is

[GitHub] ignite pull request #2057: IGNITE-5309: Added schema to SqlFieldsQuery for C...

Github user isapego closed the pull request at: https://github.com/apache/ignite/pull/2057 --- 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 is

[GitHub] ignite pull request #2080: IGNITE-5275

Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/2080 --- 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 is

"Review workflow" changes to prevent "broken review" issues.

Igniters, Currently, according to https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-SubmittingforReview , contributor can ask for review by moving ticket to PATCH AVAILABLE state. And, as far as I can see, this cause broken tickets issue. Contributor can wait

[GitHub] ignite pull request #2081: IGNITE-5379

Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/2081 --- 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 is

New version of Web Console released

Igniters! I'd like to announce that we just pushed new version of Ignite Web Console to master branch and redeployed the new version on GridGain infrastructure (https://console .gridgain.com) where you can give it a try right a way. NOTE: You may need to refresh page (F5 or Ctrl+R) in order to

Re: "Review workflow" changes to prevent "broken review" issues.

We should keep in mind that contributor do not have to do anything, as this is community. Instead, it is responsibility of the community to make sure that contributions are processed in a timely manner, and that contributors have positive experience with us. So, -1 from my side. On Mon, Jun 5,

Re: "Review workflow" changes to prevent "broken review" issues.

Hi Igniters, Anton, Let’s imagine that development process as a chain of production stages 1) Developing patch by contributor 2) Review changes by committer Reviews waiting too long time to be done at stage 2 may indicate that speed (potential throughput) of step 2 is less than throughput at

Re: Persistent Store and IgniteServices

Hi Semyon, Given that both ServiceDescriptors and service assignments are stored in the system cache, services should survive the cluster restart, but this needs to be double-checked because service assignments become obsolete and need to be fully recalculated. I will check this and give an

[GitHub] ignite pull request #2083: IGNITE-5196

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

[jira] [Created] (IGNITE-5409) JDBC thin: support schema in query string

Vladimir Ozerov created IGNITE-5409: --- Summary: JDBC thin: support schema in query string Key: IGNITE-5409 URL: https://issues.apache.org/jira/browse/IGNITE-5409 Project: Ignite Issue Type:

[GitHub] ignite pull request #2082: IGNITE-5380

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

[jira] [Created] (IGNITE-5410) Invocation of HadoopOutputStream.write() with an empty array сauses an AssertionError.

Ivan Veselovsky created IGNITE-5410: --- Summary: Invocation of HadoopOutputStream.write() with an empty array сauses an AssertionError. Key: IGNITE-5410 URL: https://issues.apache.org/jira/browse/IGNITE-5410

Re: Persistent Distributed Store Metrics

Guyd, I've extended the set of metrics a little bit and pushed my changes to ignite-5375 branch. Can you please review the metrics and see if we are now ok with the interfaces? 2017-06-01 21:04 GMT+03:00 Denis Magda : > Sergey, thanks, > > You get a green light from my side.

[GitHub] ignite pull request #2066: Ignite 3562 lucene 5.5.2

Github user AMashenkov closed the pull request at: https://github.com/apache/ignite/pull/2066 --- 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 #2067: Ignite 3562 lucene 5.5.2 new

Github user AMashenkov closed the pull request at: https://github.com/apache/ignite/pull/2067 --- 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

[jira] [Created] (IGNITE-5411) Persist affinity key on disc

Vladimir Ozerov created IGNITE-5411: --- Summary: Persist affinity key on disc Key: IGNITE-5411 URL: https://issues.apache.org/jira/browse/IGNITE-5411 Project: Ignite Issue Type: Task

Re: "Review workflow" changes to prevent "broken review" issues.

Hi Anton, It is ok for me if it is advice and hint for faster review, as it is now. We can periodically remind about this opportunity at dev list or in the issue comments. We can remind that tasks in patch available status may be reassigned by contributor. Looking from prospective of overall

Re: place for printing info about partition distribution (IGNITE-4756)

Taras, Yakov, Please join the conversation. — Denis > On Jun 4, 2017, at 3:43 AM, Вадим Опольский wrote: > > Guys, lets suggest the format for this log. > > Yakov's version is "print only nodes that differ on +/-10% from average > partitions count we can print problem

Re: "Review workflow" changes to prevent "broken review" issues.

Vova, Contributors interested to make contributions and I propose them to use *same* strategy as we (people inside the community) use. "-1" will not solve this issue, but my "tips" will. Dmitry, The main problem here is that nobody notified that someone is waiting for the review. It's not a

[GitHub] ignite pull request #2084: Ignite 5410

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

Re: Request for contributor permissions

Hello Alexey, what’s your JIRA id? — Denis > On Jun 5, 2017, at 2:04 AM, Alexey Ivanov wrote: > > Hello everybody, > > Please give me contributor permissions. > > Alexey Ivanov >

Re: "Review workflow" changes to prevent "broken review" issues.

In general, I tend to agree with Anton that something needs to be changed in this direction. How many of you flip through dev list, JIRA or GitHub notifications in an attempt to find tickets that demand your attention? I bet the percentage is pretty low. To solve this issue I see two options:

[GitHub] ignite pull request #2073: IGNITE-5355 Create task with release tools

Github user achetaev closed the pull request at: https://github.com/apache/ignite/pull/2073 --- 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 is

Re: "Review workflow" changes to prevent "broken review" issues.

By the way, there are emails being sent from Jira to devlist every time someone adds comment to ticket, or, for example, edits its title which helps a lot to keep a track of ticket's state. But by some reason there is no such notification when ticket silently getting moved to "Patch available"

Re: Lack of accounting for extremely disruptive functionality

Hi Roman! In fact, that particular issue you’re referring to was handled directly in JIRA [1] in order to address the reported CVE [2]. Now I see, that as one of the ticket reviewers, I should have initiated a broader discussion on @dev to avoid the point we came to today with the update

[GitHub] ignite pull request #2085: IGNITE-5400 .NET: IgniteConfiguration.SqlConnecto...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/2085 IGNITE-5400 .NET: IgniteConfiguration.SqlConnectorConfiguration You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-5400

[GitHub] ignite pull request #2086: Ignite 5355

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

Re: "Review workflow" changes to prevent "broken review" issues.

1) There is waiting for review list here https://cwiki.apache.org/confluence/display/IGNITE/Issues+waiting+for+review 2) some of contributions are supplemented by dev-list messages (please review my PR…) And these two tools sometimes do not help. I suppose it is because of reviewers already

[GitHub] ignite pull request #2082: IGNITE-5380

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2082 --- 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 is

[jira] [Created] (IGNITE-5413) Ignite shouldn't expose nor send (clear-text) env variables to a 3rd endpoint

Konstantin Boudnik created IGNITE-5413: -- Summary: Ignite shouldn't expose nor send (clear-text) env variables to a 3rd endpoint Key: IGNITE-5413 URL: https://issues.apache.org/jira/browse/IGNITE-5413

[GitHub] ignite pull request #2087: IGNITE-5408

Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/2087 --- 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 is

[GitHub] ignite pull request #2090: ignite-2190 fix issue

GitHub user nizhikov opened a pull request: https://github.com/apache/ignite/pull/2090 ignite-2190 fix issue Added GridCacheEmptyScanQueryTest to reproduce bug described in task Minor fixes in IgniteProcessProxy and GridAbstractTest for a possibility to modify separate jvm grid

[GitHub] ignite pull request #2086: Ignite 5355

Github user achetaev closed the pull request at: https://github.com/apache/ignite/pull/2086 --- 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 is

[GitHub] ignite pull request #2087: IGNITE-5408

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

[GitHub] ignite pull request #2088: Ignite 5355 Create release report task on TeamCit...

Github user achetaev closed the pull request at: https://github.com/apache/ignite/pull/2088 --- 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 is

[GitHub] ignite pull request #2088: Ignite 5355 Create release report task on TeamCit...

GitHub user achetaev opened a pull request: https://github.com/apache/ignite/pull/2088 Ignite 5355 Create release report task on TeamCity You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5355

CI Server permissions changed

Hi, That all users don't be admins, I changed permissions scheme on CI server (http://ci.ignite.apache.org) We have four groups: > TeamCity Admins - group for committers. Users in this group have full access permission to CI server and can add new users. > Ignite Tests Admins - groups for guys,

[jira] [Created] (IGNITE-5412) JDBC thin: review ResultSetMetadata implementation

Vladimir Ozerov created IGNITE-5412: --- Summary: JDBC thin: review ResultSetMetadata implementation Key: IGNITE-5412 URL: https://issues.apache.org/jira/browse/IGNITE-5412 Project: Ignite

Re: "Review workflow" changes to prevent "broken review" issues.

Wow, we have 66 tickets waiting for review this is pretty bad. Something must definitely change. >From my side, having a contributor shop around for a reviewer is not really fair. However, I would support the idea of Apache Ignite community electing a person responsible to find reviewers for

Re: Fwd: Persistent Distributed Store Metrics

On Mon, Jun 05, 2017 at 07:41PM, Dmitriy Setrakyan wrote: > On Mon, Jun 5, 2017 at 6:46 PM, Konstantin Boudnik wrote: > > > Wow, hold on - as far as I remember there was a VOTE to accept the > > contribution of the code into the project _on a branch_. We haven't vetted > > its >

Fwd: Persistent Distributed Store Metrics

On Mon, Jun 5, 2017 at 6:46 PM, Konstantin Boudnik wrote: > Wow, hold on - as far as I remember there was a VOTE to accept the > contribution of the code into the project _on a branch_. We haven't vetted > its > inclusion into the next release, We are still at the phase of

Re: Persistent Distributed Store Metrics

Wow, hold on - as far as I remember there was a VOTE to accept the contribution of the code into the project _on a branch_. We haven't vetted its inclusion into the next release, We are still at the phase of getting familiar with the code. And from what I am seeing in the discussions like this

Lack of accounting for extremely disruptive functionality

Hi! there's a thread about an extremely questionable practice that Apache Ignite engages in. A practice that borderlines on unsolicited data collection (and as such may even be illegal in some jurisdictions without an explicit opt-in):

[jira] [Created] (IGNITE-5414) Web Console: Model import should use unique indexes if no PK found

Alexey Kuznetsov created IGNITE-5414: Summary: Web Console: Model import should use unique indexes if no PK found Key: IGNITE-5414 URL: https://issues.apache.org/jira/browse/IGNITE-5414 Project: