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

2016-06-28 Thread f7753
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. `tabl

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

2016-06-28 Thread Vasiliy Sisko (JIRA)
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

[jira] [Created] (IGNITE-3393) Mvn build warning

2016-06-28 Thread lukasz gintowt (JIRA)
lukasz gintowt created IGNITE-3393: -- Summary: Mvn build warning Key: IGNITE-3393 URL: https://issues.apache.org/jira/browse/IGNITE-3393 Project: Ignite Issue Type: Bug Environment:

[jira] [Created] (IGNITE-3392) IgniteServices.deploy() method doesn't throw exception in case service initialization throws exception

2016-06-28 Thread Valentin Kulichenko (JIRA)
Valentin Kulichenko created IGNITE-3392: --- Summary: IgniteServices.deploy() method doesn't throw exception in case service initialization throws exception Key: IGNITE-3392 URL: https://issues.apache.org/jira/

Re: Fwd: TC access

2016-06-28 Thread Dmitriy Setrakyan
Anton, I think the documentation for TeamCity if well-belied and hardly noticeable. Do you mind creating a separate section for it, so everyone will know how their PR will be tested? On Tue, Jun 28, 2016 at 12:25 AM, Anton Vinogradov wrote: > Hi All, > > 1) Testing at TeamCity already documented

Re: IGNITE-3337

2016-06-28 Thread Saikat Maitra
Hello Andrey, I have updated the PR. Please review and share feedback. https://github.com/apache/ignite/pull/816 Regards Saikat On Thu, Jun 23, 2016 at 8:41 PM, Saikat Maitra wrote: > Thank you Andrey > > I will update the PR accordingly. > > Regards > Saikat > > On Thu, Jun 23, 2016 at 12:33

Re: Ignite & Kubernetes

2016-06-28 Thread Dmitriy Setrakyan
Paulo, would you like to contribute this to Ignite? On Tue, Jun 28, 2016 at 11:43 AM, Paulo Pires wrote: > I came up with https://github.com/pires/apache-ignite-discovery-kubernetes > . > > I have been using this in production Kubernetes. Obviously, one needs DNS > integration which happens to b

Re: Ignite & Kubernetes

2016-06-28 Thread Paulo Pires
I came up with https://github.com/pires/apache-ignite-discovery-kubernetes. I have been using this in production Kubernetes. Obviously, one needs DNS integration which happens to be a best-practice anyway. Pires On Thu, Apr 28, 2016 at 4:45 PM Dmitriy Setrakyan wrote: > Ignite does not have an

[jira] [Created] (IGNITE-3391) Need to be able to customize SQL table name

2016-06-28 Thread Valentin Kulichenko (JIRA)
Valentin Kulichenko created IGNITE-3391: --- Summary: Need to be able to customize SQL table name Key: IGNITE-3391 URL: https://issues.apache.org/jira/browse/IGNITE-3391 Project: Ignite Is

[GitHub] ignite pull request #837: Ignite gg 11275

2016-06-28 Thread agoncharuk
Github user agoncharuk closed the pull request at: https://github.com/apache/ignite/pull/837 --- 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 #838: IGNITE-3389 metadata result set throws NPE when cl...

2016-06-28 Thread aboudnik
GitHub user aboudnik opened a pull request: https://github.com/apache/ignite/pull/838 IGNITE-3389 metadata result set throws NPE when closed - fixed You can merge this pull request into a Git repository by running: $ git pull https://github.com/aboudnik/ignite IGNITE-3389 Alt

[GitHub] ignite pull request #837: Ignite gg 11275

2016-06-28 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/837 Ignite gg 11275 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-11275 Alternatively you can review and appl

[GitHub] ignite pull request #836: .NET: Configure PlatformAffinityFunction in Spring

2016-06-28 Thread ptupitsyn
GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/836 .NET: Configure PlatformAffinityFunction in Spring You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-3371-1.5 Alternati

[jira] [Created] (IGNITE-3390) ODBC: Add system DSN support for WIndows.

2016-06-28 Thread Igor Sapego (JIRA)
Igor Sapego created IGNITE-3390: --- Summary: ODBC: Add system DSN support for WIndows. Key: IGNITE-3390 URL: https://issues.apache.org/jira/browse/IGNITE-3390 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-3389) metadata result set throws NPE when closed

2016-06-28 Thread Alexandre Boudnik (JIRA)
Alexandre Boudnik created IGNITE-3389: - Summary: metadata result set throws NPE when closed Key: IGNITE-3389 URL: https://issues.apache.org/jira/browse/IGNITE-3389 Project: Ignite Issue T

Re: Rebalancing documentation is updated

2016-06-28 Thread Anton Vinogradov
Everything is Ok On Tue, Jun 28, 2016 at 6:44 PM, Denis Magda wrote: > Igniters, > > I’ve update Ignite’s rebalancing documentation [1] in this way: > - added the section regarding rebalance thread pool size tuning - Rebalance > Thread Pool Tuning >

Rebalancing documentation is updated

2016-06-28 Thread Denis Magda
Igniters, I’ve update Ignite’s rebalancing documentation [1] in this way: - added the section regarding rebalance thread pool size tuning - Rebalance Thread Pool Tuning - update configuration section - Configur

[jira] [Created] (IGNITE-3388) .NET: Return informational placeholders in GetConfiguration for Java objects

2016-06-28 Thread Pavel Tupitsyn (JIRA)
Pavel Tupitsyn created IGNITE-3388: -- Summary: .NET: Return informational placeholders in GetConfiguration for Java objects Key: IGNITE-3388 URL: https://issues.apache.org/jira/browse/IGNITE-3388 Proj

[jira] [Created] (IGNITE-3387) NPE deploy ignite with mesos

2016-06-28 Thread Ilya Suntsov (JIRA)
Ilya Suntsov created IGNITE-3387: Summary: NPE deploy ignite with mesos Key: IGNITE-3387 URL: https://issues.apache.org/jira/browse/IGNITE-3387 Project: Ignite Issue Type: Bug Compo

Re: Improve schema generation utility

2016-06-28 Thread Alexei Scherbakov
Hi, Alexei. I've added some thoughts to the JIRA issue. 2016-06-28 15:22 GMT+03:00 Alexey Kuznetsov : > It should be also implemented in Web Console. > > Could you add to issue description examples like: > > Db Table as input and expected generated XML and java code as output? > > This will help

Re: Improve schema generation utility

2016-06-28 Thread Alexey Kuznetsov
It should be also implemented in Web Console. Could you add to issue description examples like: Db Table as input and expected generated XML and java code as output? This will help us to implement requested features. Thanks! On Tue, Jun 28, 2016 at 7:15 PM, Alexei Scherbakov < alexey.scherbak.

[jira] [Created] (IGNITE-3386) Reentrant lock is lost when lock owner leaves topology

2016-06-28 Thread Denis Magda (JIRA)
Denis Magda created IGNITE-3386: --- Summary: Reentrant lock is lost when lock owner leaves topology Key: IGNITE-3386 URL: https://issues.apache.org/jira/browse/IGNITE-3386 Project: Ignite Issue T

Improve schema generation utility

2016-06-28 Thread Alexei Scherbakov
Guys, I think it would be useful to improve code generation capabilities of the schema import utility by allowing it to generate affinity key mapping and possibly SQL fields and indexes. This can make easier for new users to deal with Ignite's intricacies. What do you think? I've created an issu

[jira] [Created] (IGNITE-3385) Improve schema import utility

2016-06-28 Thread Alexei Scherbakov (JIRA)
Alexei Scherbakov created IGNITE-3385: - Summary: Improve schema import utility Key: IGNITE-3385 URL: https://issues.apache.org/jira/browse/IGNITE-3385 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-3384) Docker container for Ignite Web Console

2016-06-28 Thread Maxim Afanasiev (JIRA)
Maxim Afanasiev created IGNITE-3384: --- Summary: Docker container for Ignite Web Console Key: IGNITE-3384 URL: https://issues.apache.org/jira/browse/IGNITE-3384 Project: Ignite Issue Type: I

[jira] [Created] (IGNITE-3383) Hadoop: Ensure that component creation exception doesn't stop node startup if component is optional.

2016-06-28 Thread Vladimir Ozerov (JIRA)
Vladimir Ozerov created IGNITE-3383: --- Summary: Hadoop: Ensure that component creation exception doesn't stop node startup if component is optional. Key: IGNITE-3383 URL: https://issues.apache.org/jira/browse/IGN

[jira] [Created] (IGNITE-3381) IGFS: Merge RENAME handling for PRIMARY and DUAL modes.

2016-06-28 Thread Vladimir Ozerov (JIRA)
Vladimir Ozerov created IGNITE-3381: --- Summary: IGFS: Merge RENAME handling for PRIMARY and DUAL modes. Key: IGNITE-3381 URL: https://issues.apache.org/jira/browse/IGNITE-3381 Project: Ignite

[jira] [Created] (IGNITE-3382) IGFS: Merge UPDATE handling for PRIMARY and DUAL modes.

2016-06-28 Thread Vladimir Ozerov (JIRA)
Vladimir Ozerov created IGNITE-3382: --- Summary: IGFS: Merge UPDATE handling for PRIMARY and DUAL modes. Key: IGNITE-3382 URL: https://issues.apache.org/jira/browse/IGNITE-3382 Project: Ignite

[jira] [Created] (IGNITE-3379) IGFS: Merge MKDIRS handling for PRIMARY and DUAL modes.

2016-06-28 Thread Vladimir Ozerov (JIRA)
Vladimir Ozerov created IGNITE-3379: --- Summary: IGFS: Merge MKDIRS handling for PRIMARY and DUAL modes. Key: IGNITE-3379 URL: https://issues.apache.org/jira/browse/IGNITE-3379 Project: Ignite

[jira] [Created] (IGNITE-3380) IGFS: Merge OPEN handling for PRIMARY and DUAL modes.

2016-06-28 Thread Vladimir Ozerov (JIRA)
Vladimir Ozerov created IGNITE-3380: --- Summary: IGFS: Merge OPEN handling for PRIMARY and DUAL modes. Key: IGNITE-3380 URL: https://issues.apache.org/jira/browse/IGNITE-3380 Project: Ignite

[jira] [Created] (IGNITE-3378) IGFS: Merge APPEND handling for PRIMARY and DUAL modes.

2016-06-28 Thread Vladimir Ozerov (JIRA)
Vladimir Ozerov created IGNITE-3378: --- Summary: IGFS: Merge APPEND handling for PRIMARY and DUAL modes. Key: IGNITE-3378 URL: https://issues.apache.org/jira/browse/IGNITE-3378 Project: Ignite

[jira] [Created] (IGNITE-3377) IGFS: Refactor IgfsMetaManager to use the same code paths for both DUAL and PRIMARY modes.

2016-06-28 Thread Vladimir Ozerov (JIRA)
Vladimir Ozerov created IGNITE-3377: --- Summary: IGFS: Refactor IgfsMetaManager to use the same code paths for both DUAL and PRIMARY modes. Key: IGNITE-3377 URL: https://issues.apache.org/jira/browse/IGNITE-3377

[jira] [Created] (IGNITE-3376) IGFS: Allow direct PROXY mode invocations.

2016-06-28 Thread Vladimir Ozerov (JIRA)
Vladimir Ozerov created IGNITE-3376: --- Summary: IGFS: Allow direct PROXY mode invocations. Key: IGNITE-3376 URL: https://issues.apache.org/jira/browse/IGNITE-3376 Project: Ignite Issue Type:

[GitHub] ignite pull request #835: gridgain-7.5.28

2016-06-28 Thread sboikov
GitHub user sboikov opened a pull request: https://github.com/apache/ignite/pull/835 gridgain-7.5.28 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite gridgain-7.5.28 Alternatively you can review and apply t

[jira] [Created] (IGNITE-3375) Refactor legacy common-module.js to simple pieces.

2016-06-28 Thread Alexey Kuznetsov (JIRA)
Alexey Kuznetsov created IGNITE-3375: Summary: Refactor legacy common-module.js to simple pieces. Key: IGNITE-3375 URL: https://issues.apache.org/jira/browse/IGNITE-3375 Project: Ignite I

Web Console Beta 2 release

2016-06-28 Thread Alexey Kuznetsov
Igniters! I'd like to announce that we just pushed Ignite Web Console Beta 2 to master branch and deployed new version at https://console.gridgain.com NOTE: You may need to refresh page (F5 or Ctrl+R) in order to reload Web Console. What's new: - Implemented Monitoring of grid and caches (pl

Re: Fwd: TC access

2016-06-28 Thread Anton Vinogradov
Hi All, 1) Testing at TeamCity already documented here: https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-Creation 2) We cannot trigger every pullrequest testing automaticaly because it takes ~1.5 hours to test only one, but we have more than 50 commits per day a