[jira] [Updated] (IGNITE-1419) .Net: Add optional "raw" flag to binary type configuration.

[Pavel Tupitsyn (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn updated IGNITE-1419:
---
Summary: .Net: Add optional "raw" flag to binary type configuration.  (was: 
.Net: Add optional "raw" flag to portable type descriptor.)

> .Net: Add optional "raw" flag to binary type configuration.
> ---
>
> Key: IGNITE-1419
> URL: https://issues.apache.org/jira/browse/IGNITE-1419
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
>
> By default we write .Net objects with field names included. But in some cases 
> it is not needed. E.g. when objects are not going to be used in queries.
> Removing field names will speed up serialization/deserialization. We can add 
> optional "raw" flag to portable type descriptor to control this behavior.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2278) Rework all tooltips - add bullets where multilines text

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-2278:


 Summary: Rework all tooltips - add bullets where multilines text
 Key: IGNITE-2278
 URL: https://issues.apache.org/jira/browse/IGNITE-2278
 Project: Ignite
  Issue Type: Sub-task
Reporter: Alexey Kuznetsov


We need to add bullets in tooltips where it make sense for better usability.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2276) Remove --test-drive from agent, agent readme, console UI dialogs

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov updated IGNITE-2276:
-
Description: 
As we now can start test drive directly from web console lets remove 
--test-drive options from agent, agent readme and from load metadata / sql 
dialogs.

Rename in web console test drive to "start demo"

Fix agent start sql demo from web console + add cancel button + add timeouts + 
add show proper error message in case of error.

Configure agent logger to not show warnings about appender.


  was:
As we now can start test drive directly from web console lets remove 
--test-drive options from agent, agent readme and from load metadata / sql 
dialogs.

Rename in web console test drive to "start demo"

Fix agent start sql demo from web console + add cancel button + add timeouts + 
add show proper error message in case of error.



> Remove --test-drive from agent, agent readme, console UI dialogs
> 
>
> Key: IGNITE-2276
> URL: https://issues.apache.org/jira/browse/IGNITE-2276
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Andrey Novikov
>Priority: Minor
> Fix For: 1.6
>
>
> As we now can start test drive directly from web console lets remove 
> --test-drive options from agent, agent readme and from load metadata / sql 
> dialogs.
> Rename in web console test drive to "start demo"
> Fix agent start sql demo from web console + add cancel button + add timeouts 
> + add show proper error message in case of error.
> Configure agent logger to not show warnings about appender.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2277) Add demo description to load metadata dialog

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-2277:


 Summary: Add demo description to load metadata dialog
 Key: IGNITE-2277
 URL: https://issues.apache.org/jira/browse/IGNITE-2277
 Project: Ignite
  Issue Type: Sub-task
Reporter: Alexey Kuznetsov


When start demo selected we need to show on dialog what demo is.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-799) Schema import script gets "Desktop API is not supported on the current platform" exception for Ubuntu OS

[Vasiliy Sisko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vasiliy Sisko reassigned IGNITE-799:


Assignee: Vasiliy Sisko  (was: Alexey Kuznetsov)

> Schema import script gets "Desktop API is not supported on the current 
> platform" exception for Ubuntu OS
> 
>
> Key: IGNITE-799
> URL: https://issues.apache.org/jira/browse/IGNITE-799
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: sprint-4
> Environment: Ubuntu 14.04, Ignite fabric-1.0.3-QASK2401 build #53 
> (http://94.72.60.102/viewLog.html?buildId=433416=artifacts=IgniteBuildsAndUploads_UploadIgniteGridGainMvnSiteOnDemandToGg)
>Reporter: Vasilisa  Sidorova
>Assignee: Vasiliy Sisko
>Priority: Minor
> Fix For: 1.6
>
> Attachments: 
> #_IGNITE-799_Suggestion_to_install_additional_library.patch, 
> ignite-799-libgnome.png
>
>
> -
> STEPS FOR REPRODUCE
> -
> 1. Run ignite-schema-import.sh from product bin directory
> 2. Choose connection to DB
> 3. Choose tables
> 4. Press "Generate" button
> 5. Choose answer "Yes" for question "Reveal output folder in system default 
> file browser?"
> -
> ACTUAL RESULT
> -
> There is exception in the script's console:
> {noformat}
> Exception in runnable
> java.lang.UnsupportedOperationException: Desktop API is not supported on the 
> current platform
>   at java.awt.Desktop.getDesktop(Desktop.java:144)
>   at 
> org.apache.ignite.schema.ui.SchemaImportApp$3.succeeded(SchemaImportApp.java:512)
>   at javafx.concurrent.Task.setState(Task.java:639)
>   at javafx.concurrent.Task$TaskCallable$2.run(Task.java:1271)
>   at 
> com.sun.javafx.application.PlatformImpl$4$1.run(PlatformImpl.java:182)
>   at 
> com.sun.javafx.application.PlatformImpl$4$1.run(PlatformImpl.java:179)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at com.sun.javafx.application.PlatformImpl$4.run(PlatformImpl.java:179)
>   at 
> com.sun.glass.ui.InvokeLaterDispatcher$Future.run(InvokeLaterDispatcher.java:76)
>   at com.sun.glass.ui.gtk.GtkApplication._runLoop(Native Method)
>   at com.sun.glass.ui.gtk.GtkApplication$3$1.run(GtkApplication.java:89)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> All data are generated correctly
> -
> EXPECTED RESULT
> -
> Undefined. May be it should be modal window with error message instead 
> exception in the console.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2274) Avoid ArrayList creation for a single element when possible.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-2274:
---

 Summary: Avoid ArrayList creation for a single element when 
possible.
 Key: IGNITE-2274
 URL: https://issues.apache.org/jira/browse/IGNITE-2274
 Project: Ignite
  Issue Type: Sub-task
  Components: general
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 1.6


Profiling shown lots of ArrayList allocations. Investigation shown the 
following usual pattern in our code:
1) Create empty ArrayList.
2) Then add a single element to it at some point. When this addition happens, 
ArrayList allocates Object[10] array. 

But in lots cases we know in advance that particular senario will contain only 
single entry in this collection.

Need to fix places where it is trivial to detect and handle.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2279) Add more space on top margin for XML/java preview

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-2279:


 Summary: Add more space on top margin for XML/java preview
 Key: IGNITE-2279
 URL: https://issues.apache.org/jira/browse/IGNITE-2279
 Project: Ignite
  Issue Type: Sub-task
Reporter: Alexey Kuznetsov
Priority: Minor






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-2278) Rework all tooltips - add bullets where multilines text

[Dmitriy Setrakyan (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-2278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15071498#comment-15071498
 ] 

Dmitriy Setrakyan commented on IGNITE-2278:
---

I think we should add bullets to a couple of tooltips and see how it will look 
before making a global change.

> Rework all tooltips - add bullets where multilines text
> ---
>
> Key: IGNITE-2278
> URL: https://issues.apache.org/jira/browse/IGNITE-2278
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Alexey Kuznetsov
> Fix For: 1.6
>
>
> We need to add bullets in tooltips where it make sense for better usability.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Vladimir Ershov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15071430#comment-15071430
 ] 

Vladimir Ershov commented on IGNITE-2032:
-

Waiting for the review.

> Filters passed to ScanQuery are not redeployed when originating from a client 
> node
> --
>
> Key: IGNITE-2032
> URL: https://issues.apache.org/jira/browse/IGNITE-2032
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Vladimir Ershov
>Priority: Critical
>  Labels: important
> Fix For: 1.6
>
> Attachments: ScanQueryFailure.java, test-config.xml
>
>
> The following case doesn't work:
> - start a standalone server node with peer class loading enabled;
> - start a client node, populate a cache with data, perform a scan query using 
> a filter;
> - since the server doesn't have the filter in its classpath it will load it 
> from the client. Everything works fine here;
> - stop the client, the server will undeploy the filter. No issue here so far;
> - modify the filter a bit and start the client one more time. The server 
> won't deploy the new version of the filter and will be using the old 
> regardless of the fact that it was undeployed before according to the logs.
> The server can be started using ignite.bat and test-config.xml (attached).
> The source of the client is located in attached ScanQueryFailure.java.
> BTW, everything works fine if to use the server mode instead of the client 
> one.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2268) Implement CacheKeyConfiguration on cluster page

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-2268:
-

 Summary: Implement CacheKeyConfiguration on cluster page
 Key: IGNITE-2268
 URL: https://issues.apache.org/jira/browse/IGNITE-2268
 Project: Ignite
  Issue Type: Sub-task
Affects Versions: 1.6
Reporter: Vasiliy Sisko
 Fix For: 1.6


Extend binary configuration.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2270) GridDhtTxLocalAdapter: is ConcurrentHashMap8 really needed there?

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-2270:

Summary: GridDhtTxLocalAdapter: is ConcurrentHashMap8 really needed there?  
(was: GridDhtTxLocalAdapter: isConcurrentHashMap8 really needed there?)

> GridDhtTxLocalAdapter: is ConcurrentHashMap8 really needed there?
> -
>
> Key: IGNITE-2270
> URL: https://issues.apache.org/jira/browse/IGNITE-2270
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 1.6
>
>
> GridDhtTxLocalAdapter creates two CHM8: nearMap and dhtMap. 
> It looks like there is no real contention on these fields so they could be 
> replaced with plain HashMap (possibly synchronized).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2281) We need to save content in tables on focus lost and not force user to click "disk" icon

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-2281:


 Summary: We need to save content in tables on focus lost and not 
force user to click "disk" icon
 Key: IGNITE-2281
 URL: https://issues.apache.org/jira/browse/IGNITE-2281
 Project: Ignite
  Issue Type: Sub-task
Reporter: Alexey Kuznetsov






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2280) In case of one cluster/cache/metadata they should be selected by default

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-2280:


 Summary: In case of one cluster/cache/metadata they should be 
selected by default
 Key: IGNITE-2280
 URL: https://issues.apache.org/jira/browse/IGNITE-2280
 Project: Ignite
  Issue Type: Sub-task
Reporter: Alexey Kuznetsov


For better user experience we need to pre-select cluster/cache/metadata where 
it make sense.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-2154) .NET: doxygen docs generation must be included into Maven build process.

[Anton Vinogradov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15071482#comment-15071482
 ] 

Anton Vinogradov commented on IGNITE-2154:
--

Great, thanks.
Suggestion applied.

> .NET: doxygen docs generation must be included into Maven build process.
> 
>
> Key: IGNITE-2154
> URL: https://issues.apache.org/jira/browse/IGNITE-2154
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: 1.5
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2272) visorcmd: it seems that we show incorrect value for 'Heap memory maximum'

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-2272:
--

 Summary: visorcmd: it seems that we show incorrect value for 'Heap 
memory maximum'
 Key: IGNITE-2272
 URL: https://issues.apache.org/jira/browse/IGNITE-2272
 Project: Ignite
  Issue Type: Bug
Reporter: Pavel Konstantinov


I'm started node with JVM opts '-Xms1g -Xmx1400m' but 'node' command displays 
incorrect data for -Xmx 
{code}
| Heap memory initialized | 1gb
| Heap memory used| 1,024mb
| Heap memory committed   | 1gb
| Heap memory maximum | 1gb
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2275) Hadoop: restore external code execution.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-2275:
---

 Summary: Hadoop: restore external code execution.
 Key: IGNITE-2275
 URL: https://issues.apache.org/jira/browse/IGNITE-2275
 Project: Ignite
  Issue Type: Task
  Components: hadoop
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
Priority: Critical
 Fix For: 1.6


Several major problems with internal job execution were revealed:
1) Native code cannot run normally.
2) Excessive permgen allocations
3) We must use some dirty hacks to prevent classloader leaks (see mocked 
classes in HadoopClassLoader).

External execution must help us with it. 

The problem is that it never worked properly. We must restore it and then test 
very thoroughly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2269) Implement additional constructors for Binary type configurations

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-2269:
-

 Summary: Implement additional constructors for Binary type 
configurations
 Key: IGNITE-2269
 URL: https://issues.apache.org/jira/browse/IGNITE-2269
 Project: Ignite
  Issue Type: Sub-task
  Components: wizards
Affects Versions: 1.6
Reporter: Vasiliy Sisko
Assignee: Vasiliy Sisko
 Fix For: 1.6


Implement constructors with parameters and implement generation of java code 
and xml config with that constructors.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2270) GridDhtTxLocalAdapter: isConcurrentHashMap8 really needed there?

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-2270:
---

 Summary: GridDhtTxLocalAdapter: isConcurrentHashMap8 really needed 
there?
 Key: IGNITE-2270
 URL: https://issues.apache.org/jira/browse/IGNITE-2270
 Project: Ignite
  Issue Type: Sub-task
  Components: cache
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 1.6


GridDhtTxLocalAdapter creates two CHM8: nearMap and dhtMap. 
It looks like there is no real contention on these fields so they could be 
replaced with plain HashMap (possibly synchronized).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2271) visorcmd: mlist shows strange value for cache

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-2271:
--

 Summary: visorcmd: mlist shows strange value for  cache
 Key: IGNITE-2271
 URL: https://issues.apache.org/jira/browse/IGNITE-2271
 Project: Ignite
  Issue Type: Bug
  Components: UI
Reporter: Pavel Konstantinov
Priority: Trivial


{code}
visor> mlist
+===+
| Name | Value  |
+===+
| c0   | -519a5764-b9cf-4b10-8a45-e434d7e0c9b9 |
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2273) Arrays.asList() should not be used to 1- and 2- elements.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-2273:
---

 Summary: Arrays.asList() should not be used to 1- and 2- elements.
 Key: IGNITE-2273
 URL: https://issues.apache.org/jira/browse/IGNITE-2273
 Project: Ignite
  Issue Type: Sub-task
  Components: general
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
 Fix For: 1.6


There are several places in code where Arrays.asList is used as follows:
1) For a single element. These places should be replaced with 
Collections.singleton() to avoid unnecessary array allocations.
2) For two elements. Here we should create our own "doubled-singleton" 
implementation.

Some of these places are located on hot code paths (e.g. cache PUT).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2161) We need to tune Ignite site CSS to make it looks good for printing

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov updated IGNITE-2161:
-
Fix Version/s: 1.5

> We need to tune Ignite site CSS to make it looks good for printing
> --
>
> Key: IGNITE-2161
> URL: https://issues.apache.org/jira/browse/IGNITE-2161
> Project: Ignite
>  Issue Type: Bug
>  Components: website
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
> Fix For: 1.5
>
>
> Open in chrome https://ignite.apache.org/benchmarks/ignite-vs-hazelcast.html
> Click Print -> looks ugly.
> See some ideas here: 
> http://www.creativebloq.com/responsive-web-design/make-your-website-printable-css-3132929



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1278) Improve schema-import - generate cache configuration for each table

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov updated IGNITE-1278:
-
Fix Version/s: 1.6

> Improve schema-import - generate cache configuration for each table
> ---
>
> Key: IGNITE-1278
> URL: https://issues.apache.org/jira/browse/IGNITE-1278
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
>Priority: Minor
> Fix For: 1.6
>
>
> Currently schema-import generates only cache type metadata.
> But will be useful optionally to generate separated cache configuration for 
> each table. In this case user will have completely cache configuration with 
> type metadata.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2287) Generate some POJO store example if downloaded project contains caches with store + metadata

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-2287:


 Summary: Generate some POJO store example if downloaded project 
contains caches with store + metadata
 Key: IGNITE-2287
 URL: https://issues.apache.org/jira/browse/IGNITE-2287
 Project: Ignite
  Issue Type: Sub-task
Reporter: Alexey Kuznetsov


It will be useful to have example that will demonstrate how to load data from 
DB into cache via POJO store



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-2002) .Net: Data streamer does not work with peerClassLoadingEnabled

[Pavel Tupitsyn (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn reassigned IGNITE-2002:
--

Assignee: Pavel Tupitsyn

> .Net: Data streamer does not work with peerClassLoadingEnabled
> --
>
> Key: IGNITE-2002
> URL: https://issues.apache.org/jira/browse/IGNITE-2002
> Project: Ignite
>  Issue Type: Bug
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Fix For: 1.6
>
>
> Add  to spring config, 
> run streamer tests or examples, there are exceptions in Java and flush hangs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Andrey Gura (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15071705#comment-15071705
 ] 

Andrey Gura commented on IGNITE-2080:
-

{{GridUnsafeDataInput}} and {{GridUnsafeDataOutput}} classes should use the 
same byte order regardles system byte order. Otherwise situations are possible 
when read data types will differ from written data type (it is case why 
{{OptimizedObjectStreamSelfTest.testIncorrectExternalizable}} fails). After 
fixing of byte order the rest of tests passed.

Also I think that any streams should have fixed byte order. Otherwise 
heterogeneous claster isn't possible. So, from my point of view, 
{{DirectByteBufferStreamImplV1}} and {{DirectByteBufferStreamImplV2}} should 
also have fixed byte order.

One more test is still fails on Solaris: 
{{CacheAffinityCallSelfTest.testAffinityCallRestartNode}}. And for now I have 
no idea why it happens.

Also I run full API test suite and will have results tomorrow.

See PR https://github.com/apache/ignite/pull/362

> JVM crashes on SunOS with SIGBUS (0xa) on frame [libjvm.so+0xc7c438]  
> Unsafe_SetInt+0x14c
> -
>
> Key: IGNITE-2080
> URL: https://issues.apache.org/jira/browse/IGNITE-2080
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5, 1.4
> Environment: SunOS 5.11, JDK 7
>Reporter: Andrey Gura
>Assignee: Andrey Gura
> Fix For: 1.6
>
> Attachments: 054424_0_localhost.log, benchmark-offheap.properties, 
> hs_err_pid10523.log
>
>
> JVM crashes on SunOS 5.11 with the following message:
> {noformat}
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGBUS (0xa) at pc=0x76a7c438, pid=10523, tid=652
> #
> # JRE version: Java(TM) SE Runtime Environment (7.0_79-b15) (build 
> 1.7.0_79-b15)
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.79-b02 mixed mode 
> solaris-sparc )
> # Problematic frame:
> # V  [libjvm.so+0xc7c438]  Unsafe_SetInt+0x14c
> {noformat}
> Stack trace:
> {noformat}
> Stack: [0xfff0f6f0,0xfff0f700],  sp=0xfff0f6ffd1f0,  free 
> space=1012k
> Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native 
> code)
> V  [libjvm.so+0xc7c438]  Unsafe_SetInt+0x14c
> j  sun.misc.Unsafe.putInt(Ljava/lang/Object;JI)V+-1763873616
> j  sun.misc.Unsafe.putInt(Ljava/lang/Object;JI)V+0
> j  
> org.apache.ignite.internal.util.IgniteUtils.writeVersion([BJLorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;)J+135
> j  
> org.apache.ignite.internal.processors.cache.GridCacheSwapEntryImpl.marshal()[B+128
> j  
> org.apache.ignite.internal.processors.cache.GridCacheSwapManager.write(Lorg/apache/ignite/internal/processors/cache/KeyCacheObject;Ljava/nio/ByteBuffer;BLorg/apache/
> ignite/internal/processors/cache/version/GridCacheVersion;JJLorg/apache/ignite/lang/IgniteUuid;Lorg/apache/ignite/lang/IgniteUuid;)V+86
> j  org.apache.ignite.internal.processors.cache.GridCacheMapEntry.swap()V+333
> j  
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.evictInternal(ZLorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;[Lorg/apache/ignit
> e/internal/processors/cache/CacheEntryPredicate;)Z+122
> j  
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.evict0(Lorg/apache/ignite/internal/processors/cache/GridCacheAdapter;Lorg/apache/ignite/internal
> /processors/cache/GridCacheEntryEx;Lorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;[Lorg/apache/ignite/internal/processors/cache/CacheEntryPredica
> te;Z)Z+117
> j  
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.touch(Lorg/apache/ignite/internal/processors/cache/GridCacheEntryEx;Lorg/apache/ignite/internal/
> processors/affinity/AffinityTopologyVersion;)V+123
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.unlockEntries(Ljava/util/Collection;Lorg/apache/ignite/internal/processors/affi
> nity/AffinityTopologyVersion;)V+331
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(Ljava/util/UUID;Lorg/apache/ignite/internal/processors/
> cache/distributed/dht/atomic/GridNearAtomicUpdateRequest;Lorg/apache/ignite/internal/util/typedef/CI2;)V+1023
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(Ljava/util/UUID;Lorg/apache/ignite/internal/processors/c
> ache/distributed/dht/atomic/GridNearAtomicUpdateRequest;Lorg/apache/ignite/internal/util/typedef/CI2;)V+33
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapSingle(Ljava/util/UUID;Lorg/apache/ignite/internal/processors/cache/
> 

[jira] [Closed] (IGNITE-2135) ClassNotFoundException for CacheContinuousQueryExample

[Alexey Goncharuk (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Goncharuk closed IGNITE-2135.


> ClassNotFoundException for CacheContinuousQueryExample
> --
>
> Key: IGNITE-2135
> URL: https://issues.apache.org/jira/browse/IGNITE-2135
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Assignee: Saikat Maitra
>Priority: Critical
> Fix For: 1.6
>
>
> 1. Start 3 nodes with examples/config/example-ignite.xml
> 2. Run CacheContinuousQueryExample in IDEA
> 3. The example fails:
> {noformat}
> >>> Cache continuous query example started.
> [14:15:07] Ignite node stopped OK [uptime=00:00:00:898]
> Exception in thread "main" javax.cache.CacheException: class 
> org.apache.ignite.IgniteCheckedException: Query execution failed: 
> GridCacheQueryBean [qry=GridCacheQueryAdapter [type=SCAN, clsName=null, 
> clause=null, 
> filter=org.apache.ignite.examples.datagrid.CacheContinuousQueryExample$1@6b6b1935,
>  part=null, incMeta=false, metrics=GridCacheQueryMetricsAdapter [minTime=0, 
> maxTime=0, sumTime=0, avgTime=0.0, execs=0, completed=0, fails=0], 
> pageSize=1024, timeout=0, keepAll=true, incBackups=false, dedup=false, 
> prj=null, keepPortable=false, subjId=2908e088-371e-4528-9141-52efb5ef42d6, 
> taskHash=0], rdc=null, trans=null]
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1634)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.next(GridCacheQueryFutureAdapter.java:181)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy$5.onHasNext(IgniteCacheProxy.java:528)
>   at 
> org.apache.ignite.internal.util.GridCloseableIteratorAdapter.hasNextX(GridCloseableIteratorAdapter.java:53)
>   at 
> org.apache.ignite.internal.util.lang.GridIteratorAdapter.hasNext(GridIteratorAdapter.java:45)
>   at 
> org.apache.ignite.examples.datagrid.CacheContinuousQueryExample.main(CacheContinuousQueryExample.java:92)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
> Caused by: class org.apache.ignite.IgniteCheckedException: Query execution 
> failed: GridCacheQueryBean [qry=GridCacheQueryAdapter [type=SCAN, 
> clsName=null, clause=null, 
> filter=org.apache.ignite.examples.datagrid.CacheContinuousQueryExample$1@6b6b1935,
>  part=null, incMeta=false, metrics=GridCacheQueryMetricsAdapter [minTime=0, 
> maxTime=0, sumTime=0, avgTime=0.0, execs=0, completed=0, fails=0], 
> pageSize=1024, timeout=0, keepAll=true, incBackups=false, dedup=false, 
> prj=null, keepPortable=false, subjId=2908e088-371e-4528-9141-52efb5ef42d6, 
> taskHash=0], rdc=null, trans=null]
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.checkError(GridCacheQueryFutureAdapter.java:267)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.internalIterator(GridCacheQueryFutureAdapter.java:325)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.next(GridCacheQueryFutureAdapter.java:171)
>   ... 9 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to execute 
> query on node [query=GridCacheQueryBean [qry=GridCacheQueryAdapter 
> [type=SCAN, clsName=null, clause=null, 
> filter=org.apache.ignite.examples.datagrid.CacheContinuousQueryExample$1@6b6b1935,
>  part=null, incMeta=false, metrics=GridCacheQueryMetricsAdapter [minTime=0, 
> maxTime=0, sumTime=0, avgTime=0.0, execs=0, completed=0, fails=0], 
> pageSize=1024, timeout=0, keepAll=true, incBackups=false, dedup=false, 
> prj=null, keepPortable=false, subjId=2908e088-371e-4528-9141-52efb5ef42d6, 
> taskHash=0], rdc=null, trans=null], 
> nodeId=a17e9748-7771-441c-a594-122c598b7b8e]
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.onPage(GridCacheQueryFutureAdapter.java:390)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager.processQueryResponse(GridCacheDistributedQueryManager.java:395)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager.access$000(GridCacheDistributedQueryManager.java:60)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager$1.apply(GridCacheDistributedQueryManager.java:90)
>   at 
> 

[jira] [Assigned] (IGNITE-1223) Use Gson instead of net.sf.json-lib:json-lib:2.4

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov reassigned IGNITE-1223:


Assignee: Semen Boikov  (was: Andrey Novikov)

Semen, take a look at this.

May be it make sense to investigate possible upgrade to Gson, because 
net.sf.json-lib seems to be abandoned project.


> Use Gson instead of net.sf.json-lib:json-lib:2.4
> 
>
> Key: IGNITE-1223
> URL: https://issues.apache.org/jira/browse/IGNITE-1223
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Sergey Evdokimov
>Assignee: Semen Boikov
> Fix For: 1.6
>
> Attachments: master_ae11e9b_ignite-1223.patch
>
>
> Gson faster then "net.sf.json-lib:json-lib:2.4" 4 times. (Serialization of 
> GridRestCommand#NODE responce 2 times take 1,45 seconds with Gson and 5,8 
> seconds with json-lib. Also json-lib cannot work with gridgain-style getters 
> and setters.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1223) Use Gson instead of net.sf.json-lib:json-lib:2.4

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov updated IGNITE-1223:
-
Fix Version/s: 1.6

> Use Gson instead of net.sf.json-lib:json-lib:2.4
> 
>
> Key: IGNITE-1223
> URL: https://issues.apache.org/jira/browse/IGNITE-1223
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Sergey Evdokimov
>Assignee: Semen Boikov
> Fix For: 1.6
>
> Attachments: master_ae11e9b_ignite-1223.patch
>
>
> Gson faster then "net.sf.json-lib:json-lib:2.4" 4 times. (Serialization of 
> GridRestCommand#NODE responce 2 times take 1,45 seconds with Gson and 5,8 
> seconds with json-lib. Also json-lib cannot work with gridgain-style getters 
> and setters.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-254) Visor: cache command skips wrong arguments

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov updated IGNITE-254:

Fix Version/s: 1.6

> Visor: cache command skips wrong arguments
> --
>
> Key: IGNITE-254
> URL: https://issues.apache.org/jira/browse/IGNITE-254
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: sprint-1
>Reporter: Sergey Kozlov
>Assignee: Andrey Novikov
> Fix For: 1.6
>
>
> Ignite visor skips wrong arguments.
> {noformat}
> visor> cache -clear -c='partitioned'
> Cleared cache with name: partitioned
> +==+
> |  Node ID8(@)  | Cache Size Before | Cache Size After |
> +==+
> | 3277D96E(@n0) | 0 | 0|
> +--+
> visor> cache clear -c='partitioned'
> Time of the snapshot: 02/14/15, 15:45:41
> +===
> +
> | Name(@)  | Nodes  |  Entries  |   
> Hits|  Misses   |   Reads   |  Writes
> |
> +===
> +
> | partitioned(@c4) | [3277d96e-37af-4f85-8437-65563aee7a5a] | min: 0| 
> min: 0| min: 0| min: 0| min: 0
> |
> |  || avg: 0.00 | 
> avg: 0.00 | avg: 0.00 | avg: 0.00 | avg: 0.00
> |
> |  || max: 0| 
> max: 0| max: 0| max: 0| max: 0
> |
> +---
> +
> Use "-a" flag to see detailed statistics.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1054) New version checker should print out info about new version using logger in daemon node

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov updated IGNITE-1054:
-
Fix Version/s: 1.6

> New version checker should print out info about new version using logger in 
> daemon node
> ---
>
> Key: IGNITE-1054
> URL: https://issues.apache.org/jira/browse/IGNITE-1054
> Project: Ignite
>  Issue Type: Bug
>  Components: UI
>Affects Versions: sprint-7
>Reporter: Pavel Konstantinov
>Assignee: Andrey Novikov
>Priority: Minor
> Fix For: 1.6
>
>
> Currently new version checker prints out info in current cursor position and 
> may 'corrupt' text user writing
> For example, I wrote 'cache' command and got:
> {code}
> visor> ca[10:46:26] New version is available at 
> http://www.gridgain.com/download/editions/#enterprise-edition: 7.1.4che
> {code}
> Or may be we can prevent daemon node output at all.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Andrey Gura (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15071638#comment-15071638
 ] 

Andrey Gura commented on IGNITE-2080:
-

{{GridEmbeddedFutureSelfTest}} test passes if increase stack size for JVM.

> JVM crashes on SunOS with SIGBUS (0xa) on frame [libjvm.so+0xc7c438]  
> Unsafe_SetInt+0x14c
> -
>
> Key: IGNITE-2080
> URL: https://issues.apache.org/jira/browse/IGNITE-2080
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5, 1.4
> Environment: SunOS 5.11, JDK 7
>Reporter: Andrey Gura
>Assignee: Andrey Gura
> Fix For: 1.6
>
> Attachments: 054424_0_localhost.log, benchmark-offheap.properties, 
> hs_err_pid10523.log
>
>
> JVM crashes on SunOS 5.11 with the following message:
> {noformat}
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGBUS (0xa) at pc=0x76a7c438, pid=10523, tid=652
> #
> # JRE version: Java(TM) SE Runtime Environment (7.0_79-b15) (build 
> 1.7.0_79-b15)
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.79-b02 mixed mode 
> solaris-sparc )
> # Problematic frame:
> # V  [libjvm.so+0xc7c438]  Unsafe_SetInt+0x14c
> {noformat}
> Stack trace:
> {noformat}
> Stack: [0xfff0f6f0,0xfff0f700],  sp=0xfff0f6ffd1f0,  free 
> space=1012k
> Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native 
> code)
> V  [libjvm.so+0xc7c438]  Unsafe_SetInt+0x14c
> j  sun.misc.Unsafe.putInt(Ljava/lang/Object;JI)V+-1763873616
> j  sun.misc.Unsafe.putInt(Ljava/lang/Object;JI)V+0
> j  
> org.apache.ignite.internal.util.IgniteUtils.writeVersion([BJLorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;)J+135
> j  
> org.apache.ignite.internal.processors.cache.GridCacheSwapEntryImpl.marshal()[B+128
> j  
> org.apache.ignite.internal.processors.cache.GridCacheSwapManager.write(Lorg/apache/ignite/internal/processors/cache/KeyCacheObject;Ljava/nio/ByteBuffer;BLorg/apache/
> ignite/internal/processors/cache/version/GridCacheVersion;JJLorg/apache/ignite/lang/IgniteUuid;Lorg/apache/ignite/lang/IgniteUuid;)V+86
> j  org.apache.ignite.internal.processors.cache.GridCacheMapEntry.swap()V+333
> j  
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.evictInternal(ZLorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;[Lorg/apache/ignit
> e/internal/processors/cache/CacheEntryPredicate;)Z+122
> j  
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.evict0(Lorg/apache/ignite/internal/processors/cache/GridCacheAdapter;Lorg/apache/ignite/internal
> /processors/cache/GridCacheEntryEx;Lorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;[Lorg/apache/ignite/internal/processors/cache/CacheEntryPredica
> te;Z)Z+117
> j  
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.touch(Lorg/apache/ignite/internal/processors/cache/GridCacheEntryEx;Lorg/apache/ignite/internal/
> processors/affinity/AffinityTopologyVersion;)V+123
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.unlockEntries(Ljava/util/Collection;Lorg/apache/ignite/internal/processors/affi
> nity/AffinityTopologyVersion;)V+331
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(Ljava/util/UUID;Lorg/apache/ignite/internal/processors/
> cache/distributed/dht/atomic/GridNearAtomicUpdateRequest;Lorg/apache/ignite/internal/util/typedef/CI2;)V+1023
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(Ljava/util/UUID;Lorg/apache/ignite/internal/processors/c
> ache/distributed/dht/atomic/GridNearAtomicUpdateRequest;Lorg/apache/ignite/internal/util/typedef/CI2;)V+33
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapSingle(Ljava/util/UUID;Lorg/apache/ignite/internal/processors/cache/
> distributed/dht/atomic/GridNearAtomicUpdateRequest;)V+28
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.access$1200(Lorg/apache/ignite/internal/processors/cache/distributed/dh
> t/atomic/GridNearAtomicUpdateFuture;Ljava/util/UUID;Lorg/apache/ignite/internal/processors/cache/distributed/dht/atomic/GridNearAtomicUpdateRequest;)V+3
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.map(Lorg/apache/ignite/internal/processors/affinity/Affinit
> yTopologyVersion;)V+595
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology()V+253
> j  
> 

[jira] [Resolved] (IGNITE-755) Add example for Query + CacheTypeMetadata

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov resolved IGNITE-755.
-
Resolution: Won't Fix
  Assignee: (was: Vasiliy Sisko)

CacheTypeMetadata was deprecated in ignite-1.5.

> Add example for Query + CacheTypeMetadata
> -
>
> Key: IGNITE-755
> URL: https://issues.apache.org/jira/browse/IGNITE-755
> Project: Ignite
>  Issue Type: Task
>Reporter: Alexey Kuznetsov
> Attachments: 
> 0001-IGNITE-755-Implemented-example-of-cache-type-metadat.patch
>
>
> Check content for page 
> https://dash.readme.io/project/apacheignite/v1.3/suggested/update/556e697efc3aa80d00e1a8f2



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-303) Create test reproducing the SO issue

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov reassigned IGNITE-303:
---

Assignee: (was: Andrey Novikov)

> Create test reproducing the SO issue
> 
>
> Key: IGNITE-303
> URL: https://issues.apache.org/jira/browse/IGNITE-303
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-2
>Reporter: Alexey Kuznetsov
>
> http://stackoverflow.com/questions/27290272/failed-to-send-update-request-to-backup-node



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2286) Improve Metadata load from cache

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-2286:


 Summary: Improve Metadata load from cache
 Key: IGNITE-2286
 URL: https://issues.apache.org/jira/browse/IGNITE-2286
 Project: Ignite
  Issue Type: Sub-task
Reporter: Alexey Kuznetsov
 Fix For: 1.6


# Add option "Generate primitives in POJO for not null columns"+ tooltip with 
description
# Add option "Use Java builtin types as Key class" + tooltip with description 
when KeyClass generated and when it will be better to use java builtin types




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-1419) .Net: Add optional "raw" flag to binary type configuration.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15071589#comment-15071589
 ] 

ASF GitHub Bot commented on IGNITE-1419:


GitHub user ptupitsyn opened a pull request:

https://github.com/apache/ignite/pull/377

IGNITE-1419 .Net: Add optional "raw" flag to binary type configuration.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ptupitsyn/ignite ignite-1419

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/377.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #377


commit edc0bd67f1003b50fde74ee3d8160909a2eb4a8c
Author: Pavel Tupitsyn 
Date:   2015-12-25T09:35:24Z

IGNITE-1419 .Net: Add optional "raw" flag to binary type configuration.

commit 34f5662919caa2099847a1e26ac0833bad4abfad
Author: Pavel Tupitsyn 
Date:   2015-12-25T09:41:40Z

wip Java

commit 4b87360e458607b44a5b1d9139ef9b0e05f0e570
Author: Pavel Tupitsyn 
Date:   2015-12-25T09:45:36Z

wip

commit 1882ada2a6e34975a47e47fc5a060c4d9b32cb0d
Author: Pavel Tupitsyn 
Date:   2015-12-25T09:46:51Z

wip

commit 28483646ab1cf0ba11f93dbf0b773d6c062de467
Author: Pavel Tupitsyn 
Date:   2015-12-25T10:05:09Z

wip

commit c6dfc28fdae9d3a1cf3c8ec940183638ae0f8231
Author: Pavel Tupitsyn 
Date:   2015-12-25T10:40:45Z

wip

commit 1e664132f4ccc1c240523637dc3392e1609c4aa6
Author: Pavel Tupitsyn 
Date:   2015-12-25T10:50:01Z

wip

commit 3d75004d3969aab625c90b42a5af9a94834488e4
Author: Pavel Tupitsyn 
Date:   2015-12-25T10:58:05Z

wip

commit 8f35db028f3c30f7d6b80744cda81e337a69e23a
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:06:08Z

wip

commit 802b5ad69230fd288734b6e5406cb29e9ad2a577
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:08:42Z

wip

commit 03f60ac14eecf9889543119fbd347d137d7d6ad2
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:09:59Z

wip

commit 375f57058665b15f2ab405cbbef5cab26662140e
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:21:00Z

wip test

commit 1c7958075ff71b75260b239902f4f00cb3ae3861
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:41:24Z

Test works

commit 876d1132517e63accbb4cc6118ae9cdc296bd85b
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:45:14Z

wip tests

commit 8f9c671291540f679b47e46146f3efcb0936963e
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:48:49Z

wip tests

commit 07e03db0134b632ee52bca23bf4a2977dd33a18c
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:49:51Z

wip tests

commit f7c1ddda8cda98a7c2ac38f742419de940d87686
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:51:51Z

wip

commit cb9ef1bbe6255907392dd6326327f728b368fd61
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:54:47Z

Fix npe in collections




> .Net: Add optional "raw" flag to binary type configuration.
> ---
>
> Key: IGNITE-1419
> URL: https://issues.apache.org/jira/browse/IGNITE-1419
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
>
> By default we write .Net objects with field names included. But in some cases 
> it is not needed. E.g. when objects are not going to be used in queries.
> Removing field names will speed up serialization/deserialization. We can add 
> optional "raw" flag to portable type descriptor to control this behavior.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-1413) .Net: Get rid of set -> map conversion in PlatformDotNetCacheStore.writeAll

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15071620#comment-15071620
 ] 

ASF GitHub Bot commented on IGNITE-1413:


GitHub user ptupitsyn opened a pull request:

https://github.com/apache/ignite/pull/380

IGNITE-1413 .Net: Get rid of set -> map conversion in 
PlatformDotNetCacheStore.writeAll



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ptupitsyn/ignite ignite-1413

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/380.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #380


commit 38e36bd720a2082e400947b5352c9405fad00c6d
Author: Pavel Tupitsyn 
Date:   2015-12-25T13:46:22Z

IGNITE-1413 .Net: Get rid of set -> map conversion in 
PlatformDotNetCacheStore.writeAll




> .Net: Get rid of set -> map conversion in PlatformDotNetCacheStore.writeAll
> ---
>
> Key: IGNITE-1413
> URL: https://issues.apache.org/jira/browse/IGNITE-1413
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
>
> This is a legacy artifact from a veeery old API which is currently removed. 
> Just pass set without unnecessary conversions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2283) Improve Summary page

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov updated IGNITE-2283:
-
Summary: Improve Summary page  (was: Improve download on Summary page)

> Improve Summary page
> 
>
> Key: IGNITE-2283
> URL: https://issues.apache.org/jira/browse/IGNITE-2283
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Priority: Minor
> Fix For: 1.6
>
>
> # Add "project" to download button and "Project structure" link that will 
> show popup with project structure description
> # Change "On this page" to be more accurate with description about page
> # rename "factory" package to "config"
> # Add more info into README.txt in jdbc-drivers folder
> # Describe project structure in root README.txt
> # Generated pom.xml should be configured as code java 7, source java 7
> # Add in more info links to documentation



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2283) Improve Summary page

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov updated IGNITE-2283:
-
Description: 
# Add "project" to download button and "Project structure" link that will show 
popup with project structure description
# Change "On this page" to be more accurate with description about page
# rename "factory" package to "config"
# Add more info into README.txt in jdbc-drivers folder
# Describe project structure in root README.txt
# Generated pom.xml should be configured as code java 7, source java 7
# Add in more info links to documentation
# Add in more info links to Ignite downloads

  was:
# Add "project" to download button and "Project structure" link that will show 
popup with project structure description
# Change "On this page" to be more accurate with description about page
# rename "factory" package to "config"
# Add more info into README.txt in jdbc-drivers folder
# Describe project structure in root README.txt
# Generated pom.xml should be configured as code java 7, source java 7
# Add in more info links to documentation



> Improve Summary page
> 
>
> Key: IGNITE-2283
> URL: https://issues.apache.org/jira/browse/IGNITE-2283
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Priority: Minor
> Fix For: 1.6
>
>
> # Add "project" to download button and "Project structure" link that will 
> show popup with project structure description
> # Change "On this page" to be more accurate with description about page
> # rename "factory" package to "config"
> # Add more info into README.txt in jdbc-drivers folder
> # Describe project structure in root README.txt
> # Generated pom.xml should be configured as code java 7, source java 7
> # Add in more info links to documentation
> # Add in more info links to Ignite downloads



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2284) Improve Metadata and Caches screen integration

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-2284:


 Summary: Improve Metadata and Caches screen integration
 Key: IGNITE-2284
 URL: https://issues.apache.org/jira/browse/IGNITE-2284
 Project: Ignite
  Issue Type: Sub-task
Reporter: Alexey Kuznetsov
Priority: Minor


# Add "name" to "Data source bean" labels
# Auto generate name for POJO Store datasource bean name (cacheName + Ds).
# Auto select H2 dialect
# If on metadata page cache is selected and this cache has no store configured 
we need to show dialog with cache POJO store configuration on user click "Save" 
button




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-302) 2nd run CacheQueryExample fails on 2 nodes

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov reassigned IGNITE-302:
---

Assignee: Sergey Kozlov  (was: Andrey Novikov)

Sergey, as you checked all examples and verified how examples should be 
started, could you check if this issue is valid for ignite-1.5?

> 2nd run CacheQueryExample fails on 2 nodes
> --
>
> Key: IGNITE-302
> URL: https://issues.apache.org/jira/browse/IGNITE-302
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: sprint-2
>Reporter: Alexey Kuznetsov
>Assignee: Sergey Kozlov
>
> 1. Start two nodes by bin\ggstart.bat examples\config\example-cache.xml
> 2. Run in Idea CacheQueryExample twice
> 3. Second run hangs and one node has ClassNotFoundException:
> {noformat}
> [17:11:11,044][WARNING][gridgain-#23%sys-null%][GridDeploymentPerVersionStore]
>  Failed to load peer class (ignore if class got undeployed during preloa
> ding) [alias=o.g.examples.datagrid.CacheQueryExample$Person, 
> dep=SharedDeployment [rmv=false, super=GridDeployment [ts=1414415470972, 
> depMode=SHARED,
> clsLdr=GridDeploymentClassLoader 
> [id=909c9b15941-8a410e89-f7a0-4ec6-a6b4-c4d135de731a, singleNode=false, 
> nodeLdrMap={a73e5cd4-c058-46b8-a3d9-cb0f4bbad
> 5c1=0fe3bb15941-a73e5cd4-c058-46b8-a3d9-cb0f4bbad5c1, 
> 09497dce-3430-4555-8a75-676c0275119c=1e8b9b15941-09497dce-3430-4555-8a75-676c0275119c},
>  p2pTimeo
> ut=5000, usrVer=0, depMode=SHARED, quiet=false], 
> clsLdrId=909c9b15941-8a410e89-f7a0-4ec6-a6b4-c4d135de731a, userVer=0, 
> loc=false, sampleClsName=o.g.ex
> amples.datagrid.CacheQueryExample$Organization, pendingUndeploy=false, 
> undeployed=false, usage=0]]]
> [17:11:11,046][SEVERE][gridgain-#23%sys-null%][GridCacheIoManager] 
>  Failed to process message 
> [senderId=a73e5cd4-c058-46b8-a3d9-cb0f4bbad
> 5c1]
> class org.gridgain.grid.GridException: Failed to find class with given class 
> loader for unmarshalling (make sure same version of all classes are avail
> able on all nodes or enable peer-class-loading): 
> org.gridgain.grid.kernal.processors.cache.GridCacheDeploymentManager$CacheClassLoader@724a63f4
> For more information see:
> Troubleshooting:  http://bit.ly/GridGain-Troubleshooting
> Documentation Center: http://bit.ly/GridGain-Documentation
> at 
> org.gridgain.grid.marshaller.optimized.GridOptimizedMarshaller.unmarshal(GridOptimizedMarshaller.java:355)
> at 
> org.gridgain.grid.kernal.processors.cache.GridCacheMessage.unmarshalValueBytesCollection(GridCacheMessage.java:441)
> at 
> org.gridgain.grid.kernal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateRequest.finishUnmarshal(GridNearAtomicUpdateRequest.ja
> va:491)
> at 
> org.gridgain.grid.kernal.processors.cache.GridCacheIoManager.unmarshall(GridCacheIoManager.java:752)
> at 
> org.gridgain.grid.kernal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:208)
> at 
> org.gridgain.grid.kernal.processors.cache.GridCacheIoManager.access$200(GridCacheIoManager.java:35)
> at 
> org.gridgain.grid.kernal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:128)
> at 
> org.gridgain.grid.kernal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:648)
> at 
> org.gridgain.grid.kernal.managers.communication.GridIoManager.access$1900(GridIoManager.java:48)
> at 
> org.gridgain.grid.kernal.managers.communication.GridIoManager$6.body(GridIoManager.java:609)
> at org.gridgain.grid.util.worker.GridWorker.run(GridWorker.java:137)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.ClassNotFoundException: Failed to load class 
> [name=org.gridgain.examples.datagrid.CacheQueryExample$Person, 
> ctx={1e8b9b15941-0949
> 7dce-3430-4555-8a75-676c0275119c=CachedDeploymentInfo 
> [sndId=09497dce-3430-4555-8a75-676c0275119c, 
> ldrId=1e8b9b15941-09497dce-3430-4555-8a75-676c02751
> 19c, userVer=0, depMode=SHARED, participants=null], 
> 0fe3bb15941-a73e5cd4-c058-46b8-a3d9-cb0f4bbad5c1=CachedDeploymentInfo 
> [sndId=a73e5cd4-c058-46b8-a3
> d9-cb0f4bbad5c1, ldrId=0fe3bb15941-a73e5cd4-c058-46b8-a3d9-cb0f4bbad5c1, 
> userVer=0, depMode=SHARED, participants=null]}]
> at 
> org.gridgain.grid.kernal.processors.cache.GridCacheDeploymentManager$CacheClassLoader.findClass(GridCacheDeploymentManager.java:786)
> at 
> org.gridgain.grid.kernal.processors.cache.GridCacheDeploymentManager$CacheClassLoader.loadClass(GridCacheDeploymentManager.java:743)
> at java.lang.Class.forName0(Native Method)
> at 

[jira] [Updated] (IGNITE-864) Visorcmd: new version checker prints it's output in visorcmd command prompt

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov updated IGNITE-864:

Fix Version/s: 1.6

> Visorcmd: new version checker prints it's output in visorcmd command prompt
> ---
>
> Key: IGNITE-864
> URL: https://issues.apache.org/jira/browse/IGNITE-864
> Project: Ignite
>  Issue Type: Bug
>  Components: UI
>Affects Versions: sprint-4
>Reporter: Pavel Konstantinov
>Assignee: Andrey Novikov
>Priority: Minor
> Fix For: 1.6
>
>
> {code}
> visor> [09:33:36] New version is available at 
> http://www.gridgain.com/download/editions: 1.0.2
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2286) Improve Metadata load from cache

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov updated IGNITE-2286:
-
Description: 
# Add option "Generate primitives in POJO for not null columns"+ tooltip with 
description
# Add option "Use Java builtin types as Key class" + tooltip with description 
when KeyClass generated and when it will be better to use java builtin types
# Add option to generate cache for each loaded type


  was:
# Add option "Generate primitives in POJO for not null columns"+ tooltip with 
description
# Add option "Use Java builtin types as Key class" + tooltip with description 
when KeyClass generated and when it will be better to use java builtin types



> Improve Metadata load from cache
> 
>
> Key: IGNITE-2286
> URL: https://issues.apache.org/jira/browse/IGNITE-2286
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Alexey Kuznetsov
> Fix For: 1.6
>
>
> # Add option "Generate primitives in POJO for not null columns"+ tooltip with 
> description
> # Add option "Use Java builtin types as Key class" + tooltip with description 
> when KeyClass generated and when it will be better to use java builtin types
> # Add option to generate cache for each loaded type



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2183) Broken UI after killing web agent

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov updated IGNITE-2183:
-
Fix Version/s: (was: 1.7)
   1.6

> Broken UI after killing web agent
> -
>
> Key: IGNITE-2183
> URL: https://issues.apache.org/jira/browse/IGNITE-2183
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
> Fix For: 1.6
>
> Attachments: ig-2183.png
>
>
> Some time after I'm killing web agent I'm getting a broken UI (please see 
> attachment)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (IGNITE-2080) JVM crashes on SunOS with SIGBUS (0xa) on frame [libjvm.so+0xc7c438] Unsafe_SetInt+0x14c

[Andrey Gura (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15070385#comment-15070385
 ] 

Andrey Gura edited comment on IGNITE-2080 at 12/25/15 6:40 PM:
---

{{GridUnsafeMap}} is fixed. But the following tests fail under Solaris:

  * {{GridCacheMemoryModeBinarySelfTest.testOffheapSwap}}
  * {{GridCacheMemoryModeBinarySelfTest.testTiered}}
  * {{GridCacheP2PUndeploySelfTest.testOffHeapP2PReplicated}} and other offheap 
related tests
  * {{GridUnsafeMemorySelfTest}}
  * {{GridUnsafeMapSelfTest}}
  * {{GridCacheMemoryModeSelfTest}}
  * {{GridUnsafePartitionedMapSelfTest}}
  * {{OptimizedObjectStreamSelfTest}}
  * {{OffHeapTieredTransactionSelfTest}}
  * {{GridEmbeddedFutureSelfTest}}
  * {{SocketStreamerSelfTest}}
  * {{GridCacheAbstractReduceFieldsQuerySelfTest.testIncludeBackups}}
  * {{GridCacheSwapScanQuerySelfTest}}
  * {{GridCacheValueBytesPreloadingSelfTest}}
  * {{CacheSerializableTransactionsTest}}

Failures don't related with JVM crash. Need to investigate.


was (Author: agura):
{{GridUnsafeMap}} is fixed. But the following tests fail under Solaris:

  * {{GridCacheMemoryModeBinarySelfTest.testOffheapSwap}}
  * {{GridCacheMemoryModeBinarySelfTest.testTiered}}
  * {{GridCacheP2PUndeploySelfTest.testOffHeapP2PReplicated}} and other offheap 
related tests
  * {{GridUnsafeMemorySelfTest}}
  * {{GridUnsafeMapSelfTest}}
  * {{GridCacheMemoryModeSelfTest}}
  * {{GridUnsafePartitionedMapSelfTest}}
  * {{OptimizedObjectStreamSelfTest}}
  * {{OffHeapTieredTransactionSelfTest}}
  * {{GridEmbeddedFutureSelfTest}}
  * {{SocketStreamerSelfTest}}
  * {{GridCacheAbstractReduceFieldsQuerySelfTest.testIncludeBackups}}
  * {{GridCacheSwapScanQuerySelfTest}}
  * {{GridCacheValueBytesPreloadingSelfTest}}

Failures don't related with JVM crash. Need to investigate.

> JVM crashes on SunOS with SIGBUS (0xa) on frame [libjvm.so+0xc7c438]  
> Unsafe_SetInt+0x14c
> -
>
> Key: IGNITE-2080
> URL: https://issues.apache.org/jira/browse/IGNITE-2080
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5, 1.4
> Environment: SunOS 5.11, JDK 7
>Reporter: Andrey Gura
>Assignee: Andrey Gura
> Fix For: 1.6
>
> Attachments: 054424_0_localhost.log, benchmark-offheap.properties, 
> hs_err_pid10523.log
>
>
> JVM crashes on SunOS 5.11 with the following message:
> {noformat}
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGBUS (0xa) at pc=0x76a7c438, pid=10523, tid=652
> #
> # JRE version: Java(TM) SE Runtime Environment (7.0_79-b15) (build 
> 1.7.0_79-b15)
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.79-b02 mixed mode 
> solaris-sparc )
> # Problematic frame:
> # V  [libjvm.so+0xc7c438]  Unsafe_SetInt+0x14c
> {noformat}
> Stack trace:
> {noformat}
> Stack: [0xfff0f6f0,0xfff0f700],  sp=0xfff0f6ffd1f0,  free 
> space=1012k
> Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native 
> code)
> V  [libjvm.so+0xc7c438]  Unsafe_SetInt+0x14c
> j  sun.misc.Unsafe.putInt(Ljava/lang/Object;JI)V+-1763873616
> j  sun.misc.Unsafe.putInt(Ljava/lang/Object;JI)V+0
> j  
> org.apache.ignite.internal.util.IgniteUtils.writeVersion([BJLorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;)J+135
> j  
> org.apache.ignite.internal.processors.cache.GridCacheSwapEntryImpl.marshal()[B+128
> j  
> org.apache.ignite.internal.processors.cache.GridCacheSwapManager.write(Lorg/apache/ignite/internal/processors/cache/KeyCacheObject;Ljava/nio/ByteBuffer;BLorg/apache/
> ignite/internal/processors/cache/version/GridCacheVersion;JJLorg/apache/ignite/lang/IgniteUuid;Lorg/apache/ignite/lang/IgniteUuid;)V+86
> j  org.apache.ignite.internal.processors.cache.GridCacheMapEntry.swap()V+333
> j  
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.evictInternal(ZLorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;[Lorg/apache/ignit
> e/internal/processors/cache/CacheEntryPredicate;)Z+122
> j  
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.evict0(Lorg/apache/ignite/internal/processors/cache/GridCacheAdapter;Lorg/apache/ignite/internal
> /processors/cache/GridCacheEntryEx;Lorg/apache/ignite/internal/processors/cache/version/GridCacheVersion;[Lorg/apache/ignite/internal/processors/cache/CacheEntryPredica
> te;Z)Z+117
> j  
> org.apache.ignite.internal.processors.cache.GridCacheEvictionManager.touch(Lorg/apache/ignite/internal/processors/cache/GridCacheEntryEx;Lorg/apache/ignite/internal/
> processors/affinity/AffinityTopologyVersion;)V+123
> j  
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.unlockEntries(Ljava/util/Collection;Lorg/apache/ignite/internal/processors/affi

[jira] [Commented] (IGNITE-1419) .Net: Add optional "raw" flag to binary type configuration.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15071586#comment-15071586
 ] 

ASF GitHub Bot commented on IGNITE-1419:


GitHub user ptupitsyn opened a pull request:

https://github.com/apache/ignite/pull/376

IGNITE-1419 .Net: Add optional "raw" flag to binary type configuration.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ptupitsyn/ignite ignite-1419

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/376.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #376


commit 49c298866b7c113aa62af4fe0587d6d39edd9f50
Author: sboikov 
Date:   2015-12-24T12:52:59Z

ignite-1.5 Fixed test.

commit 18c413c41b51994fb2eeaaebf4cf727049db0c8b
Author: vozerov-gridgain 
Date:   2015-12-25T06:48:28Z

IGNITE-2257: Fixed BinaryContext serialization.

commit edc0bd67f1003b50fde74ee3d8160909a2eb4a8c
Author: Pavel Tupitsyn 
Date:   2015-12-25T09:35:24Z

IGNITE-1419 .Net: Add optional "raw" flag to binary type configuration.

commit 34f5662919caa2099847a1e26ac0833bad4abfad
Author: Pavel Tupitsyn 
Date:   2015-12-25T09:41:40Z

wip Java

commit 4b87360e458607b44a5b1d9139ef9b0e05f0e570
Author: Pavel Tupitsyn 
Date:   2015-12-25T09:45:36Z

wip

commit 1882ada2a6e34975a47e47fc5a060c4d9b32cb0d
Author: Pavel Tupitsyn 
Date:   2015-12-25T09:46:51Z

wip

commit 28483646ab1cf0ba11f93dbf0b773d6c062de467
Author: Pavel Tupitsyn 
Date:   2015-12-25T10:05:09Z

wip

commit c6dfc28fdae9d3a1cf3c8ec940183638ae0f8231
Author: Pavel Tupitsyn 
Date:   2015-12-25T10:40:45Z

wip

commit 1e664132f4ccc1c240523637dc3392e1609c4aa6
Author: Pavel Tupitsyn 
Date:   2015-12-25T10:50:01Z

wip

commit 3d75004d3969aab625c90b42a5af9a94834488e4
Author: Pavel Tupitsyn 
Date:   2015-12-25T10:58:05Z

wip

commit 8f35db028f3c30f7d6b80744cda81e337a69e23a
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:06:08Z

wip

commit 802b5ad69230fd288734b6e5406cb29e9ad2a577
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:08:42Z

wip

commit 03f60ac14eecf9889543119fbd347d137d7d6ad2
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:09:59Z

wip

commit 375f57058665b15f2ab405cbbef5cab26662140e
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:21:00Z

wip test

commit 1c7958075ff71b75260b239902f4f00cb3ae3861
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:41:24Z

Test works

commit 876d1132517e63accbb4cc6118ae9cdc296bd85b
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:45:14Z

wip tests

commit 8f9c671291540f679b47e46146f3efcb0936963e
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:48:49Z

wip tests

commit 07e03db0134b632ee52bca23bf4a2977dd33a18c
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:49:51Z

wip tests

commit f7c1ddda8cda98a7c2ac38f742419de940d87686
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:51:51Z

wip

commit cb9ef1bbe6255907392dd6326327f728b368fd61
Author: Pavel Tupitsyn 
Date:   2015-12-25T11:54:47Z

Fix npe in collections




> .Net: Add optional "raw" flag to binary type configuration.
> ---
>
> Key: IGNITE-1419
> URL: https://issues.apache.org/jira/browse/IGNITE-1419
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
>
> By default we write .Net objects with field names included. But in some cases 
> it is not needed. E.g. when objects are not going to be used in queries.
> Removing field names will speed up serialization/deserialization. We can add 
> optional "raw" flag to portable type descriptor to control this behavior.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-1419) .Net: Add optional "raw" flag to binary type configuration.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15071587#comment-15071587
 ] 

ASF GitHub Bot commented on IGNITE-1419:


Github user ptupitsyn closed the pull request at:

https://github.com/apache/ignite/pull/376


> .Net: Add optional "raw" flag to binary type configuration.
> ---
>
> Key: IGNITE-1419
> URL: https://issues.apache.org/jira/browse/IGNITE-1419
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
>
> By default we write .Net objects with field names included. But in some cases 
> it is not needed. E.g. when objects are not going to be used in queries.
> Removing field names will speed up serialization/deserialization. We can add 
> optional "raw" flag to portable type descriptor to control this behavior.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-2166) .NET: Add toBuilder() method on BinaryObject interface.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15071609#comment-15071609
 ] 

ASF GitHub Bot commented on IGNITE-2166:


GitHub user ptupitsyn opened a pull request:

https://github.com/apache/ignite/pull/379

IGNITE-2166 .NET: Add toBuilder() method on BinaryObject interface.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ptupitsyn/ignite ignite-2166

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/379.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #379


commit a95fd8feeff825059f037102d233e03019f381b4
Author: Pavel Tupitsyn 
Date:   2015-12-25T13:05:01Z

IGNITE-2166 .NET: Add toBuilder() method on BinaryObject interface.

commit 7f6d34eb343f3401b158b6840a3a362640834d12
Author: Pavel Tupitsyn 
Date:   2015-12-25T13:09:27Z

Tests updated




> .NET: Add toBuilder() method on BinaryObject interface.
> ---
>
> Key: IGNITE-2166
> URL: https://issues.apache.org/jira/browse/IGNITE-2166
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
> Fix For: 1.6
>
>
> Port IGNITE-2138 to .NET.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-2161) We need to tune Ignite site CSS to make it looks good for printing

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov reassigned IGNITE-2161:


Assignee: Pavel Konstantinov  (was: Alexey Kuznetsov)

Please test site apache.ignite.com in print preview looks more or less normal 
in major modern browsers (chrome, safari, FF, ie, edge).
And test print to PDF file.

> We need to tune Ignite site CSS to make it looks good for printing
> --
>
> Key: IGNITE-2161
> URL: https://issues.apache.org/jira/browse/IGNITE-2161
> Project: Ignite
>  Issue Type: Bug
>  Components: website
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
> Fix For: 1.5
>
>
> Open in chrome https://ignite.apache.org/benchmarks/ignite-vs-hazelcast.html
> Click Print -> looks ugly.
> See some ideas here: 
> http://www.creativebloq.com/responsive-web-design/make-your-website-printable-css-3132929



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-2285) .Net: Add ICache.GetDataStreamer

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15071643#comment-15071643
 ] 

ASF GitHub Bot commented on IGNITE-2285:


GitHub user ptupitsyn opened a pull request:

https://github.com/apache/ignite/pull/381

IGNITE-2285 .Net: Add ICache.GetDataStreamer



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ptupitsyn/ignite ignite-2285

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/381.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #381


commit 54fc8818bab7078e4a3bbe3764b2b064f4092061
Author: Pavel Tupitsyn 
Date:   2015-12-25T15:11:37Z

IGNITE-2285 .Net: Add ICache.GetDataStreamer




> .Net: Add ICache.GetDataStreamer
> 
>
> Key: IGNITE-2285
> URL: https://issues.apache.org/jira/browse/IGNITE-2285
> Project: Ignite
>  Issue Type: Improvement
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Fix For: 1.6
>
>
> Currently we have IIgnite.GetDataStreamer, where user has to specify cache 
> name and generic arguments.
> ICache.GetDataStreamer will infer both cache name and generic types for the 
> user.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-2016) Update KafkaStreamer to fit new features introduced in Kafka 0.9

[Denis Magda (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15071500#comment-15071500
 ] 

Denis Magda commented on IGNITE-2016:
-

Roman,

According to {{SinkTask.put(...)}} API
http://docs.confluent.io/2.0.0/connect/javadocs/org/apache/kafka/connect/sink/SinkTask.html#put(java.util.Collection)
There is no need to buffer the data waiting for {{SinkTask.flush()}} to be 
called. It's ok and in my opinion preferable to start sending the data 
asynchronously.

I got your idea and concerns regarding the case when something going wrong 
during the streaming and we want to let Kafka know to continue streaming from 
some offset. However to overcome this issue we still can rely on 
{{IgniteDataStreamer}}. Just call {{IgniteDataStreamer.flush()}} in the 
implementation of your sink's flush method. This will ensure that the streamer 
has already flushed all the data properly at the time when implementation of 
your {{flush}} method returns.

Makes sense?

> Update KafkaStreamer to fit new features introduced in Kafka 0.9
> 
>
> Key: IGNITE-2016
> URL: https://issues.apache.org/jira/browse/IGNITE-2016
> Project: Ignite
>  Issue Type: New Feature
>  Components: streaming
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>
> Particularly,
> - new consumer
> - Kafka Connect (Copycat)
> http://www.confluent.io/blog/apache-kafka-0.9-is-released
> This can be a a different integration task or a complete re-write of the 
> current implementation, considering the fact that Kafka Connect is a new 
> standard way for "large-scale, real-time data import and export for Kafka."



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-2166) .NET: Add toBuilder() method on BinaryObject interface.

[Pavel Tupitsyn (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn reassigned IGNITE-2166:
--

Assignee: Pavel Tupitsyn

> .NET: Add toBuilder() method on BinaryObject interface.
> ---
>
> Key: IGNITE-2166
> URL: https://issues.apache.org/jira/browse/IGNITE-2166
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
> Fix For: 1.6
>
>
> Port IGNITE-2138 to .NET.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-1413) .Net: Get rid of set -> map conversion in PlatformDotNetCacheStore.writeAll

[Pavel Tupitsyn (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn reassigned IGNITE-1413:
--

Assignee: Pavel Tupitsyn

> .Net: Get rid of set -> map conversion in PlatformDotNetCacheStore.writeAll
> ---
>
> Key: IGNITE-1413
> URL: https://issues.apache.org/jira/browse/IGNITE-1413
> Project: Ignite
>  Issue Type: Task
>  Components: interop
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
>
> This is a legacy artifact from a veeery old API which is currently removed. 
> Just pass set without unnecessary conversions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-184) visorcmd: improve auto-calculation of width of table columns

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov updated IGNITE-184:

Fix Version/s: 1.6

> visorcmd: improve auto-calculation of width of table columns
> 
>
> Key: IGNITE-184
> URL: https://issues.apache.org/jira/browse/IGNITE-184
> Project: Ignite
>  Issue Type: Task
>  Components: UI
>Affects Versions: sprint-1
> Environment: I suggest to use following logic:
> if parameter value is a set of values separated by space then print this 
> separated values from new line
> Use terminal width to determine table columns maximum width
>Reporter: Alexey Kuznetsov
>Assignee: Andrey Novikov
> Fix For: 1.6
>
> Attachments: gg-8723.png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-184) visorcmd: improve auto-calculation of width of table columns

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov reassigned IGNITE-184:
---

Assignee: (was: Andrey Novikov)

> visorcmd: improve auto-calculation of width of table columns
> 
>
> Key: IGNITE-184
> URL: https://issues.apache.org/jira/browse/IGNITE-184
> Project: Ignite
>  Issue Type: Task
>  Components: UI
>Affects Versions: sprint-1
> Environment: I suggest to use following logic:
> if parameter value is a set of values separated by space then print this 
> separated values from new line
> Use terminal width to determine table columns maximum width
>Reporter: Alexey Kuznetsov
> Fix For: 1.6
>
> Attachments: gg-8723.png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-336) We need to add dynamic turn on/off cache statistics for Visor.

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov updated IGNITE-336:

Fix Version/s: 1.6

> We need to add dynamic turn on/off cache statistics for Visor.
> --
>
> Key: IGNITE-336
> URL: https://issues.apache.org/jira/browse/IGNITE-336
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-2
>Reporter: Vasiliy Sisko
>Assignee: Vasiliy Sisko
> Fix For: 1.6
>
>
> We need create task to turn on/off of cache statistics collecting.
> Create Visor command for toggling.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-944) HTTP REST log command doesn't work

[Saikat Maitra (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15071652#comment-15071652
 ] 

Saikat Maitra commented on IGNITE-944:
--

Chandresh,

Can you please confirm if you are currently working on this ticket or if it is 
ok if I take it up.

Regards
Saikat

> HTTP REST log command doesn't work
> --
>
> Key: IGNITE-944
> URL: https://issues.apache.org/jira/browse/IGNITE-944
> Project: Ignite
>  Issue Type: Bug
>  Components: general, newbie
>Affects Versions: sprint-5
>Reporter: Sergey Kozlov
>Assignee: Chandresh Pancholi
>
> Request http://localhost:8080/ignite?cmd=log=1=0 returns following
> {noformat}
> {"error":"Failed to find registered handler for command: 
> LOG","response":null,"sessionToken":"","successStatus":1}
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-2016) Update KafkaStreamer to fit new features introduced in Kafka 0.9

[Roman Shtykh (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15071613#comment-15071613
 ] 

Roman Shtykh commented on IGNITE-2016:
--

Denis,

Yes, it makes sense. Thank you.

The only remaining issue is using autoflushing. We already invoke 
_IgniteDataStreamer.flush()_ on _SinkTask.put(...)_, which interval can be 
configured by the user.
Therefore I think we don't need to expose __IgniteDataStreamer_'s autoflushing. 
Do you agree?

As to buffering on _SinkTask.put(...)_ and then flushing, it is needed to 
increase throughput (pretty common). It is needed only in case we use 
_cache.putAll(...)_, which was my first solution.
_In fact, in many cases internal buffering will be useful so an entire batch of 
records can be sent at once, reducing the overhead of inserting events into the 
downstream data store._ http://kafka.apache.org/documentation.html#connect
As I understand, the same thing is achieved _IgniteDataStreamer_ and, since we 
go with it, explicit buffering is not needed anymore ;)


> Update KafkaStreamer to fit new features introduced in Kafka 0.9
> 
>
> Key: IGNITE-2016
> URL: https://issues.apache.org/jira/browse/IGNITE-2016
> Project: Ignite
>  Issue Type: New Feature
>  Components: streaming
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>
> Particularly,
> - new consumer
> - Kafka Connect (Copycat)
> http://www.confluent.io/blog/apache-kafka-0.9-is-released
> This can be a a different integration task or a complete re-write of the 
> current implementation, considering the fact that Kafka Connect is a new 
> standard way for "large-scale, real-time data import and export for Kafka."



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-944) HTTP REST log command doesn't work

[Chandresh Pancholi (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15071655#comment-15071655
 ] 

Chandresh Pancholi commented on IGNITE-944:
---

Sure Saikat.
Go ahead.

> HTTP REST log command doesn't work
> --
>
> Key: IGNITE-944
> URL: https://issues.apache.org/jira/browse/IGNITE-944
> Project: Ignite
>  Issue Type: Bug
>  Components: general, newbie
>Affects Versions: sprint-5
>Reporter: Sergey Kozlov
>Assignee: Chandresh Pancholi
>
> Request http://localhost:8080/ignite?cmd=log=1=0 returns following
> {noformat}
> {"error":"Failed to find registered handler for command: 
> LOG","response":null,"sessionToken":"","successStatus":1}
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-1903) CacheStore implementation is serialised to grid clients whether they require it or not

[Denis Magda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Denis Magda updated IGNITE-1903:

Priority: Critical  (was: Major)

> CacheStore implementation is serialised to grid clients whether they require 
> it or not
> --
>
> Key: IGNITE-1903
> URL: https://issues.apache.org/jira/browse/IGNITE-1903
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5
>Reporter: Michael Griggs
>Assignee: Denis Magda
>Priority: Critical
> Fix For: 1.6
>
>
> See User discussion thread:  
> http://apache-ignite-users.70518.x6.nabble.com/CacheStore-being-serialized-to-client-td1931.html
> Brief summary:  When a grid client joins the grid (clientMode=true) it 
> receives a message from the server node(s) on the grid that contains the 
> serialized CacheStore implementation object.  If the client does not have 
> this class on its CLASSPATH (and there is no reason it should, as it is a 
> client) then the de-serialization of this message will fail, causing this 
> exception:
> {code}SEVERE: Failed to unmarshal discovery data for component: 1 
> class org.apache.ignite.IgniteCheckedException: Failed to find class with 
> given class loader for unmarshalling (make sure same versions of all classes 
> are available on all nodes or enable peer-class-loading): 
> sun.misc.Launcher$AppClassLoader@14dad5dc 
> at 
> org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal(JdkMarshaller.java:104)
>  
> at 
> org.apache.ignite.marshaller.AbstractMarshaller.unmarshal(AbstractMarshaller.java:67)
>  
> at 
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDiscoverySpi.java:1529)
>  
> at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processNodeAddFinishedMessage(ClientImpl.java:1317)
>  
> at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1229)
>  
> at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1199)
>  
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62) 
> Caused by: java.lang.ClassNotFoundException: 
> c.g.r.cachewrapper.ignite.CacheMissHandlerIgnite
> {code}
> where {{c.g.r.cachewrapper.ignite.CacheMissHandlerIgnite}} is the CacheStore 
> implementation.
> The ostensible reason for the CacheStore serialization is so that clients of 
> a TRANSACTIONAL cache can begin the transaction on the underlying store.  
> The only current solution to this is to add the grid node's CacheStore 
> implementation class definition to the CLASSPATH of the client.  This creates 
> an *undesirable coupling* between server and client.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-2281) We need to save content in tables on focus lost and not force user to click "disk" icon

[Vasiliy Sisko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vasiliy Sisko reassigned IGNITE-2281:
-

Assignee: Vasiliy Sisko

> We need to save content in tables on focus lost and not force user to click 
> "disk" icon
> ---
>
> Key: IGNITE-2281
> URL: https://issues.apache.org/jira/browse/IGNITE-2281
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Vasiliy Sisko
> Fix For: 1.6
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2291) Sql query dialog has incorrect position

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-2291:
--

 Summary: Sql query dialog has incorrect position
 Key: IGNITE-2291
 URL: https://issues.apache.org/jira/browse/IGNITE-2291
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Konstantinov
Assignee: Dmitriyff
Priority: Trivial


I think it should appear at the center of the screen



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2291) Sql query dialog has incorrect position

[Pavel Konstantinov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov updated IGNITE-2291:
---
Description: I think it should appear at the center of the screen 
(currently at the top)  (was: I think it should appear at the center of the 
screen)

> Sql query dialog has incorrect position
> ---
>
> Key: IGNITE-2291
> URL: https://issues.apache.org/jira/browse/IGNITE-2291
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Dmitriyff
>Priority: Trivial
> Fix For: 1.6
>
>
> I think it should appear at the center of the screen (currently at the top)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (IGNITE-2183) Broken UI after killing web agent

[Pavel Konstantinov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov resolved IGNITE-2183.

Resolution: Fixed

> Broken UI after killing web agent
> -
>
> Key: IGNITE-2183
> URL: https://issues.apache.org/jira/browse/IGNITE-2183
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
> Fix For: 1.6
>
> Attachments: ig-2183.png
>
>
> Some time after I'm killing web agent I'm getting a broken UI (please see 
> attachment)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-2016) Update KafkaStreamer to fit new features introduced in Kafka 0.9

[Denis Magda (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15071825#comment-15071825
 ] 

Denis Magda commented on IGNITE-2016:
-

Roman,

Agree, there is no need to setup auto-flushing on IgniteDataStreamer size since 
Kafka will call {{IgniteDataStreamer.flush()}} periodically.
Moreover, IgniteDataStreamer's buffers will be flushed automatically when 
{{IgniteDataStreamer.perNodeBufferSize}} is reached meaning that the streamer 
doesn't need to wait until the flush is called and can push data to a cache 
asynchronously. Default value of {{IgniteDataStreamer.perNodeBufferSize}} is 
1024 and I think it's ok to leave it as is not exposing an additional 
configuration parameter for the user. It can be added in the future if needed.

So, summarizing I have the following pseudo-code in my head how implementation 
of {{IgniteSinkTask}} {{put}} and {{flush}} basing on {{IgniteDataStreamer}} 
should look like omitting details.

{noformat}
public class IgniteSinkTask extends SinkTask {
/** Cache data streamer. */
IgniteDataStreamer ds;

/**
 * Buffers records.
 *
 * @param records Records to inject into grid.
 */
@Override public void put(Collection records) {
for (SinkRecord record : records) {
if (record.key() != null)
// Data will be flushed asynchronously when 
IgniteDataStreamer.perNodeBufferSize is reached
ds.addData(record.key(), record.value());
}
}

/**
 * Pushes buffered data to grid. Flush interval is configured by worker 
configurations.
 *
 * @param offsets Offset information.
 */
@Override public void flush(Map offsets) 
{
// Flushing any pending data in the streamer.
ds.flush();
}
}
{noformat}

> Update KafkaStreamer to fit new features introduced in Kafka 0.9
> 
>
> Key: IGNITE-2016
> URL: https://issues.apache.org/jira/browse/IGNITE-2016
> Project: Ignite
>  Issue Type: New Feature
>  Components: streaming
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>
> Particularly,
> - new consumer
> - Kafka Connect (Copycat)
> http://www.confluent.io/blog/apache-kafka-0.9-is-released
> This can be a a different integration task or a complete re-write of the 
> current implementation, considering the fact that Kafka Connect is a new 
> standard way for "large-scale, real-time data import and export for Kafka."



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2289) Eviction policy doesn't work with OFFHEAP_VALUES mode

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-2289:
---

 Summary: Eviction policy doesn't work with OFFHEAP_VALUES mode
 Key: IGNITE-2289
 URL: https://issues.apache.org/jira/browse/IGNITE-2289
 Project: Ignite
  Issue Type: Bug
  Components: cache
Reporter: Valentin Kulichenko
 Fix For: 1.6


For issue description and the test refer to this discussion: 
http://apache-ignite-users.70518.x6.nabble.com/Eviction-for-OFFHEAP-TIERED-vs-OFFHEAP-VALUES-td2302.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (IGNITE-2217) Add BinaryConfiguration support to cluster screen

[Pavel Konstantinov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov closed IGNITE-2217.
--
Assignee: (was: Pavel Konstantinov)

Tested.

> Add BinaryConfiguration support to cluster screen
> -
>
> Key: IGNITE-2217
> URL: https://issues.apache.org/jira/browse/IGNITE-2217
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Alexey Kuznetsov
> Fix For: 1.6
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-2290) Section title has no 'hand' mouse pointer

[Pavel Konstantinov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov updated IGNITE-2290:
---
Summary: Section title has no 'hand' mouse pointer  (was: Section title has 
no 'hand' mouse point )

> Section title has no 'hand' mouse pointer
> -
>
> Key: IGNITE-2290
> URL: https://issues.apache.org/jira/browse/IGNITE-2290
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Dmitriyff
>Priority: Trivial
> Fix For: 1.6
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2290) Section title has no 'hand' mouse point

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-2290:
--

 Summary: Section title has no 'hand' mouse point 
 Key: IGNITE-2290
 URL: https://issues.apache.org/jira/browse/IGNITE-2290
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Konstantinov
Assignee: Dmitriyff
Priority: Trivial






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Reopened] (IGNITE-2161) We need to tune Ignite site CSS to make it looks good for printing

[Pavel Konstantinov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov reopened IGNITE-2161:

  Assignee: Dmitriyff  (was: Pavel Konstantinov)

Please fix 'SQL query benchmarks' page layout

> We need to tune Ignite site CSS to make it looks good for printing
> --
>
> Key: IGNITE-2161
> URL: https://issues.apache.org/jira/browse/IGNITE-2161
> Project: Ignite
>  Issue Type: Bug
>  Components: website
>Reporter: Alexey Kuznetsov
>Assignee: Dmitriyff
> Fix For: 1.5
>
>
> Open in chrome https://ignite.apache.org/benchmarks/ignite-vs-hazelcast.html
> Click Print -> looks ugly.
> See some ideas here: 
> http://www.creativebloq.com/responsive-web-design/make-your-website-printable-css-3132929



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (IGNITE-2183) Broken UI after killing web agent

[Pavel Konstantinov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov closed IGNITE-2183.
--
Assignee: (was: Pavel Konstantinov)

I was not able to reproduce one more time.
Will consider this is fixed.

> Broken UI after killing web agent
> -
>
> Key: IGNITE-2183
> URL: https://issues.apache.org/jira/browse/IGNITE-2183
> Project: Ignite
>  Issue Type: Sub-task
>  Components: wizards
>Reporter: Pavel Konstantinov
> Fix For: 1.6
>
> Attachments: ig-2183.png
>
>
> Some time after I'm killing web agent I'm getting a broken UI (please see 
> attachment)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (IGNITE-2161) We need to tune Ignite site CSS to make it looks good for printing

[Dmitriyff (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriyff resolved IGNITE-2161.
---
Resolution: Fixed
  Assignee: Pavel Konstantinov  (was: Dmitriyff)

> We need to tune Ignite site CSS to make it looks good for printing
> --
>
> Key: IGNITE-2161
> URL: https://issues.apache.org/jira/browse/IGNITE-2161
> Project: Ignite
>  Issue Type: Bug
>  Components: website
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
> Fix For: 1.5
>
>
> Open in chrome https://ignite.apache.org/benchmarks/ignite-vs-hazelcast.html
> Click Print -> looks ugly.
> See some ideas here: 
> http://www.creativebloq.com/responsive-web-design/make-your-website-printable-css-3132929



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)