[jira] [Resolved] (IGNITE-2390) IGFS path modes are not honored

[ https://issues.apache.org/jira/browse/IGNITE-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda resolved IGNITE-2390. - Resolution: Won't Fix That was a misprint in the documentation. Closing the ticket. > IGFS path

[jira] [Closed] (IGNITE-2390) IGFS path modes are not honored

[ https://issues.apache.org/jira/browse/IGNITE-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda closed IGNITE-2390. --- > IGFS path modes are not honored > --- > > Key: IGNITE-2390

[jira] [Closed] (IGNITE-2381) Move Indexed key-value pairs from Cache Screen to Metadata Screen

[ https://issues.apache.org/jira/browse/IGNITE-2381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-2381. -- Assignee: (was: Pavel Konstantinov) Tested. > Move Indexed key-value pairs from

[jira] [Commented] (IGNITE-2380) .NET: Ignite configuration in app.config and web.config

[ https://issues.apache.org/jira/browse/IGNITE-2380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101709#comment-15101709 ] Pavel Tupitsyn commented on IGNITE-2380: TODO: * How to represent and serialize

[jira] [Resolved] (IGNITE-2386) affinityCall() execution hangs

[ https://issues.apache.org/jira/browse/IGNITE-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov resolved IGNITE-2386. -- Resolution: Fixed Hang was possible in scenario: - two nodes (or two threads) try to create

[jira] [Created] (IGNITE-2393) Set appropriate DB dialect for caches created during importing metadata from DB

Pavel Konstantinov created IGNITE-2393: -- Summary: Set appropriate DB dialect for caches created during importing metadata from DB Key: IGNITE-2393 URL: https://issues.apache.org/jira/browse/IGNITE-2393

[jira] [Commented] (IGNITE-2080) JVM crashes on Solaris (SPARC V9 arch) with SIGBUS (0xa) on frame [libjvm.so+0xc7c438] Unsafe_SetInt+0x14c

[ https://issues.apache.org/jira/browse/IGNITE-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101712#comment-15101712 ] Andrey Gura commented on IGNITE-2080: - TC looks good. Please, review. > JVM crashes on Solaris

[jira] [Updated] (IGNITE-2380) .NET: Ignite configuration in app.config and web.config

[ https://issues.apache.org/jira/browse/IGNITE-2380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-2380: --- Description: * Define custom ConfigurationSection for IgniteConfiguration (see

[jira] [Commented] (IGNITE-1993) JDBC discovery uses non-standard SQL when creating table (not compatible with Oracle)

[ https://issues.apache.org/jira/browse/IGNITE-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101722#comment-15101722 ] Nigel Westbury commented on IGNITE-1993: The branch has been updated so the code now protects

[jira] [Commented] (IGNITE-2379) .NET: ASP.NET Output Cache provider

[ https://issues.apache.org/jira/browse/IGNITE-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101632#comment-15101632 ] ASF GitHub Bot commented on IGNITE-2379: GitHub user ptupitsyn opened a pull request:

[jira] [Commented] (IGNITE-2379) .NET: ASP.NET Output Cache provider

[ https://issues.apache.org/jira/browse/IGNITE-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101652#comment-15101652 ] Pavel Tupitsyn commented on IGNITE-2379: OutputCacheProvider is set in web.config. For now, it is

[jira] [Issue Comment Deleted] (IGNITE-2379) .NET: ASP.NET Output Cache provider

[ https://issues.apache.org/jira/browse/IGNITE-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-2379: --- Comment: was deleted (was: OutputCacheProvider is set in web.config. Need to figure out the

[jira] [Updated] (IGNITE-2380) .NET: Ignite configuration in app.config and web.config

[ https://issues.apache.org/jira/browse/IGNITE-2380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-2380: --- Fix Version/s: 1.6 > .NET: Ignite configuration in app.config and web.config >

[jira] [Assigned] (IGNITE-2380) .NET: Ignite configuration in app.config and web.config

[ https://issues.apache.org/jira/browse/IGNITE-2380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn reassigned IGNITE-2380: -- Assignee: Pavel Tupitsyn > .NET: Ignite configuration in app.config and web.config >

[jira] [Closed] (IGNITE-2392) Do not generate 'cacheConfiguration' for client in case if cluster has no caches but has IGFS

[ https://issues.apache.org/jira/browse/IGNITE-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-2392. -- Assignee: (was: Pavel Konstantinov) Tested > Do not generate 'cacheConfiguration'

[jira] [Comment Edited] (IGNITE-2379) .NET: ASP.NET Output Cache provider

[ https://issues.apache.org/jira/browse/IGNITE-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101652#comment-15101652 ] Pavel Tupitsyn edited comment on IGNITE-2379 at 1/15/16 11:20 AM: --

[jira] [Commented] (IGNITE-429) Implement IgniteStormStreamer to stream data from Apache Storm

[ https://issues.apache.org/jira/browse/IGNITE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101666#comment-15101666 ] Anton Vinogradov commented on IGNITE-429: - Roman, I've updated 'Streamers' & created empty

[jira] [Updated] (IGNITE-2394) Cache loading from storage is called on client nodes

[ https://issues.apache.org/jira/browse/IGNITE-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-2394: Labels: newbie (was: ) > Cache loading from storage is called on client nodes >

[jira] [Created] (IGNITE-2394) Cache loading from storage is called on client nodes

Denis Magda created IGNITE-2394: --- Summary: Cache loading from storage is called on client nodes Key: IGNITE-2394 URL: https://issues.apache.org/jira/browse/IGNITE-2394 Project: Ignite Issue

[jira] [Commented] (IGNITE-2395) Binary marshaller: id mapper must be resolved according to configuration.

[ https://issues.apache.org/jira/browse/IGNITE-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101833#comment-15101833 ] Artem Shutak commented on IGNITE-2395: -- There is a *workaround*. The following BinaryConfiguration

[jira] [Commented] (IGNITE-429) Implement IgniteStormStreamer to stream data from Apache Storm

[ https://issues.apache.org/jira/browse/IGNITE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101796#comment-15101796 ] Roman Shtykh commented on IGNITE-429: - Anton, Thanks a lot! I will probably be able to suggest the

[jira] [Commented] (IGNITE-2395) Binary marshaller: id mapper must be resolved according to configuration.

[ https://issues.apache.org/jira/browse/IGNITE-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101869#comment-15101869 ] Artem Shutak commented on IGNITE-2395: -- How to resolve id mapper according configuration (code

[jira] [Created] (IGNITE-2395) Binary marshaller: id mapper must be resolved according to configuration.

Artem Shutak created IGNITE-2395: Summary: Binary marshaller: id mapper must be resolved according to configuration. Key: IGNITE-2395 URL: https://issues.apache.org/jira/browse/IGNITE-2395 Project:

[jira] [Commented] (IGNITE-2395) Binary marshaller: id mapper must be resolved according to configuration.

[ https://issues.apache.org/jira/browse/IGNITE-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101943#comment-15101943 ] Artem Shutak commented on IGNITE-2395: -- Note. In bounds of the issue all usages of

[jira] [Commented] (IGNITE-1993) JDBC discovery uses non-standard SQL when creating table (not compatible with Oracle)

[ https://issues.apache.org/jira/browse/IGNITE-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15102128#comment-15102128 ] Nikolay Tikhonov commented on IGNITE-1993: -- Hi, Nigel! I checked your changes on Oracle and H2

[jira] [Commented] (IGNITE-1605) Provide stronger data loss check

[ https://issues.apache.org/jira/browse/IGNITE-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15102081#comment-15102081 ] ASF GitHub Bot commented on IGNITE-1605: GitHub user VladimirErshov opened a pull request:

[jira] [Comment Edited] (IGNITE-2395) Binary marshaller: id mapper must be resolved according to configuration.

[ https://issues.apache.org/jira/browse/IGNITE-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101869#comment-15101869 ] Artem Shutak edited comment on IGNITE-2395 at 1/15/16 3:43 PM: --- How to

[jira] [Commented] (IGNITE-2191) Binary marshaller: support user classes with the same simple name

[ https://issues.apache.org/jira/browse/IGNITE-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15102273#comment-15102273 ] Artem Shutak commented on IGNITE-2191: -- Reverted fix for the bug described above. Created a separate

[jira] [Commented] (IGNITE-2394) Cache loading from storage is called on client nodes

[ https://issues.apache.org/jira/browse/IGNITE-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15102489#comment-15102489 ] Valentin Kulichenko commented on IGNITE-2394: - Described solution will break data loading for

[jira] [Updated] (IGNITE-2394) Cache loading from storage is called on client nodes

[ https://issues.apache.org/jira/browse/IGNITE-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko updated IGNITE-2394: Attachment: LocalLoadTest.java > Cache loading from storage is called on client

[jira] [Created] (IGNITE-2392) Do not generate 'cacheConfiguration' for client in case if cluster has no caches but has IGFS

Pavel Konstantinov created IGNITE-2392: -- Summary: Do not generate 'cacheConfiguration' for client in case if cluster has no caches but has IGFS Key: IGNITE-2392 URL:

[jira] [Updated] (IGNITE-2391) IGFS + Ignite MR works slower than Hadoop (Hortonswork) MR

[ https://issues.apache.org/jira/browse/IGNITE-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-2391: Labels: important (was: ) > IGFS + Ignite MR works slower than Hadoop (Hortonswork) MR >

[jira] [Reopened] (IGNITE-2370) Validation of cache's data sorces with the same name

[ https://issues.apache.org/jira/browse/IGNITE-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov reopened IGNITE-2370: Assignee: Alexey Kuznetsov (was: Pavel Konstantinov) I think the current

[jira] [Closed] (IGNITE-2099) Binary marshaller writes any map as a HashMap

[ https://issues.apache.org/jira/browse/IGNITE-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk closed IGNITE-2099. Assignee: Alexey Goncharuk (was: Vladimir Ozerov) > Binary marshaller writes any map as a

[jira] [Closed] (IGNITE-2365) Cache inconsistency: concurrent preloading from a storage when OFF HEAP is used

[ https://issues.apache.org/jira/browse/IGNITE-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk closed IGNITE-2365. The issue was fixed in master by the commit 02dbcfd8ed2701a4f415c8871d0b8fd08bfa0583 > Cache

[jira] [Updated] (IGNITE-2391) IGFS + Ignite MR works slower than Hadoop (Hortonswork) MR

[ https://issues.apache.org/jira/browse/IGNITE-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-2391: Description: A performance test of IGFS MR vs Traditional HDFS (Hortonswork) MR and performance

[jira] [Created] (IGNITE-2391) IGFS + Ignite MR works slower than Hadoop (Hortonswork) MR

Denis Magda created IGNITE-2391: --- Summary: IGFS + Ignite MR works slower than Hadoop (Hortonswork) MR Key: IGNITE-2391 URL: https://issues.apache.org/jira/browse/IGNITE-2391 Project: Ignite

[jira] [Closed] (IGNITE-2328) Object class is lost after cache.get if object implements Map

[ https://issues.apache.org/jira/browse/IGNITE-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk closed IGNITE-2328. > Object class is lost after cache.get if object implements Map >

[jira] [Closed] (IGNITE-2032) Filters passed to ScanQuery are not redeployed when originating from a client node

[ https://issues.apache.org/jira/browse/IGNITE-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk closed IGNITE-2032. > Filters passed to ScanQuery are not redeployed when originating from a client > node >

[jira] [Commented] (IGNITE-2391) IGFS + Ignite MR works slower than Hadoop (Hortonswork) MR

[ https://issues.apache.org/jira/browse/IGNITE-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101469#comment-15101469 ] Denis Magda commented on IGNITE-2391: - Lets start reproducing the issue in the following way: -

[jira] [Updated] (IGNITE-2391) IGFS + Ignite MR works slower than Hadoop (Hortonswork) MR

[ https://issues.apache.org/jira/browse/IGNITE-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-2391: Assignee: Ivan Veselovsky > IGFS + Ignite MR works slower than Hadoop (Hortonswork) MR >

[jira] [Resolved] (IGNITE-2392) Do not generate 'cacheConfiguration' for client in case if cluster has no caches but has IGFS

[ https://issues.apache.org/jira/browse/IGNITE-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko resolved IGNITE-2392. --- Resolution: Fixed Assignee: Pavel Konstantinov (was: Vasiliy Sisko) Fixed > Do not

[jira] [Commented] (IGNITE-2391) IGFS + Ignite MR works slower than Hadoop (Hortonswork) MR

[ https://issues.apache.org/jira/browse/IGNITE-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101542#comment-15101542 ] Denis Magda commented on IGNITE-2391: - Attaching ignite node config that was used during the test. >

[jira] [Updated] (IGNITE-2391) IGFS + Ignite MR works slower than Hadoop (Hortonswork) MR

[ https://issues.apache.org/jira/browse/IGNITE-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-2391: Attachment: default-config.xml > IGFS + Ignite MR works slower than Hadoop (Hortonswork) MR >