Re: Create cache using thin protocol

Hi Denis, I think we can assign an id to each parameter. It is not difficult to add. > not to tell about this operation Hiding stuff is not a good approach. Any decent engineer will have a look at the server code and see it. Pavel On Fri, Dec 22, 2017 at 3:45 AM, Denis Magda

Re: Contributor permission request

Hello Anton and welcome! Added you to JIRA’s contributors list. Go ahead and take over the ticket. — Denis > On Dec 21, 2017, at 6:15 AM, dmitrievanthony > wrote: > > My JIRA username is dmitrievanthony. > > Best regards, > Anton Dmitriev > > > > -- > Sent

Re: Hello Ignite

You’re in. Feel free to assign the ticket on your account. — Denis > On Dec 21, 2017, at 1:24 AM, Stanislav Lukyanov > wrote: > > Hi Denis, > > Sorry, forgot to include that. > It’s slukyanov. > > Thanks, > Stan > > From: Denis Magda > Sent: 21 декабря 2017 г. 7:20

Re: Create cache using thin protocol

Hi Pavel, If it’s supposed to be used this way then it’s better not to tell about this operation at all until it’s simplified from a user standpoint. My suggestion would be to design the operation so that I can pass only those configuration parameters that need to be different from the

Re: Partition loss policy - how to use?

Couple more questions: - Is there any way to know which partitions in which caches are currently unavailable? - How can I check which nodes failed to trigger the data loss? The only way I see is to listen for EVT_CACHE_REBALANCE_PART_DATA_LOST event... Probably we should add something more

Ignite Committership Bar Guidance

Igniters, We at Ignite PMC put together a page with rules-of-thumb on when it’s a right time to promote a contributor to a committer: https://cwiki.apache.org/confluence/display/IGNITE/Committership+Bar+Guidance

Re: default SQL timeout

To my knowledge, it's only possible to set timeout on query level which actually can be an issue. Developers and admins do not always have full control on what is executed on the cluster and may want to set timeout on server side rather then rely on clients. Here is the ticket for this:

[jira] [Created] (IGNITE-7285) Add default query timeout

Valentin Kulichenko created IGNITE-7285: --- Summary: Add default query timeout Key: IGNITE-7285 URL: https://issues.apache.org/jira/browse/IGNITE-7285 Project: Ignite Issue Type:

Re: Time and scope for Apache Ignite 2.4

Yuri, Do you aggregate NN tasks somehow in JIRA? Want to learn more on what’s going there. — Denis > On Dec 21, 2017, at 1:39 AM, Yury Babak wrote: > > Hi Denis, > > as for ML - we on track. For this release we have FCM, Decision tree, KNN, > Model/Trainer API, Neural

Re: Suppressing "development" warning

Ticket created: https://issues.apache.org/jira/browse/IGNITE-7284 -Val On Wed, Dec 20, 2017 at 6:12 PM, Dmitriy Setrakyan wrote: > Sounds good, markers should work. > > On Wed, Dec 20, 2017 at 1:00 PM, Valentin Kulichenko < > valentin.kuliche...@gmail.com> wrote: > > >

[jira] [Created] (IGNITE-7284) Introduce DEV_ONLY marker to IgniteLogger

Valentin Kulichenko created IGNITE-7284: --- Summary: Introduce DEV_ONLY marker to IgniteLogger Key: IGNITE-7284 URL: https://issues.apache.org/jira/browse/IGNITE-7284 Project: Ignite

[GitHub] ignite pull request #3259: Ignite gg 12015m1

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

[GitHub] ignite pull request #3260: IGNITE-7197 Avoid NPE in services() by waiting on...

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

[GitHub] ignite pull request #3184: IGNITE-6729: Removed obsolete reflection-based wo...

Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/3184 ---

[GitHub] ignite pull request #3272: Ignite 1.9.10

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

[jira] [Created] (IGNITE-7283) .NET: Include all tests in DotNetCore test project

Pavel Tupitsyn created IGNITE-7283: -- Summary: .NET: Include all tests in DotNetCore test project Key: IGNITE-7283 URL: https://issues.apache.org/jira/browse/IGNITE-7283 Project: Ignite

Re: Contributor permission request

My JIRA username is dmitrievanthony. Best regards, Anton Dmitriev -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[GitHub] ignite pull request #3271: IGNITE-7279 .NET: Compile on Linux

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/3271 IGNITE-7279 .NET: Compile on Linux You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-7279 Alternatively you can

Contributor permission request

Hi, my name is Anton Dmitriev. I'd like to contribute into your project into "ml" module. I'd like to start with task 5217 . This task was suggested for me by Yuri Babak. Best regards, Anton Dmitriev -- Sent from:

[GitHub] ignite pull request #3270: Affinity reassignment if PRIMARY node isn't OWNER

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/3270 Affinity reassignment if PRIMARY node isn't OWNER You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-13223

[jira] [Created] (IGNITE-7282) .NET: Thin client: Failover

Pavel Tupitsyn created IGNITE-7282: -- Summary: .NET: Thin client: Failover Key: IGNITE-7282 URL: https://issues.apache.org/jira/browse/IGNITE-7282 Project: Ignite Issue Type: Improvement

Re: Transaction classes naming

Completely agree. Also locks acquisition related futures should be renamed. On Thu, Dec 21, 2017 at 8:21 AM, ALEKSEY KUZNETSOV wrote: > > for renaming +1 > >> 21 дек. 2017 г., в 5:25, Dmitriy Setrakyan >> написал(а): >> >> Will this renaming

[jira] [Created] (IGNITE-7281) .NET: Services do not work on .NET Core

Pavel Tupitsyn created IGNITE-7281: -- Summary: .NET: Services do not work on .NET Core Key: IGNITE-7281 URL: https://issues.apache.org/jira/browse/IGNITE-7281 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-7280) SQL TX: improve JDBC test coverage

Vladimir Ozerov created IGNITE-7280: --- Summary: SQL TX: improve JDBC test coverage Key: IGNITE-7280 URL: https://issues.apache.org/jira/browse/IGNITE-7280 Project: Ignite Issue Type: Bug

[GitHub] ignite pull request #3269: IGNITE-6732: Preventing Hadoop module from start ...

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/3269 IGNITE-6732: Preventing Hadoop module from start on Java >= 9. You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #3268: IGNITE-7217: Add abilities to monitor custom thre...

GitHub user slukyano opened a pull request: https://github.com/apache/ignite/pull/3268 IGNITE-7217: Add abilities to monitor custom thread pools Added logging and MX beans for custom executors (plus simple tests for availability of other MX beans). You can merge this pull request

[GitHub] ignite pull request #3267: IGNITE-6951 .NET: Support pointer serialization

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

[jira] [Created] (IGNITE-7279) .NET: Compile on Linux

Pavel Tupitsyn created IGNITE-7279: -- Summary: .NET: Compile on Linux Key: IGNITE-7279 URL: https://issues.apache.org/jira/browse/IGNITE-7279 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-7278) Node failed to recover partition from WAL on unstable topology.

Andrew Mashenkov created IGNITE-7278: Summary: Node failed to recover partition from WAL on unstable topology. Key: IGNITE-7278 URL: https://issues.apache.org/jira/browse/IGNITE-7278 Project:

[jira] [Created] (IGNITE-7277) JDBC thin driver may list table name twice.

Vyacheslav Koptilin created IGNITE-7277: --- Summary: JDBC thin driver may list table name twice. Key: IGNITE-7277 URL: https://issues.apache.org/jira/browse/IGNITE-7277 Project: Ignite

[GitHub] ignite pull request #3263: IGNITE-6615 .NET: Thin client: XML configuration

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

Re: List of running Continuous queries or CacheEntryListener per cache or node

Hello, Dmitry. I think it a great idea. Do we a feature to list all running ComputeTasks? I, personally, think we have to implement possibility to track all user-provided tasks - CacheListener, ContinuousQuery, ComputeTasks, etc. В Чт, 21/12/2017 в 10:13 +0300, Dmitry Karachentsev пишет: >

[jira] [Created] (IGNITE-7276) .NET: Enable/disable cache statistics in runtime

Pavel Tupitsyn created IGNITE-7276: -- Summary: .NET: Enable/disable cache statistics in runtime Key: IGNITE-7276 URL: https://issues.apache.org/jira/browse/IGNITE-7276 Project: Ignite Issue

Re: Time and scope for Apache Ignite 2.4

Hi Denis, as for ML - we on track. For this release we have FCM, Decision tree, KNN, Model/Trainer API, Neural Network introduction and bunch of improvements and bugfixes. Also we slightly change our plan for NN. In this release we will add distributed(and local) MLP(multilayer perceptron)

RE: Hello Ignite

Hi Denis, Sorry, forgot to include that. It’s slukyanov. Thanks, Stan From: Denis Magda Sent: 21 декабря 2017 г. 7:20 To: dev@ignite.apache.org Subject: Re: Hello Ignite Hi Stan, Please tell me your JIRA id and I’ll add you to the contributors list. Get familiar with Ignite development