[jira] [Created] (IGNITE-3986) Web console: Wrong defaults in special case

Vasiliy Sisko created IGNITE-3986: - Summary: Web console: Wrong defaults in special case Key: IGNITE-3986 URL: https://issues.apache.org/jira/browse/IGNITE-3986 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-3985) Web Console: Refactor test database init in backend tests.

Andrey Novikov created IGNITE-3985: -- Summary: Web Console: Refactor test database init in backend tests. Key: IGNITE-3985 URL: https://issues.apache.org/jira/browse/IGNITE-3985 Project: Ignite

[jira] [Created] (IGNITE-3984) NullPointerException in IgniteCacheProxy when creating continuous query

Jason Man created IGNITE-3984: - Summary: NullPointerException in IgniteCacheProxy when creating continuous query Key: IGNITE-3984 URL: https://issues.apache.org/jira/browse/IGNITE-3984 Project: Ignite

Re: Default hash code generation strategy for new binary objects

Agree with Denis. - by default, all non-transient key fields should participate in the hashcode generation - when working on DDL, then the primary key fields should participate in the hashcode - we should add a resolver to override the default behavior (please propose the

Re: Default hash code generation strategy for new binary objects

Hi Alexander, Vladimir’s proposal sounds reasonable to me. However we must keep in mind one important thing. Binary objects were designed to address the following disadvantages a regular serializer, like optimized marshaller, has: necessity to deserialize an object on a server side every time

[jira] [Created] (IGNITE-3983) CacheBinaryAutoStoreExample get wrong result

Vasilisa Sidorova created IGNITE-3983: -- Summary: CacheBinaryAutoStoreExample get wrong result Key: IGNITE-3983 URL: https://issues.apache.org/jira/browse/IGNITE-3983 Project: Ignite

Adding Thrift binary protocol

Dear community, i was redirected from the users list, ofcourse, with the following: i am looking for a way to make Ignite work in a polyglot software enviroment using Apache Thrift as equalizer. The additional ReST client is a give away, but i would like to have tcp/ip level access to avoid http

[jira] [Created] (IGNITE-3982) ODBC: Add documentation for added connection string attributes and features.

Igor Sapego created IGNITE-3982: --- Summary: ODBC: Add documentation for added connection string attributes and features. Key: IGNITE-3982 URL: https://issues.apache.org/jira/browse/IGNITE-3982 Project:

[GitHub] ignite pull request #1126: IGNITE-3868: Fix for Tableau connect using DSN.

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/1126 IGNITE-3868: Fix for Tableau connect using DSN. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3868

[GitHub] ignite pull request #1125: IGNITE-3280 .NET: Log4net integration

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/1125 IGNITE-3280 .NET: Log4net integration You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-3280 Alternatively you can

[jira] [Created] (IGNITE-3981) GridTestProperties should be test instance member.

Vladimir Ozerov created IGNITE-3981: --- Summary: GridTestProperties should be test instance member. Key: IGNITE-3981 URL: https://issues.apache.org/jira/browse/IGNITE-3981 Project: Ignite

[jira] [Created] (IGNITE-3980) Process failing Binary Object Queries tests.

Vladimir Ozerov created IGNITE-3980: --- Summary: Process failing Binary Object Queries tests. Key: IGNITE-3980 URL: https://issues.apache.org/jira/browse/IGNITE-3980 Project: Ignite Issue

Re: Merge small test suites into one big suite.

Correct, 1+ minute seems to be a problem. We can add special TC suite which will compile sources and use it as dependency for each another TC suite. It can be more suitable than combine suites. On Tue, Sep 27, 2016 at 4:33 PM, Vladimir Ozerov wrote: > Anton, > > What

[GitHub] ignite pull request #1123: Ignite 3978

Github user devozerov closed the pull request at: https://github.com/apache/ignite/pull/1123 --- 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: Merge small test suites into one big suite.

Anton, What metrics do you need? Most probably everything already can be found in logs. E.g.: http://172.25.1.150:8111/viewLog.html?buildId=323412=IgniteTests_Gce=buildLog#_focus=2450 Highlights: - p2p stuff build took 40s - ignite-core took ~1m to compile On Tue, Sep 27, 2016 at 4:30 PM,

Re: Merge small test suites into one big suite.

Guys, lets continue discussion after we gain metrics. Simplest check is to create accumulated TC task (which will run all test suites) and check how fast is it. On Tue, Sep 27, 2016 at 4:09 PM, Alexey Kuznetsov wrote: > I see following possible ways of optimize

Re: Merge small test suites into one big suite.

I see following possible ways of optimize compilation: 1. Build ALL once and after that run tests (may be complicated to implement). 2. We could tune test compilation steps by specifying only needed modules in maven command. If we running test for ignite-core, lets compile only ignite-core and

[GitHub] ignite pull request #1124: IGNITE-3873: Added configs for WiX to generate OD...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/1124 IGNITE-3873: Added configs for WiX to generate ODBC installers. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: Merge small test suites into one big suite.

+1 for reusing built binaries. * Even minimal Java build (with excluded Scala, Javadoc, etc) takes over 5 minutes * There are almost 100 suites currently So we waste around 1 hour of agents time for each full TC run. Joining small suites also makes sense, even with reused binaries, because of

Re: Merge small test suites into one big suite.

First of all we should undestand how many time we spend on compilation. Im not sure that compilation required for test takes more than 20 secons. Even minimal Java build (with excluded Scala, Javadoc, etc) takes over 5 Don't mix up project build and compilation required for tests. But I see

[GitHub] ignite pull request #1123: Ignite 3978

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

[jira] [Created] (IGNITE-3979) .NET: Reorganize test suites

Pavel Tupitsyn created IGNITE-3979: -- Summary: .NET: Reorganize test suites Key: IGNITE-3979 URL: https://issues.apache.org/jira/browse/IGNITE-3979 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-3978) Process failing AWS tests.

Vladimir Ozerov created IGNITE-3978: --- Summary: Process failing AWS tests. Key: IGNITE-3978 URL: https://issues.apache.org/jira/browse/IGNITE-3978 Project: Ignite Issue Type: Sub-task

Re: Merge small test suites into one big suite.

I would merge them only if they ALL are "green". or May be better solution - build ONCE and REUSE binaries for test? On Tue, Sep 27, 2016 at 7:25 PM, Vladimir Ozerov wrote: > Igniters, > > Currently we have about 60-70 test suites on Team City. When I look at > results

Merge small test suites into one big suite.

Igniters, Currently we have about 60-70 test suites on Team City. When I look at results I see this: Ignite 150 Clients -> 1 test -> 6m Ignite AWS -> 10 tests -> 11m Ignite GCE -> 1 test -> 3m Ignite Geospacial Indexing -> 11 tests -> 4m Ignite IGFS Examples -> 1 test -> 3m Ignite Logging -> 1

[jira] [Created] (IGNITE-3977) Process failing OSGI tests.

Vladimir Ozerov created IGNITE-3977: --- Summary: Process failing OSGI tests. Key: IGNITE-3977 URL: https://issues.apache.org/jira/browse/IGNITE-3977 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-3976) Process failing SPI tests.

Vladimir Ozerov created IGNITE-3976: --- Summary: Process failing SPI tests. Key: IGNITE-3976 URL: https://issues.apache.org/jira/browse/IGNITE-3976 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-3975) Process failing streamer tests.

Vladimir Ozerov created IGNITE-3975: --- Summary: Process failing streamer tests. Key: IGNITE-3975 URL: https://issues.apache.org/jira/browse/IGNITE-3975 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-3974) Process failing ZooKeeper tests.

Vladimir Ozerov created IGNITE-3974: --- Summary: Process failing ZooKeeper tests. Key: IGNITE-3974 URL: https://issues.apache.org/jira/browse/IGNITE-3974 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-3973) Nodes can form separate clusters with TcpDiscoveryMulticastIpFinder

Semen Boikov created IGNITE-3973: Summary: Nodes can form separate clusters with TcpDiscoveryMulticastIpFinder Key: IGNITE-3973 URL: https://issues.apache.org/jira/browse/IGNITE-3973 Project: Ignite

[jira] [Created] (IGNITE-3972) Continuous query events could be lost on backup node when primary leaves.

Vladimir Ozerov created IGNITE-3972: --- Summary: Continuous query events could be lost on backup node when primary leaves. Key: IGNITE-3972 URL: https://issues.apache.org/jira/browse/IGNITE-3972

[GitHub] ignite pull request #1122: IGNITE-3957: clear swap space when cache is destr...

GitHub user amartianov opened a pull request: https://github.com/apache/ignite/pull/1122 IGNITE-3957: clear swap space when cache is destroyed You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3957

[GitHub] ignite pull request #1121: Ignite 3597 1

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

[jira] [Created] (IGNITE-3971) Web console: Add links to documentaiton on section tooltips

Vasiliy Sisko created IGNITE-3971: - Summary: Web console: Add links to documentaiton on section tooltips Key: IGNITE-3971 URL: https://issues.apache.org/jira/browse/IGNITE-3971 Project: Ignite

[GitHub] ignite pull request #1120: ignite-1.7.2

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

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

[jira] [Created] (IGNITE-3970) .NET: Cyrillic 'C' letter in code

Pavel Tupitsyn created IGNITE-3970: -- Summary: .NET: Cyrillic 'C' letter in code Key: IGNITE-3970 URL: https://issues.apache.org/jira/browse/IGNITE-3970 Project: Ignite Issue Type: Bug

[GitHub] ignite pull request #1119: GG-11547 - RWLock tags

GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/1119 GG-11547 - RWLock tags You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-11547 Alternatively you can review

[GitHub] ignite pull request #1118: Ignite 3235

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

[jira] [Created] (IGNITE-3969) Hadoop: Add installation instructions for MapR to readme.io.

Vladimir Ozerov created IGNITE-3969: --- Summary: Hadoop: Add installation instructions for MapR to readme.io. Key: IGNITE-3969 URL: https://issues.apache.org/jira/browse/IGNITE-3969 Project: Ignite