[jira] [Created] (IGNITE-7415) Ability to disable WAL (Documentation)

Anton Vinogradov created IGNITE-7415: Summary: Ability to disable WAL (Documentation) Key: IGNITE-7415 URL: https://issues.apache.org/jira/browse/IGNITE-7415 Project: Ignite Issue Type:

Re: Handling slashes in cache names

To understand how much storage you need for cache group "X" and watch the trends. Anyway, folder named by ID and txt file inside should do the trick =) --Yakov

Hello!

Hello Ignite Community! My name is Sergey. I want to contribute to Apache Ignite and want to start with this issue - IGNITE-5565. Any help on this will be appreciated. Thanks! Best regards, Sergey Kosarev.

[GitHub] ignite pull request #3383: Ignite 7284 1.9

GitHub user slukyano opened a pull request: https://github.com/apache/ignite/pull/3383 Ignite 7284 1.9 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7284-1.9 Alternatively you can review and

[jira] [Created] (IGNITE-7414) Cluster restart may lead to cluster activation error

c5-4d67-8ca5-b6dd1628c5dc, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, 172.25.4.158, 2001:0:9d38:6abd:188f:1f82:53e6:fb61], sockAddrs=[DESKTOP-IMRCA1M/172.25.4.158:47500, /2001:0:9d38:6abd:188f:1f82:53e6:fb61:47500, /0:0:0:0:0:0:0:1:47500, /127.0.0.1:47500], discPort=47500, order=1, intOrder=1, lastExchangeTi

[GitHub] ignite pull request #3377: IGNITE-7386: Got rid of ThreadLocalRandom8.

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/3377 IGNITE-7386: Got rid of ThreadLocalRandom8. For test purposes. You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite

[GitHub] ignite pull request #3380: IGNITE-1628 .NET: Compile and run on Mono

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/3380 IGNITE-1628 .NET: Compile and run on Mono You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-1628 Alternatively you

Re: Handling slashes in cache names

> try creating a directory on all nodes And then a new node appears with a different kind of file system.. Escaping removes all limitations and does not affect usability. Pavel On Mon, Jan 15, 2018 at 5:47 PM, Yakov Zhdanov wrote: > Agree that cache names should be case

Re: Handling slashes in cache names

>> And then a new node appears with a different kind of file system.. This is hardly possible. And I suggest not to >> Escaping removes all limitations and does not affect usability. Disagree. You will never ever relate smth like "fdee0456adcc" to "мои_данные". Guys, I just realized that we

[GitHub] ignite pull request #3381: Ignite 7284 2.3

GitHub user slukyano opened a pull request: https://github.com/apache/ignite/pull/3381 Ignite 7284 2.3 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7284-2.3 Alternatively you can review and

[GitHub] ignite pull request #3382: Ignite 7284 2.1

GitHub user slukyano opened a pull request: https://github.com/apache/ignite/pull/3382 Ignite 7284 2.1 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7284-2.1 Alternatively you can review and

Re: Hello!

Hello and welcome! Please get familiar with Ignite development process described here: https://cwiki.apache.org/confluence/display/IGNITE/Development+Process Subscribe to both dev and user lists: https://ignite.apache.org/community/resources.html#mail-lists Instructions on how to contribute

[GitHub] ignite pull request #3379: ignite-7389 : DataStreamer operations will ensure...

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/3379 ignite-7389 : DataStreamer operations will ensure that cache start is completed You can merge this pull request into a Git repository by running: $ git pull

Re: Handling slashes in cache names

Agree that cache names should be case insensitive - currently it seems that we have issues on Windows OS. As far as allowed characters - why don't we try creating a directory on all nodes (but calling toLower() prior to creation)? If creation succeeds everywhere then cache name is acceptable. New

[jira] [Created] (IGNITE-7416) Add more parameter update methods

Artem Malykh created IGNITE-7416: Summary: Add more parameter update methods Key: IGNITE-7416 URL: https://issues.apache.org/jira/browse/IGNITE-7416 Project: Ignite Issue Type: Improvement

Re: Handling slashes in cache names

> You will never ever relate smth like "fdee0456adcc" to "мои_данные". As a user, why do I need to understand file names in Ignite work directory? On Mon, Jan 15, 2018 at 6:22 PM, Yakov Zhdanov wrote: > >> And then a new node appears with a different kind of file system..

[GitHub] ignite pull request #3378: IGNITE-3935: Fix P2P class loading for StreamTran...

GitHub user dmekhanikov opened a pull request: https://github.com/apache/ignite/pull/3378 IGNITE-3935: Fix P2P class loading for StreamTransformer.from() You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: Ignite not friendly for Monitoring

Igniters, It's a right idea! Let's try to revitalize it and make a move on. As a first step, I would like to propose a list of a top-level domain. -- the phase 1 1. UnExpected, UnKnown 2. Cluster and Topology Discovery Segmentation Node Startup

[jira] [Created] (IGNITE-7417) AdaDelta parameter update algorithm

Artem Malykh created IGNITE-7417: Summary: AdaDelta parameter update algorithm Key: IGNITE-7417 URL: https://issues.apache.org/jira/browse/IGNITE-7417 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-7419) Document swap usage in Ignite 2.x memory architecture

Denis Magda created IGNITE-7419: --- Summary: Document swap usage in Ignite 2.x memory architecture Key: IGNITE-7419 URL: https://issues.apache.org/jira/browse/IGNITE-7419 Project: Ignite Issue

[jira] [Created] (IGNITE-7418) Add RMSProp parameter update algorithm/

Artem Malykh created IGNITE-7418: Summary: Add RMSProp parameter update algorithm/ Key: IGNITE-7418 URL: https://issues.apache.org/jira/browse/IGNITE-7418 Project: Ignite Issue Type:

Re: Hello!

my username: macrergate Best regards, Sergey Kosarev. 2018-01-15 19:31 GMT+03:00 Sergey : > Hello Ignite Community! > > My name is Sergey. > > I want to contribute to Apache Ignite and want to start with this issue - > IGNITE-5565. Any help on this will be appreciated. >

Re: Username/password authentication for thin clients

The overall proposal sounds simple and reasonable to me. However, I would suggest us to consider requirements of REST, Web Console and scripts that needs to be adopted too. Alexey K., Andrey N., as Web Console maintainers please chime in. Vladimir, do you think simple password based

[jira] [Created] (IGNITE-7420) Too thick modal body

Alexander Kalinin created IGNITE-7420: - Summary: Too thick modal body Key: IGNITE-7420 URL: https://issues.apache.org/jira/browse/IGNITE-7420 Project: Ignite Issue Type: Bug

[GitHub] ignite pull request #3380: IGNITE-1628 .NET: Compile and run on Mono

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3380 ---

RE: IGNITE-6853: Cassandra cache store does not clean prepared statements cache when remove old cassandra session

Thanks. Just replied on the jira thread as well. Thanks. -Original Message- From: Denis Magda [mailto:dma...@apache.org] Sent: Saturday, January 13, 2018 1:41 AM To: Igor Rudyak Cc: Jason Man, CLSA; dev@ignite.apache.org Subject: Re: IGNITE-6853: Cassandra cache store does not clean

[jira] [Created] (IGNITE-7413) .NET: Datagrid.QueryDmlExample: Incorrect result for Delete and Update if run with standalone nodes

Irina Zaporozhtseva created IGNITE-7413: --- Summary: .NET: Datagrid.QueryDmlExample: Incorrect result for Delete and Update if run with standalone nodes Key: IGNITE-7413 URL:

[jira] [Created] (IGNITE-7412) WAL: Last fsync position can be update by wrong value

Andrey Gura created IGNITE-7412: --- Summary: WAL: Last fsync position can be update by wrong value Key: IGNITE-7412 URL: https://issues.apache.org/jira/browse/IGNITE-7412 Project: Ignite Issue

Re: Irrelevant data in discovery messages

I agree with your suggestion to add required properties to node attributes under specific key disregarding includeProperties value. --Yakov

[GitHub] ignite pull request #3376: ignite-7412 Fixed race in WAL manager with mmap e...

GitHub user agura opened a pull request: https://github.com/apache/ignite/pull/3376 ignite-7412 Fixed race in WAL manager with mmap enabled You can merge this pull request into a Git repository by running: $ git pull https://github.com/agura/incubator-ignite ignite-7412

RE: Handling slashes in cache names

Let me return back to this issue. > Well, having to support multiple cache name formats going forward will be > difficult. I don’t think there is a question of multiple name formats. Let’s just say that there are issues that can be solved on the base cache level (e.g. making cache names always

[GitHub] ignite pull request #3373: Assert on last fsync position

Github user agura closed the pull request at: https://github.com/apache/ignite/pull/3373 ---

[jira] [Created] (IGNITE-7406) Transactions hang forever during load test

Ksenia Rybakova created IGNITE-7406: --- Summary: Transactions hang forever during load test Key: IGNITE-7406 URL: https://issues.apache.org/jira/browse/IGNITE-7406 Project: Ignite Issue

[jira] [Created] (IGNITE-7407) Cancelling Query notebook deletion doesn't work

Alexander Kalinin created IGNITE-7407: - Summary: Cancelling Query notebook deletion doesn't work Key: IGNITE-7407 URL: https://issues.apache.org/jira/browse/IGNITE-7407 Project: Ignite

[GitHub] ignite pull request #3372: Ignite-gg -13276 weak ref for group state in chec...

GitHub user DmitriyGovorukhin opened a pull request: https://github.com/apache/ignite/pull/3372 Ignite-gg -13276 weak ref for group state in checkpoint entry You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[jira] [Created] (IGNITE-7408) Document WAL changes

Andrey Gura created IGNITE-7408: --- Summary: Document WAL changes Key: IGNITE-7408 URL: https://issues.apache.org/jira/browse/IGNITE-7408 Project: Ignite Issue Type: Task Environment:

[jira] [Created] (IGNITE-7409) Rework exception handling in suspend()\resume() methods

Alexey Kuznetsov created IGNITE-7409: Summary: Rework exception handling in suspend()\resume() methods Key: IGNITE-7409 URL: https://issues.apache.org/jira/browse/IGNITE-7409 Project: Ignite

[jira] [Created] (IGNITE-7410) IgniteSparseDistributedMatrixMulBenchmark(Mul2) hangs

Ilya Suntsov created IGNITE-7410: Summary: IgniteSparseDistributedMatrixMulBenchmark(Mul2) hangs Key: IGNITE-7410 URL: https://issues.apache.org/jira/browse/IGNITE-7410 Project: Ignite

[GitHub] ignite pull request #3364: Ignite 2.4.1-merge-master-weakref-checkpointentry

Github user DmitriyGovorukhin closed the pull request at: https://github.com/apache/ignite/pull/3364 ---

Re: Irrelevant data in discovery messages

Guys, this config property allows to filter out system/env properties - org.apache.ignite.configuration.IgniteConfiguration#getIncludeProperties By default this returns null which is "include everything". Pass empty array to filter all or non-empty for filtering. --Yakov

Re: Irrelevant data in discovery messages

Thanks, Yakov! Maybe we should change the default behaviour? Any environment contains *PATH* and *java.class.path* variables at least, and they are not used by anybody. I don't think we should include them to node attributes by default. Denis пн, 15 янв. 2018 г. в 13:02, Yakov Zhdanov

Re: Irrelevant data in discovery messages

At least *java.net.preferIPv4Stack* parameter shouldn't be ignored. We check, that nodes have the same value of this parameter, and print a warning otherwise. It is pretty helpful sometimes. Maybe, some other parameters are also used internally. They should be added to node attributes regardless

[GitHub] ignite pull request #3375: Ignite 6891

GitHub user x-kreator opened a pull request: https://github.com/apache/ignite/pull/3375 Ignite 6891 You can merge this pull request into a Git repository by running: $ git pull https://github.com/x-kreator/ignite ignite-6891 Alternatively you can review and apply these

Username/password authentication for thin clients

Igniters, Current Ignite has no means for user authentication and authorization. I believe this is a big flaw in the product and we should start working on it. As a first step I would like to propose to add simple username/password authentication for our thin clients ("thin", JDBC, ODBC).

[GitHub] ignite pull request #3373: Assert on last fsync position

GitHub user agura opened a pull request: https://github.com/apache/ignite/pull/3373 Assert on last fsync position You can merge this pull request into a Git repository by running: $ git pull https://github.com/agura/incubator-ignite last_fsync_pos_assert Alternatively you

Re: Irrelevant data in discovery messages

What if we change default to empty array? Users that want to include everything will init it to null manually --Yakov

Re: BinaryObjectImpl.deserializeValue with specific ClassLoader

The ticket is on the radar, but not in immediate plans. The problem might sounds simple at first glance, but we already spent considerable time on implementation and review, because we heavily rely on classes caching, and a lot of internal BinaryMarshaller infrastructure should be reworked to

[GitHub] ignite pull request #3374: Ignite-7409 exception handling reworked for resum...

GitHub user voipp opened a pull request: https://github.com/apache/ignite/pull/3374 Ignite-7409 exception handling reworked for resuming active tx. You can merge this pull request into a Git repository by running: $ git pull https://github.com/voipp/ignite Ignite-7409

[jira] [Created] (IGNITE-7411) JDBC thin client selects NULL cache ID values of entries added with Java API

Alexey Kukushkin created IGNITE-7411: Summary: JDBC thin client selects NULL cache ID values of entries added with Java API Key: IGNITE-7411 URL: https://issues.apache.org/jira/browse/IGNITE-7411