Re: Ignite-1.5 Release

Branch ignite-1.5 created. On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov wrote: > I assume that correct link at 10th feature is > https://issues.apache.org/jira/browse/IGNITE-638 > > On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov wrote: > >>

[GitHub] ignite pull request: IGNITE-1835 .Net: Use thread-local pool to st...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/196 IGNITE-1835 .Net: Use thread-local pool to store schemas in PortableWriter You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite

[jira] [Created] (IGNITE-1838) Implement fast-path deserialization of common types in PortableObjectImpl.

Vladimir Ozerov created IGNITE-1838: --- Summary: Implement fast-path deserialization of common types in PortableObjectImpl. Key: IGNITE-1838 URL: https://issues.apache.org/jira/browse/IGNITE-1838

Re: Request add me to development list

Prabhat, It looks like you are incorrectly subscribed to the dev list and I always have to manually approve your emails before they get distributed. Can you please try subscribing again by sending an email to dev-subscr...@ignite.apache.org. Please make sure to follow the simple instructions in

Re: Ignite-1.5 Release

I assume that correct link at 10th feature is https://issues.apache.org/jira/browse/IGNITE-638 On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov wrote: > Guys, > > I think we can start preparation to Ignite-1.5 release which will include > many interesting features: > > 1.

Re: Ignite-1.5 Release

Can/will this include https://issues.apache.org/jira/browse/IGNITE-1681 ? On Mon, Nov 2, 2015 at 1:51 PM, Anton Vinogradov wrote: > Branch ignite-1.5 created. > > On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov > > wrote: > > > I assume

[GitHub] ignite pull request: IGNITE-1397 Load/consistency test framework

Github user ashutakGG closed the pull request at: https://github.com/apache/ignite/pull/145 --- 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: Ignite-1.5 Release

On Mon, Nov 2, 2015 at 6:58 AM, M G wrote: > Can/will this include https://issues.apache.org/jira/browse/IGNITE-1681 ? > I don’t see why not. Would be nice if one of the committers could pick up the review for this patch. > > On Mon, Nov 2, 2015 at 1:51 PM, Anton

[jira] [Created] (IGNITE-1842) Add dropdown list of existing fields for setting it in index

Pavel Konstantinov created IGNITE-1842: -- Summary: Add dropdown list of existing fields for setting it in index Key: IGNITE-1842 URL: https://issues.apache.org/jira/browse/IGNITE-1842 Project:

[jira] [Created] (IGNITE-1841) Need add ConnectorConfiguration to cluster configuration

Andrey Novikov created IGNITE-1841: -- Summary: Need add ConnectorConfiguration to cluster configuration Key: IGNITE-1841 URL: https://issues.apache.org/jira/browse/IGNITE-1841 Project: Ignite

Re: Ignite-1.5 Release

Thanks Vladislav! Would also be nice to get an update from other committers involved in the outlined tickets. Specifically whether the ticket has been merged to master or not, and if not, what should be the expectation. Thanks, D. On Mon, Nov 2, 2015 at 11:23 AM, Vladisav Jelisavcic

Re: Request add me to development list

Hi Prabhat, Welcome on board! Please share your JIRA account with us and we will set all required permissions for it. Once it has been done you will be able to assign that ticket to you by yourself. Regards, Denis On 10/31/2015 3:42 PM, Prabhat Ranjan wrote: Hi, I work in financial

Re: Contributing to Ignite

I would like to work on this issue https://issues.apache.org/jira/browse/IGNITE-1831 please assign this issue to me, my account on jira @Dmitriyff 2015-11-02 14:59 GMT+07:00 Alexey Kuznetsov : > Hi! > > Welcome to Ignite Apache. > > We have feature that requires web

RE: OSGi migration may require a special marshaller

Raul, The fundamental hurdle we need to jump over to make Ignite OSGi-enabled is the marshalling. More specifically the issue is with deserialization of the classes that are provided by the bundles other than the Ignite bundle itself. When the Ignite transport layer receives a message it

[jira] [Created] (IGNITE-1839) [Test failed] GridCacheNearTxExceptionSelfTest.testRemoveBackup failed

Andrey Gura created IGNITE-1839: --- Summary: [Test failed] GridCacheNearTxExceptionSelfTest.testRemoveBackup failed Key: IGNITE-1839 URL: https://issues.apache.org/jira/browse/IGNITE-1839 Project: Ignite

Re: Questions about TeamCity CI organization

I am also curious to get answers to the questions posted by Raul. Can someone knowledgeable in TC configuration respond? D. On Mon, Oct 26, 2015 at 6:14 AM, Raul Kripalani wrote: > Hey guys, > > I have a few questions about the way our builds are organised in TeamCity. > > 1.

Re: Regrouping of streamers under TeamCity

Thanks Raul! What is the name of the new module? Should the documentation be updated (or created?) On Wed, Oct 28, 2015 at 5:53 AM, Raul Kripalani wrote: > Hello all, > > I've regrouped Ignite streamer modules in TeamCity into the existing Ignite > Streamers build

[jira] [Created] (IGNITE-1836) Automatically select the first item if current is not in filtered list

Pavel Konstantinov created IGNITE-1836: -- Summary: Automatically select the first item if current is not in filtered list Key: IGNITE-1836 URL: https://issues.apache.org/jira/browse/IGNITE-1836

[GitHub] ignite pull request: IGNITE-1818 .Net: compact footer offsets

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/193 IGNITE-1818 .Net: compact footer offsets You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-1818 Alternatively you can

[jira] [Created] (IGNITE-1833) VisorCache task collects wrong backup partitions information

Alexey Kuznetsov created IGNITE-1833: Summary: VisorCache task collects wrong backup partitions information Key: IGNITE-1833 URL: https://issues.apache.org/jira/browse/IGNITE-1833 Project: Ignite

[jira] [Created] (IGNITE-1834) .Net: Remove MetadataEnabled property

Pavel Tupitsyn created IGNITE-1834: --- Summary: .Net: Remove MetadataEnabled property Key: IGNITE-1834 URL: https://issues.apache.org/jira/browse/IGNITE-1834 Project: Ignite Issue Type:

[GitHub] ignite pull request: ignite-1698 SqlFieldsQuery works incorrectly ...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/178 --- 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: OSGi migration may require a special marshaller

Hi Andrey, Thanks for the participation in this topic. I don't like the solution to incorporate the bundle symbolic name in the serialised form. Nothing guarantees that the classdef will be located under the same bundle in both source and target machines. We also have to take into account that

Re: Ignite-1.5 Release

I am finalizing changes related to IGNITE-1486 branch. Currently the API changes are finished and now I am mostly fixing the CI tests. In fact, I just submitted the latest fix related to the new .NET platform functionality and hope CI tests will pass, in this case it will be ready to be merged

Hello

Subscribe me. Is this automated only?

Re: Ignite-1.5 Release

Alexey, I am confused. Why do you have 2 branches? D. On Mon, Nov 2, 2015 at 2:32 PM, Alexey Goncharuk wrote: > I am finalizing changes related to IGNITE-1486 branch. Currently the API > changes are finished and now I am mostly fixing the CI tests. In fact, I >

Re: Ignite-1.5 Release

I'm sorry, I meant to write "changes related to IGNITE-1486 *ticket*". The changes are in ignite-950-new branch because it is a result of work on multiple sub-tickets and it is currently used as an integration branch. 2015-11-03 1:39 GMT+03:00 Dmitriy Setrakyan : > Alexey,

Re: Hello

Hi Michael, Please subscribe to this list by sending an email to dev-subscr...@ignite.apache.org and following the simple instructions in the reply. D. On Mon, Nov 2, 2015 at 2:31 PM, Michael Grabenstein wrote: > Subscribe me. > Is this automated only? > >

[GitHub] ignite pull request: IGNITE-1834 .Net: Remove MetadataEnabled prop...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/194 IGNITE-1834 .Net: Remove MetadataEnabled property You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-1834 Alternatively

[GitHub] ignite pull request: ignite-1380 Random eviction policy for near c...

Github user agura closed the pull request at: https://github.com/apache/ignite/pull/185 --- 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: OSGi migration may require a special marshaller

Romain, Is that correct that you obtain instance of Ignite through cache manager and pass your classloader to which gets ignored at some point? Or you use IgniteConfiguration#setClassLoader? Can you or anyone in community please provide a short example or junit so I can reproduce this? Thanks!

Re: Request add me to development list

Yakov, Dmitriy or anyone else from the community with administrative rights please provide Prabhat's JIRA account with all required permissions. -- Denis On 11/2/2015 1:49 PM, Prabhat Ranjan wrote: Thanks Denis. Please set required permission to my JIRA account 'prabhat'. Regards, Prabhat

RE: OSGi migration may require a special marshaller

Hey Raul, What kind of use case do you have in mind when you suggest that a classdef may be located in different bundles on different machines? What would one have to do to end up in such a predicament? It feels more like a configuration/deployment issue rather than a desirable feature. A

Re: OSGi migration may require a special marshaller

I think I can see Andrey’s point about the bundles. Having same classdef in different bundles on sender and receiver sides sounds rather like a bug, not a feature we should support. Having read this thread, I think we need to have ClassLoaderResolver on the sending and receiving sides. Something

[GitHub] ignite pull request: IGNITE-1397 Load/consistency test framework

GitHub user ashutakGG opened a pull request: https://github.com/apache/ignite/pull/195 IGNITE-1397 Load/consistency test framework IGNITE-1397 Load/consistency test framework You can merge this pull request into a Git repository by running: $ git pull

Re: Request add me to development list

Done! --Yakov 2015-11-02 14:53 GMT+03:00 Denis Magda : > Yakov, Dmitriy or anyone else from the community with administrative > rights please provide Prabhat's JIRA account with all required permissions. > > -- > Denis > > On 11/2/2015 1:49 PM, Prabhat Ranjan wrote: > >>

[jira] [Created] (IGNITE-1837) Slow rebalancing on a big cluster (64 nodes and more)

Denis Magda created IGNITE-1837: --- Summary: Slow rebalancing on a big cluster (64 nodes and more) Key: IGNITE-1837 URL: https://issues.apache.org/jira/browse/IGNITE-1837 Project: Ignite Issue

Re: OSGi migration may require a special marshaller

Hi Romain, I'm working on the OSGi compatibility of Ignite. I appreciate your input. I'm thinking about the situation you describe and I wonder if you're exporting Ignite as an OSGi service which is then consumed from other bundles. Under this situation, it would be quite easy to reproduce the

Integration with Spring Transaction Manager

Igniters, Anyone in the community interested in picking up integration with Spring Transaction Manager? The implementation should not be difficult, but will be a very useful addition to the project (many users have been asking for it). Here is the Jira ticket:

IgniteMultiMap design

Igniters, MultiMap should be really great addition to the Ignite fabric, as it provides an easy-to-use API to work with time-series data. I have added a detailed design description to the IgniteMultiMap ticket: https://issues.apache.org/jira/browse/IGNITE-640 Vladislav Jelisavcic, the ticket is

Re: Hello

Hi Jose, You can also find interesting Jira tickets to work on here: https://ignite.apache.org/community/contribute.html#pick-ticket D. On Sat, Oct 31, 2015 at 4:55 AM, Gianfranco Murador wrote: > Welcome Josè , take a look at these guidelines: >