Re: Web Console Beta 2 release

Just checked it out, looks awesome! Very nice and easy way to configure, manage, and query Ignite clusters. On Tue, Jun 28, 2016 at 1:41 AM, Alexey Kuznetsov wrote: > Igniters! > > I'd like to announce that we just pushed Ignite Web Console Beta 2 to > master branch and

Re: great ticket for a newbie

My username is my email: bryan.a.karlov...@gmail.com Looking forward to it :) Bryan On Wed, Jun 29, 2016 at 8:17 PM, Dmitriy Setrakyan wrote: > Hi Bryan, > > Welcome to the Ignite community! > > Please familiarize yourself with Ignite development process: >

Re: great ticket for a newbie

Hi Bryan, Welcome to the Ignite community! Please familiarize yourself with Ignite development process: https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute Also, please let us know your Apache Jira username, so we could add you to the list of Ignite contributors. This way you

Re: great ticket for a newbie

Hello. My name is Bryan. I'm a software engineer based in Chicago. I haven't contributed to Ignite before, and I'd love to start with this ticket. Thanks. On Wed, Jun 29, 2016 at 6:58 PM, Dmitriy Setrakyan wrote: > I believe this is an absolutely great ticket to get

great ticket for a newbie

I believe this is an absolutely great ticket to get started with Ignite: https://issues.apache.org/jira/browse/IGNITE-3399 On top of being a great way to get started with the project, it will also significantly enhance SQL querying support when used with binary protocol. Hope someone in the

[jira] [Created] (IGNITE-3399) Support primitive type names in QueryEntity

Alexey Goncharuk created IGNITE-3399: Summary: Support primitive type names in QueryEntity Key: IGNITE-3399 URL: https://issues.apache.org/jira/browse/IGNITE-3399 Project: Ignite Issue

[jira] [Created] (IGNITE-3398) .NET: Allow extending predefined Affinity Functions

Pavel Tupitsyn created IGNITE-3398: -- Summary: .NET: Allow extending predefined Affinity Functions Key: IGNITE-3398 URL: https://issues.apache.org/jira/browse/IGNITE-3398 Project: Ignite

Re: IGNITE-3337

Thank you Andrey!! Saikat On Wed, Jun 29, 2016 at 4:49 PM, Andrey Novikov wrote: > Hi Saikat! > > I’ve just reviewed and merged your pull request. > > Thank you for your contribution! > > — > Andrey > > On Wed, Jun 29, 2016 at 3:25 AM, Saikat Maitra

[GitHub] ignite pull request #840: IGNITE-3329 .NET: Fix TestDeployNodeSingleton test...

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/840 --- 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 #841: Ignite 1088 H2 based cache store for multi JVM tes...

GitHub user alexpaschenko opened a pull request: https://github.com/apache/ignite/pull/841 Ignite 1088 H2 based cache store for multi JVM tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-1088

[jira] [Created] (IGNITE-3397) CLONE - Aggregation query with where clause failed

Sergey Kozlov created IGNITE-3397: - Summary: CLONE - Aggregation query with where clause failed Key: IGNITE-3397 URL: https://issues.apache.org/jira/browse/IGNITE-3397 Project: Ignite Issue

[jira] [Created] (IGNITE-3396) Aggregation query with where clase failed

Sergey Kozlov created IGNITE-3396: - Summary: Aggregation query with where clase failed Key: IGNITE-3396 URL: https://issues.apache.org/jira/browse/IGNITE-3396 Project: Ignite Issue Type: Bug

Re: IGNITE-3337

Hi Saikat! I’ve just reviewed and merged your pull request. Thank you for your contribution! — Andrey On Wed, Jun 29, 2016 at 3:25 AM, Saikat Maitra wrote: > Hello Andrey, > > I have updated the PR. Please review and share feedback. > >

[GitHub] ignite pull request #816: IGNITE-3337 REST HTTP: metadata command returns al...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/816 --- 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-3395) .NET: TestPutGetAsyncMultithreaded failure

Pavel Tupitsyn created IGNITE-3395: -- Summary: .NET: TestPutGetAsyncMultithreaded failure Key: IGNITE-3395 URL: https://issues.apache.org/jira/browse/IGNITE-3395 Project: Ignite Issue Type:

[GitHub] ignite pull request #840: IGNITE-3329 .NET: Fix TestDeployNodeSingleton test...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/840 IGNITE-3329 .NET: Fix TestDeployNodeSingleton test failures You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-3329

[GitHub] ignite pull request #836: IGNITE-3371 .NET: Configure PlatformAffinityFuncti...

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/836 --- 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: Fwd: TC access

Alexey, I've fixed adress. Seems, you have good vision how to describe TeamCity usage, could you pleae create it? On Wed, Jun 29, 2016 at 10:56 AM, Alexey Kuznetsov wrote: > Anton, > > I noticed that wiki page > >

Re: Fwd: TC access

Anton, I noticed that wiki page https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-Creation refers to TC by IP and not by name http://ci.ignite.apache.org And I also agree with Dima - we could have a special paragraph on that page about TC. In current version

Re: Fwd: TC access

Dmitriy, TeamCity usage is a part of contribution process. The only reason for contributor to use TeamCity is to check pull-request. Thats why TeamCity usage explained at " Create GitHub pull-request -> Creation" section. On Wed, Jun 29, 2016 at 12:46 AM, Dmitriy Setrakyan

[GitHub] ignite pull request #839: IGNITE-3391 add param tableName for queryEntity

GitHub user f7753 opened a pull request: https://github.com/apache/ignite/pull/839 IGNITE-3391 add param tableName for queryEntity Currently the SQL table name is always the same as class name. In some cases user may want to override this and use different name in queries.

[jira] [Created] (IGNITE-3394) Failed to load data from Oracle DB with type TIMESTAMP(6)

Vasiliy Sisko created IGNITE-3394: - Summary: Failed to load data from Oracle DB with type TIMESTAMP(6) Key: IGNITE-3394 URL: https://issues.apache.org/jira/browse/IGNITE-3394 Project: Ignite