[jira] [Created] (IGNITE-1766) Zooming of charts

Pavel Konstantinov created IGNITE-1766: -- Summary: Zooming of charts Key: IGNITE-1766 URL: https://issues.apache.org/jira/browse/IGNITE-1766 Project: Ignite Issue Type: Sub-task

Re: Ignite Web Console - Loading metadata from MySQL

On Wed, Oct 21, 2015 at 5:08 PM, Prachi Garg wrote: > 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 >

[jira] [Created] (IGNITE-1768) .Net: Review portable configuration on Java side.

Vladimir Ozerov created IGNITE-1768: --- Summary: .Net: Review portable configuration on Java side. Key: IGNITE-1768 URL: https://issues.apache.org/jira/browse/IGNITE-1768 Project: Ignite

[jira] [Created] (IGNITE-1764) Insufficient width for label on Y-axis in case of large values

Pavel Konstantinov created IGNITE-1764: -- Summary: Insufficient width for label on Y-axis in case of large values Key: IGNITE-1764 URL: https://issues.apache.org/jira/browse/IGNITE-1764 Project:

Re: TC patch validation

On Thu, Oct 22, 2015 at 01:28PM, Artem Shutak wrote: > Yes, automatic runs were disabled for patches too. > > To run patches you can use "Run All for patch" with specified jira number > at "Paramethers / Jira number*". Right, that presumes that a user has an account. I am sure I have one, but I

Re: MQTT Streamer Code Style and Javadoc fixes (IGNITE-1747)

Raul, Thanks for your contribution! I want to address the coding guidelines comments, as they keep coming up again and again. I do agree that coding guidelines may not be ideal, and may seem redundant at times. However, they make Ignite code look consistent. If you try to change them now, even

[jira] [Created] (IGNITE-1778) IGFS: implement rollback procedure: cleanup the "reserved" data.

Ivan Veselovsky created IGNITE-1778: --- Summary: IGFS: implement rollback procedure: cleanup the "reserved" data. Key: IGNITE-1778 URL: https://issues.apache.org/jira/browse/IGNITE-1778 Project:

Re: IGNITE-1371 patch is ready

Hi Igor, Please, see my comments in the Jira. -- Artem -- On Wed, Oct 21, 2015 at 3:50 AM, Igor Rudyak wrote: > Hi guys, > > I attached patch for IGNITE-1371 on a previous week, but looks like it > wasn't taken into consideration. > > I am assuming that may be I forgot to

Re: MQTT Streamer Code Style and Javadoc fixes (IGNITE-1747)

Hi Yakov, Thanks for the review. Comments inline. Aside from them: being honest, do you think Javadoc like the following snippets are useful and provide any value? More so in a test case... Snippet #1: /** * @param topics Topics. * @param fromIdx From index. * @param cnt

Re: MQTT Streamer Code Style and Javadoc fixes (IGNITE-1747)

Raul, It wasn't easy for me to get into the way of following Ignite coding guidelines. So you're not alone :) However one day I found "ignite/idea/ignite_codeStyle.xml" file and set it in Intellij IDEA settings. Since that time coding guidelines has never worried me again. Probably this

[jira] [Created] (IGNITE-1777) IGFS: write files with fail-safe logic: "lock" -> "reserve space" -> "write" -> "size update, unlock"

Ivan Veselovsky created IGNITE-1777: --- Summary: IGFS: write files with fail-safe logic: "lock" -> "reserve space" -> "write" -> "size update, unlock" Key: IGNITE-1777 URL:

Re: Ignite Web Console - Loading metadata from MySQL

On Thu, Oct 22, 2015 at 11:06 AM, Prachi Garg wrote: > Thanks! > > I think we should also provide an option on the client side for the user to > browse to the local folder of his system. > I really like this idea. I think it fits into the current architecture perfectly. >

Re: MQTT Streamer Code Style and Javadoc fixes (IGNITE-1747)

Hey Denis, Yep, I've been using the Ignite code style for IntelliJ since the beginning. It's ok for indentation, whitespacing, line breaks, etc. But things too specific like abbreviations, string outputs, Javadoc conventions like using {@code ...}, etc. are not covered. checkstyle is a

[GitHub] ignite pull request: IGNITE-1371 implemented

GitHub user irudyak opened a pull request: https://github.com/apache/ignite/pull/172 IGNITE-1371 implemented You can merge this pull request into a Git repository by running: $ git pull https://github.com/irudyak/ignite ignite-1371 Alternatively you can review and apply

[jira] [Created] (IGNITE-1769) We must close the current query on server-side when user start new one

Pavel Konstantinov created IGNITE-1769: -- Summary: We must close the current query on server-side when user start new one Key: IGNITE-1769 URL: https://issues.apache.org/jira/browse/IGNITE-1769

[jira] [Created] (IGNITE-1770) Portables: implement constant-time field lookup.

Vladimir Ozerov created IGNITE-1770: --- Summary: Portables: implement constant-time field lookup. Key: IGNITE-1770 URL: https://issues.apache.org/jira/browse/IGNITE-1770 Project: Ignite

[jira] [Created] (IGNITE-1771) Ignite should support Apache Spark 1.5.1

Artem Shutak created IGNITE-1771: Summary: Ignite should support Apache Spark 1.5.1 Key: IGNITE-1771 URL: https://issues.apache.org/jira/browse/IGNITE-1771 Project: Ignite Issue Type: Bug

[GitHub] ignite pull request: IGNITE-1759 .Net: Guid read/write is not plat...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/171 IGNITE-1759 .Net: Guid read/write is not platform-safe. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-1759

Re: TC patch validation

Yes, automatic runs were disabled for patches too. To run patches you can use "Run All for patch" with specified jira number at "Paramethers / Jira number*". -- Artem -- On Thu, Oct 22, 2015 at 4:11 AM, Dmitriy Setrakyan wrote: > I think Cos’ question also was why the

[jira] [Created] (IGNITE-1776) [Test Failed] TcpClientDiscoverySpiSelfTest.testClientNodeFailOneServer fails sometimes

Artem Shutak created IGNITE-1776: Summary: [Test Failed] TcpClientDiscoverySpiSelfTest.testClientNodeFailOneServer fails sometimes Key: IGNITE-1776 URL: https://issues.apache.org/jira/browse/IGNITE-1776

[jira] [Created] (IGNITE-1775) Show Y-columns in chart settings with same color as chart

Alexey Kuznetsov created IGNITE-1775: Summary: Show Y-columns in chart settings with same color as chart Key: IGNITE-1775 URL: https://issues.apache.org/jira/browse/IGNITE-1775 Project: Ignite

Re: Data Snapshots in Ignite

I have a specific use-case for snapshots that my current client would want to make use of, it may be helpful if I share it with you. At the start of day we make a batch load from a reference data system, and run a set of Start-Of-Day (SOD) reports. Those reports must be on a consistent view of

[jira] [Created] (IGNITE-1774) REST API should be implemented using Jersey

Michael Griggs created IGNITE-1774: -- Summary: REST API should be implemented using Jersey Key: IGNITE-1774 URL: https://issues.apache.org/jira/browse/IGNITE-1774 Project: Ignite Issue Type:

Re: Ignite Web Console - Loading metadata from MySQL

Prachi, If this issue: https://issues.apache.org/jira/browse/IGNITE-1761 Is the same as you propose? P.S. Did you managed to load metadata from your MySQL database? On Fri, Oct 23, 2015 at 1:06 AM, Prachi Garg wrote: > Thanks! > > I think we should also provide an option

Re: Data Snapshots in Ignite

Hey Andre, I think I answered some of your questions in my response to Dmitriy [1]. Could you please have a look and tell me if it answers your questions? N.B.: My idea is based around the typical use case for LevelDb Snapshots, but we might create something entirely different in Ignite if the

Re: Data Snapshots in Ignite

Hey Dmitry, Actually, there are so many possibilities around snapshotting that we're thinking about what I feel are two distinct functionalities ;-) While persistent snapshotting is indeed useful, what you describe is a mechanism somewhere in the spectrum between archiving and backups, right? I

[jira] [Created] (IGNITE-1763) We need somehow handle long field name in metadata dialog

Pavel Konstantinov created IGNITE-1763: -- Summary: We need somehow handle long field name in metadata dialog Key: IGNITE-1763 URL: https://issues.apache.org/jira/browse/IGNITE-1763 Project: Ignite