[jira] [Created] (IGNITE-1760) .Net: Validate field type in PortableReaderImpl

Pavel Tupitsyn created IGNITE-1760: --- Summary: .Net: Validate field type in PortableReaderImpl Key: IGNITE-1760 URL: https://issues.apache.org/jira/browse/IGNITE-1760 Project: Ignite Issue

Re: Data Snapshots in Ignite

On Wed, Oct 21, 2015 at 05:58PM, Dmitriy Setrakyan wrote: > On Wed, Oct 21, 2015 at 4:48 PM, Konstantin Boudnik wrote: > > > I like it quite a bit, as well! Ticket would make the most sense as well, > > so > > there will be a single place to collect the design docs (if needed),

Re: Ignite Web Console - Loading metadata from MySQL

Prachi, I'm assuming that you have MySQL database up and running and know JDBC URL for you database (it should looks like: jdbc:mysql://[host]:[port]/[database]). You should copy MySQL JDBC driver jar into " folder_where_agent_unzipped/jdbc-drivers". Latest MySQL JDBC driver should looks like

Re: Data Snapshots in Ignite

On Wed, Oct 21, 2015 at 4:48 PM, Konstantin Boudnik wrote: > I like it quite a bit, as well! Ticket would make the most sense as well, > so > there will be a single place to collect the design docs (if needed), etc. > > On Wed, Oct 21, 2015 at 04:45PM, Dmitriy Setrakyan wrote: >

Re: TC patch validation

I think Cos’ question also was why the patches attached to Jira do not get automatically run on TC. To my knowledge, the automatic runs were disabled, but I am not sure if it includes patches as well. Can someone clarify how to run patches on TC? D. On Fri, Oct 16, 2015 at 2:16 AM, Ivan

[jira] [Created] (IGNITE-1759) .Net: Guid read/write is not platform-safe.

Vladimir Ozerov created IGNITE-1759: --- Summary: .Net: Guid read/write is not platform-safe. Key: IGNITE-1759 URL: https://issues.apache.org/jira/browse/IGNITE-1759 Project: Ignite Issue

Re: Data Snapshots in Ignite

I also really like the idea. One potential use case is fraud analysis in financial institutions. Rarely it makes sense to perform such analysis on a life system, but rather a snapshot of some data needs to be taken and analyzed offline. I think snapshots should be saved to disk, so users could

Re: Data Snapshots in Ignite

I like it quite a bit, as well! Ticket would make the most sense as well, so there will be a single place to collect the design docs (if needed), etc. On Wed, Oct 21, 2015 at 04:45PM, Dmitriy Setrakyan wrote: > I also really like the idea. One potential use case is fraud analysis in > financial

Ignite Web Console - Loading metadata from MySQL

I am trying to load metadata from MySQL database, but the web console doesn't allow me to provide the MySQL driver JAR. It is set to H2, by default, and doesn't let me change. I tried running the Ignite web agent in both test and non-test modes. How can I provide the MySQL driver JAR? Thanks,

[jira] [Created] (IGNITE-1761) Load metadata from DB: add possibility to set JDBC driver jar file from local folder

Pavel Konstantinov created IGNITE-1761: -- Summary: Load metadata from DB: add possibility to set JDBC driver jar file from local folder Key: IGNITE-1761 URL: https://issues.apache.org/jira/browse/IGNITE-1761

Re: Data Snapshots in Ignite

Some time ago we already discussed snapshots idea while discussing library "cqengine" [1]. May be this library could be useful in snapshot mode. [1] Sources: https://github.com/npgall/cqengine Docs: https://code.google.com/p/cqengine/ On Thu, Oct 22, 2015 at 8:48 AM, Konstantin Boudnik

[jira] [Created] (IGNITE-1762) Chart settings should be preserved between chats type switch

Alexey Kuznetsov created IGNITE-1762: Summary: Chart settings should be preserved between chats type switch Key: IGNITE-1762 URL: https://issues.apache.org/jira/browse/IGNITE-1762 Project: Ignite

Data Snapshots in Ignite

Hey guys, LevelDb has a functionality called Snapshots which provides a consistent read-only view of the DB at a given point in time, against which queries can be executed. To my knowledge, this functionality doesn't exist in the world of open source In-Memory Computing. Ignite could be an

[jira] [Created] (IGNITE-1753) Rework CacheJdbcPojoStore to new API.

Alexey Kuznetsov created IGNITE-1753: Summary: Rework CacheJdbcPojoStore to new API. Key: IGNITE-1753 URL: https://issues.apache.org/jira/browse/IGNITE-1753 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-1754) SQL: Issue with area chart

Pavel Konstantinov created IGNITE-1754: -- Summary: SQL: Issue with area chart Key: IGNITE-1754 URL: https://issues.apache.org/jira/browse/IGNITE-1754 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-1757) [Failed test] CacheHibernateBlobStoreSelfTest.testSimpleMultithreading fails on TC sometimes

Artem Shutak created IGNITE-1757: Summary: [Failed test] CacheHibernateBlobStoreSelfTest.testSimpleMultithreading fails on TC sometimes Key: IGNITE-1757 URL: https://issues.apache.org/jira/browse/IGNITE-1757

Re: Data Snapshots in Ignite

Raul, Actually SQL indexes are already snapshotable. I'm not sure if it does make sense to make the whole cache (with full cache API support) snapshotable, but I like your idea about running multiple SQL statements against the same snapshot. Also I don't think that it is a good idea to keep

[jira] [Created] (IGNITE-1758) Clients don't survive during massive servers shutdown

Denis Magda created IGNITE-1758: --- Summary: Clients don't survive during massive servers shutdown Key: IGNITE-1758 URL: https://issues.apache.org/jira/browse/IGNITE-1758 Project: Ignite Issue

[jira] [Created] (IGNITE-1756) [Test Failed] GridCacheAtomicOffHeapTieredMultiNodeFullApiSelfTest.testIgniteCacheIterator fails sometimes

Artem Shutak created IGNITE-1756: Summary: [Test Failed] GridCacheAtomicOffHeapTieredMultiNodeFullApiSelfTest.testIgniteCacheIterator fails sometimes Key: IGNITE-1756 URL:

[jira] [Created] (IGNITE-1751) Spinning wheel artifacts

Pavel Konstantinov created IGNITE-1751: -- Summary: Spinning wheel artifacts Key: IGNITE-1751 URL: https://issues.apache.org/jira/browse/IGNITE-1751 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-1750) Missed placeholders in cluster configuration

Pavel Konstantinov created IGNITE-1750: -- Summary: Missed placeholders in cluster configuration Key: IGNITE-1750 URL: https://issues.apache.org/jira/browse/IGNITE-1750 Project: Ignite

[jira] [Created] (IGNITE-1752) Too many space between Notebook name and Edit\Remove buttons

Pavel Konstantinov created IGNITE-1752: -- Summary: Too many space between Notebook name and Edit\Remove buttons Key: IGNITE-1752 URL: https://issues.apache.org/jira/browse/IGNITE-1752 Project: