[jira] [Created] (IGNITE-1785) .Net: Improve PlatformMemory/PortableStream performance and memory usage

Pavel Tupitsyn created IGNITE-1785: --- Summary: .Net: Improve PlatformMemory/PortableStream performance and memory usage Key: IGNITE-1785 URL: https://issues.apache.org/jira/browse/IGNITE-1785

[jira] [Created] (IGNITE-1780) .Net: DateTime is seialized incorrectly.

Vladimir Ozerov created IGNITE-1780: --- Summary: .Net: DateTime is seialized incorrectly. Key: IGNITE-1780 URL: https://issues.apache.org/jira/browse/IGNITE-1780 Project: Ignite Issue Type:

Account @ TeamCity, please

Hey guys, Could someone please create an account for me @ TeamCity with committer/PMC permissions? Thanks, *Raúl Kripalani* PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and Messaging Engineer http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani

Re: Ignite Web Console - Loading metadata from MySQL

On Fri, Oct 23, 2015 at 3:16 AM, Alexey Kuznetsov wrote: > Actually it is quite hard to do. > > The main complexity that we need to implement double transfer: > 1) Transfer selected jar from user local folder to Web Console Server. > 2) Transfer jar from Web Console

[jira] [Created] (IGNITE-1782) IgniteKernal get wrong message in the log about set marshaller

Vasilisa Sidorova created IGNITE-1782: -- Summary: IgniteKernal get wrong message in the log about set marshaller Key: IGNITE-1782 URL: https://issues.apache.org/jira/browse/IGNITE-1782 Project:

[jira] [Created] (IGNITE-1781) Broken query header in case of long query name

Pavel Konstantinov created IGNITE-1781: -- Summary: Broken query header in case of long query name Key: IGNITE-1781 URL: https://issues.apache.org/jira/browse/IGNITE-1781 Project: Ignite

Re: Ignite Web Console - Loading metadata from MySQL

Actually it is quite hard to do. The main complexity that we need to implement double transfer: 1) Transfer selected jar from user local folder to Web Console Server. 2) Transfer jar from Web Console Server to Host were Web Agent running. And I would prefer to do it after first release. On Fri,

[GitHub] ignite pull request: ignite-1718 Fix of 'Not enough data to read t...

Github user agura closed the pull request at: https://github.com/apache/ignite/pull/165 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request: ignite-1718 Fix of 'Not enough data to read t...

Github user agura closed the pull request at: https://github.com/apache/ignite/pull/165 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

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

Hey Yakov, About the exception messages, come on, you have to admit you are making up rules as we go ;-) Nowhere in the coding guidelines does it say that all exception messages have to start with "Failed to...". In fact, there are hundreds if not thousands of Exception messages in the existing

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

Dmitriy, The first step is to write a complete specification for a coding style. It's still incomplete from what I see. It's inadmissible that new rules pop up in an ad hoc manner during reviews, based on a single person's judgement. If it's not documented in the guidelines, it *cannot be

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

Gents, First of all, can I ask why this review is being done on the dev list instead of in the Jira? All we are doing is splitting the communication about the same feature into multiple places. I believe we have all agreed in the past that Jira is the proper place for it. Now, I have not done

[jira] [Created] (IGNITE-1783) Remove GridBoundedConcurrentLinkedHashMap and replace its usages with ConcurrentLinkedHashMap

Yakov Zhdanov created IGNITE-1783: - Summary: Remove GridBoundedConcurrentLinkedHashMap and replace its usages with ConcurrentLinkedHashMap Key: IGNITE-1783 URL: https://issues.apache.org/jira/browse/IGNITE-1783

Re: TC patch validation

Cos, see email. -- Artem -- On Thu, Oct 22, 2015 at 9:15 PM, Konstantin Boudnik wrote: > 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

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

Raul, My comments are below. 2015-10-22 22:22 GMT+03:00 Raul Kripalani : > 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

Re: Account @ TeamCity, please

Raul, you should be able to create an account and login by yourself. Then you will be able to trigger builds manually. D. On Fri, Oct 23, 2015 at 11:14 AM, Raul Kripalani wrote: > Hey guys, > > Could someone please create an account for me @ TeamCity with committer/PMC >

[jira] [Created] (IGNITE-1786) Need to implement ODBC driver for Ignite

Dmitriy Setrakyan created IGNITE-1786: - Summary: Need to implement ODBC driver for Ignite Key: IGNITE-1786 URL: https://issues.apache.org/jira/browse/IGNITE-1786 Project: Ignite Issue

[jira] [Created] (IGNITE-1779) .Net: Evaluate BinaryFormatter overhead for generic collections.

Vladimir Ozerov created IGNITE-1779: --- Summary: .Net: Evaluate BinaryFormatter overhead for generic collections. Key: IGNITE-1779 URL: https://issues.apache.org/jira/browse/IGNITE-1779 Project: