[jira] [Created] (IGNITE-1844) Automatically create IgfsGroupDataBlocksKeyMapper for IGFS configuration

Pavel Konstantinov created IGNITE-1844: -- Summary: Automatically create IgfsGroupDataBlocksKeyMapper for IGFS configuration Key: IGNITE-1844 URL: https://issues.apache.org/jira/browse/IGNITE-1844

[jira] [Created] (IGNITE-1846) CPP: Adopt portable API changes.

Vladimir Ozerov created IGNITE-1846: --- Summary: CPP: Adopt portable API changes. Key: IGNITE-1846 URL: https://issues.apache.org/jira/browse/IGNITE-1846 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-1845) .Net: Adopt poratble API changes.

Vladimir Ozerov created IGNITE-1845: --- Summary: .Net: Adopt poratble API changes. Key: IGNITE-1845 URL: https://issues.apache.org/jira/browse/IGNITE-1845 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-1847) Portables: add "field" method to PortableMetadata.

Vladimir Ozerov created IGNITE-1847: --- Summary: Portables: add "field" method to PortableMetadata. Key: IGNITE-1847 URL: https://issues.apache.org/jira/browse/IGNITE-1847 Project: Ignite

Re: log4j2 garbage files

Hey guys, Sorry I missed Artem's request for a review. Glad you got the chance, Denis. Regards, *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

[jira] [Created] (IGNITE-1849) cache.size() method causes three TASK_* events

Sergey Kozlov created IGNITE-1849: - Summary: cache.size() method causes three TASK_* events Key: IGNITE-1849 URL: https://issues.apache.org/jira/browse/IGNITE-1849 Project: Ignite Issue

Re: Questions about TeamCity CI organization

Hi Raul, 1. Yes, this is correct separation. If you are working on some new feature usually in development process you want to run only your build, may be 2, but not all tests. And only when a feature is close to complete you want to run all tests. 2. There are at least 2 goals: - Don't run all

Re: log4j2 garbage files

Guys, I've merged the fix into the master. Thanks, Denis On 10/30/2015 3:43 PM, Gianfranco Murador wrote: Hi Artem, I have no write permission to merge the fix On Oct 30, 2015 11:43 AM, "Artem Shutak" wrote: Hi Raul, Oh, I was sure I deleted these files. Fixed in my

Re: OSGi migration may require a special marshaller

Hi Raul, - Do you plan to use the TCCL when marshalling in OSGi env? If yes how? - I like the point 2. Maybe for a graph of object that come from different packages / bundles you may have to recursively capture the package version of the individual element of your graph. - For the point 3 I

about apache ignite's document localization(Simplified Chinese)

Hi： I am a software architecter from China, is very interested in Ignite, Ignite design is very good, very powerful, is a very potential technology, I hope to promote the promotion of Ignite in China through the translation of Ignite's documentation, so that Ignite can be used as soon as

Re: Ignite-1.5 Release

I implemented changes related to IGNITE-426 task. Currently investigating performance degradation for atomic caches. I expect the ticket to be merged in 2 days. On Tue, Nov 3, 2015 at 6:47 PM, Alexey Goncharuk wrote: > IGNITE-950 is taking more time to be merged

Re: OSGi migration may require a special marshaller

Hey guys, About the TCCL, I need to dig deeper into how serialisation is being done now. If, at any point, we are resolving a class through the classloader of a particular class, e.g. Ignition.getClass().getClassLoader(), etc. we are using the class space of the bundle containing that class. If

[GitHub] ignite pull request: IGNITE-1850.

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

Re: OSGi migration may require a special marshaller

Romain, Can you comment on the ClassLoaderResolver suggestion that I proposed earlier? Will it solve your problem? D. On Tue, Nov 3, 2015 at 2:38 AM, Romain Gilles wrote: > Hi Raul, > - Do you plan to use the TCCL when marshalling in OSGi env? If yes how? > - I like

Re: Questions about TeamCity CI organization

Hi Artem, Thanks for the clarifications. At first, it did seem overkill that we're building the code over and over again in each build configuration – when the ultimate goal is just to run a subset of tests. But you are right in that the build itself takes very little time comparatively to the

Hello

-- _pradeep

Re: Ignite-1.5 Release

Good news for the IGNITE-950 ticket - CI looks good, changes will be merged to ignite-1282 integration branch after benchmarks re-run. 2015-11-03 21:37 GMT+03:00 Nikolay Tikhonov : > I implemented changes related to IGNITE-426 task. Currently investigating > performance

Re: Ignite-1.5 Release

I'm working on IGNITE-1753 Rework CacheJdbcPojoStore to new API ( https://issues.apache.org/jira/browse/IGNITE-1753). Issue is implemented and waiting for IGNITE-950 to be merged into ignite-1282. On Wed, Nov 4, 2015 at 5:22 AM, Alexey Goncharuk wrote: > Good news

Re: about apache ignite's document localization(Simplified Chinese)

(adding the contributor to the CC) Hi, I am sorry, I do not know your name, but it is a great contribution! Can I ask you to properly subscribe to the dev list? You need to send an email to “dev-subscr...@ignite.apache.org” and then follow the simply instructions in the reply. This will make

Re: OSGi migration may require a special marshaller

Hi Dmitriy, I think your solution is good. Maybe I will change it a little bit... :P I think you should delegate the Class resolution to the resolver. Because for example with your current solution the marshaller may before (or after) store the fqn of the class (maybe only the first time it

RE: OSGi migration may require a special marshaller

Dmitriy, I think your approach will work, but I let Romain respond. Also, in terms of the implementation, please keep in mind that the resolver must be called for each non-JDK and non-Ignite core class (it would probably make sense to eschew storing class loaders for such classes in favor of

Re: Hello

Hi Pradeep, Welcome to the Ignite community! Please properly subscribe to the dev list (this way I will not have to manually approve your emails). All you need to do is send an email to “ dev-subscr...@ignite.apache.org” and follow simple instructions in the reply. You should get familiar with

Ignite web console UI usability

Hi, Igniters, I'm playing with Ignite Web Console (console.gridgain.com) and would like to ask your opinion about name of 'Reset' button on Caches screen. By fact this button doing 'undo all changes'. But it's current name - Reset - a bit confusing me. When I see 'Reset' I'm thinking about

Re: Ignite web console UI usability

To me, "Revert", "Cancel", "Undo" -- any of these is better than "Reset". -Roman On Wednesday, November 4, 2015 1:29 PM, Pavel Konstantinov wrote: Hi, Igniters, I'm playing with Ignite Web Console (console.gridgain.com) and would like to ask your

[jira] [Created] (IGNITE-1852) Need to align RDBMS dropdown and it's tooltip

Pavel Konstantinov created IGNITE-1852: -- Summary: Need to align RDBMS dropdown and it's tooltip Key: IGNITE-1852 URL: https://issues.apache.org/jira/browse/IGNITE-1852 Project: Ignite

Re: OSGi migration may require a special marshaller

Andrey, et al, Can you provide a way on how to get a required Bundle object based on, say, bundle symbolic name and version? I have reached the end of the internet trying to find a way in OSGI to look up a Bundle based on something other than an actual Class belonging to that bundle, but no

RE: OSGi migration may require a special marshaller

Romain/Dmitriy, I prefer Romain's approach, but just curious, in the API you guys are proposing why use a byte[] rather than OutputStream/InputStream? With a byte[], one would inevitably end up wrapping it into a byte stream class. Also, the stream-based interface would be more in line with

Re: OSGi migration may require a special marshaller

Hi Raul, I had a look to what has been done in camel. I think here the use cases came be different. Let say I want to run a closure against the grid like this: IgniteCompute compute = ignite.compute(); // Execute closure on all cluster nodes.Collection res = compute.apply( String::length,

Re: Ignite web console UI usability

Pavel, I do not have the same association as you. To me “Reset” means reset to the previous state. I would prefer to leave it. If we still decide to change it, then I would pick “Cancel”. D. On Tue, Nov 3, 2015 at 10:10 PM, Roman wrote: > To me, "Revert", "Cancel",

Re: Ignite web console UI usability

Guys, Currently each section has undo button without any text name only 'round arrow' image. Maybe make the same button on the top level? On Wed, Nov 4, 2015 at 2:24 PM, Dmitriy Setrakyan wrote: > Pavel, > > I do not have the same association as you. To me “Reset” means

[jira] [Created] (IGNITE-1853) Implement plugins support

Dmitriyff created IGNITE-1853: - Summary: Implement plugins support Key: IGNITE-1853 URL: https://issues.apache.org/jira/browse/IGNITE-1853 Project: Ignite Issue Type: Sub-task

Re: Ignite-1.5 Release

On 11/2/2015 8:40 PM, Dmitriy Setrakyan wrote: 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.

Re: IgniteMultiMap design

Dear Dmitriy, it sounds excellent, I would like to do it, but I would like to implement ReentrantLock first: https://issues.apache.org/jira/browse/IGNITE-642 What do you think? On Tue, Nov 3, 2015 at 3:37 AM, Dmitriy Setrakyan wrote: > Igniters, > > MultiMap should be

[jira] [Created] (IGNITE-1850) IGFS: implicitly created directoried should always have default properties

Ivan Veselovsky created IGNITE-1850: --- Summary: IGFS: implicitly created directoried should always have default properties Key: IGNITE-1850 URL: https://issues.apache.org/jira/browse/IGNITE-1850