[GitHub] ignite pull request #2206: IGNITE-5340 AssertionError in index name check

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/2206 IGNITE-5340 AssertionError in index name check You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5340

[GitHub] ignite pull request #448: ignite-2536 reproducer test

Github user agura closed the pull request at: https://github.com/apache/ignite/pull/448 --- 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 #387: ignite-2307 Reproducer test

Github user agura closed the pull request at: https://github.com/apache/ignite/pull/387 --- 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 #2207: Ignite 5589: Archive WAL segment after significan...

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/2207 Ignite 5589: Archive WAL segment after significant period of grid inactivity Please don't merge. PR is for TC run You can merge this pull request into a Git repository by running: $ git pull

Re: Problem with setting up .NET dev environment

Hi Vadim, Just to be sure, what is considered root directory? Cause I've always been running the command in the topmost directory of the repo with all the .git, .pom, readme and all other files and folders? On 27 June 2017 at 19:57, Vyacheslav Daradur wrote: > Hi, looks

[CVE-2017-7686] Apache Ignite Information Disclosure

Severity: Important Vendor: The Apache Software Foundation Versions Affected: * Apache Ignite 1.0.0-RC3 to 2.0 Impact: Apache Ignite Might Transfer Sensitive Information to 3rd Party Domain Description: Apache Ignite uses an update notifier component to update the users about new project

Re: Problem with setting up .NET dev environment

Sorry, Vyacheslav =)) On 27 June 2017 at 22:37, Guru Stron wrote: > Hi Vadim, > > Just to be sure, what is considered root directory? Cause I've always been > running the command in the topmost directory of the repo with all the .git, > .pom, readme and all other

[GitHub] ignite pull request #2208: for test purposes

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/2208 for test purposes You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite gg-12370 Alternatively you can review and apply

[jira] [Created] (IGNITE-5597) Wrong javadoc in Affinity and AffinityFunction for REPLICATED cache

Evgenii Zhuravlev created IGNITE-5597: - Summary: Wrong javadoc in Affinity and AffinityFunction for REPLICATED cache Key: IGNITE-5597 URL: https://issues.apache.org/jira/browse/IGNITE-5597

Re: Server stores cache data on-heap if client has near cache - IGNITE-4662

I'm not sure this ticket is valid for 2.0. Semen, can you comment? -Val On Tue, Jun 27, 2017 at 1:14 AM, Vyacheslav Daradur wrote: > Hi Igniters. > > I have some questions according to this task: > > 1. Does the method: GridCacheMapEntry#evictInternal do the >

FW: golang client for Ignite

Dear Ignite team, I see there is no native client for golang. I tried to fix this gap a little bit and developed golang SQL driver for ignite/gridgain: https://github.com/amsokol/go-ignite-client. Enjoy ))). It's in beta phase now. I’m focusing on test coverage now. Driver uses HTTP REST API

Re: daemon nodes

Daemon nodes are nodes that join the cluster, but do not store data or execute computations or perform any other of the Ignite API-based functionality. Visor node is a good example of a daemon node, because it wants to join the cluster and receive metrics from other nodes, but does not need to

Ignite Persistent Store: Ready for merge?

Guys, According to the discussions I see on the @dev list the donated Ignite Persistent Store [1] is stable and ready to be rolled out to our users. Considering that we’ve been already getting to know the donation for a while and had the webinar dedicated to the functionality trying to answer

Re: cannot build ignite 2.1.0

Aleksey, What’s the command you use to trigger the build? — Denis > On Jun 23, 2017, at 9:24 AM, ALEKSEY KUZNETSOV > wrote: > > Cannot build apache ignite 2.1.0 package. Build fails on ignite-hadoop > module : > Could not find artifact

Re: Replace Cron4J with Quartz for ignite-schedule module.

Yakov, No, the mentioned discussion didn’t turn into a JIRA ticket. Alex K., please follow to some thoughts from there and wrap them up in a form of the ticket. — Denis > On Jun 26, 2017, at 2:58 AM, Yakov Zhdanov wrote: > > Guys, I remember we discussed this some time

Re: DataStreamer Transactional and Timestamp Implementation

Faith, Thanks for sharing it with us. In general, we can always wrap this code up in a form of an example to be delivered with every Ignite release. But probably it makes sense to add it to the core streaming functionality. *Igniters*, what’d you think? — Denis > On Jun 27, 2017, at

Re: golang client for Ignite

Hi Aleksandr, That looks really interesting to me. Personally, I would like to see a dedicated Go module in Ignite. Do you support SQL API right now? If it’s so then you might want to switch to Ignite JDBC driver instead that should outperform the REST protocol. Otherwise, if the goal is to

[jira] [Created] (IGNITE-5593) Affinity change message leak on massive topology updates

Alexey Goncharuk created IGNITE-5593: Summary: Affinity change message leak on massive topology updates Key: IGNITE-5593 URL: https://issues.apache.org/jira/browse/IGNITE-5593 Project: Ignite

Re: Problem with setting up .NET dev environment

Hi, looks like you call command within wrong directory. Please make sure that directory (where you call maven comand) is the root-folder of the project. 2017-06-27 16:11 GMT+03:00 Guru Stron : > Hi igniters, > > I have problem with setting up dev environment on one of

[jira] [Created] (IGNITE-5598) WAL Iteration stopped with exception after writting log with background mode

Dmitriy Pavlov created IGNITE-5598: -- Summary: WAL Iteration stopped with exception after writting log with background mode Key: IGNITE-5598 URL: https://issues.apache.org/jira/browse/IGNITE-5598

[GitHub] ignite pull request #2199: Ignite gg 12347 1

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/2199 Ignite gg 12347 1 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-12347-1 Alternatively you can

[GitHub] ignite pull request #2202: IGNITE-5076: improved multi-threaded start of nod...

GitHub user sk0x50 opened a pull request: https://github.com/apache/ignite/pull/2202 IGNITE-5076: improved multi-threaded start of nodes You can merge this pull request into a Git repository by running: $ git pull https://github.com/sk0x50/ignite ignite-5076-master

Re: JIRA Access - Ignite

Hi Ankur, What is your JIRA ID? On Tue, Jun 27, 2017 at 3:42 PM, Ankur Kumar wrote: > I can access Apache Ignite but can not assign any defect to myself. Can I > get permission to assign issues to myself to work on these items? > > Regards, > > Ankur Kumar > --

daemon nodes

Hi Igniters, Can somebody explain what does mean daemon node? I thought that exist only client and server node, but node may can be daemon (server daemon or client daemon). As is can see, command line visor join in topology as server daemon. Can this be an outdated functionality?

[GitHub] ignite pull request #2203: IGNITE-5456 JDBC thin driver: the statement produ...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/2203 IGNITE-5456 JDBC thin driver: the statement produces multiple result … …sets must be handled correct You can merge this pull request into a Git repository by running: $ git pull

JIRA Access - Ignite

I can access Apache Ignite but can not assign any defect to myself. Can I get permission to assign issues to myself to work on these items? Regards, Ankur Kumar

DataStreamer Transactional and Timestamp Implementation

Hi We have implemented some receivers to be able to update data in data nodes by ignite datastreamer api. There is an associated ticket as below already exist. We thought it would be useful to use that implementation from ignite directly. Maybe can be added to ignite directly.

[GitHub] ignite pull request #2201: IGNITE-5521: Large near caches lead to cluster in...

GitHub user mcherkasov opened a pull request: https://github.com/apache/ignite/pull/2201 IGNITE-5521: Large near caches lead to cluster instability with metrics enabled You can merge this pull request into a Git repository by running: $ git pull

Server stores cache data on-heap if client has near cache - IGNITE-4662

Hi Igniters. I have some questions according to this task: 1. Does the method: GridCacheMapEntry#evictInternal do the eviction(on-heap -> off-heap)? 2. Is CacheOffheapEvictionManager responsible for managing the eviction(on-heap -> off-heap)? (if not, then who is?) 3. At what moment the

[jira] [Created] (IGNITE-5596) Exchange time measurement

Oleg Ostanin created IGNITE-5596: Summary: Exchange time measurement Key: IGNITE-5596 URL: https://issues.apache.org/jira/browse/IGNITE-5596 Project: Ignite Issue Type: Improvement

Problem with setting up .NET dev environment

Hi igniters, I have problem with setting up dev environment on one of my machines(using fresh master). The maven build step from Ignite.NET+Development manual page fails. My old dev environment on other machine works just

[jira] [Created] (IGNITE-5594) Ignite test framework intervenes into configuration of Ignite node internal component

Sergey Chugunov created IGNITE-5594: --- Summary: Ignite test framework intervenes into configuration of Ignite node internal component Key: IGNITE-5594 URL: https://issues.apache.org/jira/browse/IGNITE-5594

[jira] [Created] (IGNITE-5595) Optimize 'client' event exchanges

Semen Boikov created IGNITE-5595: Summary: Optimize 'client' event exchanges Key: IGNITE-5595 URL: https://issues.apache.org/jira/browse/IGNITE-5595 Project: Ignite Issue Type: Task

[GitHub] ignite pull request #2192: fix metadata update

Github user sboikov closed the pull request at: https://github.com/apache/ignite/pull/2192 --- 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: Zookeeper Discovery SPI & external IP address in AWS

>>Both will work, but frankly I like option 1 more. First of all, it's just >>more intuitive that IP finder contains all possible addresses that can be >>used to join. Second of all, option 2 introduces requirement to have >>address resolver for server addresses configured on client nodes - this

[GitHub] ignite pull request #2204: IGNITE-5279

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

Re: Zookeeper Discovery SPI & external IP address in AWS

Yakov, What do you mean by 'mixture'? :) Client obviously needs to know public addresses to connect and I think it's natural to get them from IP finder. Is there something wrong with this? -Val On Tue, Jun 27, 2017 at 5:01 AM, Yakov Zhdanov wrote: > >>Both will work, but

Re: DataStreamer Transactional and Timestamp Implementation

Fatih, Can you give more details about the use case addressed by this implementation? -Val On Tue, Jun 27, 2017 at 3:45 PM, Denis Magda wrote: > Faith, > > Thanks for sharing it with us. > > In general, we can always wrap this code up in a form of an example to be >

[jira] [Created] (IGNITE-5599) Web console: Agent should check that node URI is valid

Vasiliy Sisko created IGNITE-5599: - Summary: Web console: Agent should check that node URI is valid Key: IGNITE-5599 URL: https://issues.apache.org/jira/browse/IGNITE-5599 Project: Ignite