Handling slashes in cache names

Hi all, I’m looking into https://issues.apache.org/jira/browse/IGNITE-7264, and I need some guidance on what’s the best way to approach it. The problem is that cache names are not restricted, but if persistence is enabled the cache needs to have a corresponding directory on the file system

Re: IGNITE-7107 Apache Ignite RPM packages

Hi, I think we should provide the same default configuration for all binary builds. From my point of view RPM/DEB/etc packages should use default configuration file like to standard binary release. On Mon, Dec 25, 2017 at 4:39 PM, Ilya Kasnacheev wrote: > Hello

Re: IGNITE-7107 Apache Ignite RPM packages

I agree with Andrey. The product should be identical regardless of how you download and install it. On Mon, Dec 25, 2017 at 7:18 AM, Andrey Gura wrote: > Hi, > > I think we should provide the same default configuration for all > binary builds. From my point of view RPM/DEB/etc

Jira access

Hello dear developers, I'm Pavel and I'm going to contribute to Apache Ignite (mostly tests at this time). Could someone please give me access to jira (https://issues.apache.org/jira/projects/IGNITE) my jira id is pkouznet Thanks, -Pavel

Re: IGNITE-7107 Apache Ignite RPM packages

Can we change default configuration file then? So that both binary and package deliveries contained PDS turned on by default? And what about Multicast Discovery? > On 25 Dec 2017, at 18:41, Dmitriy Setrakyan wrote: > > I agree with Andrey. The product should be

Re: IGNITE-7107 Apache Ignite RPM packages

PDS and discovery settings are unrelated to the packaging task. Andrey is right, just use existing default config. On Mon, Dec 25, 2017 at 6:51 PM, Petr Ivanov wrote: > Can we change default configuration file then? > So that both binary and package deliveries contained PDS

[jira] [Created] (IGNITE-7303) BaselineTopology: API to reset branching history

Sergey Chugunov created IGNITE-7303: --- Summary: BaselineTopology: API to reset branching history Key: IGNITE-7303 URL: https://issues.apache.org/jira/browse/IGNITE-7303 Project: Ignite

[jira] [Created] (IGNITE-7297) Javadoc warning for RProp in MLP

Yury Babak created IGNITE-7297: -- Summary: Javadoc warning for RProp in MLP Key: IGNITE-7297 URL: https://issues.apache.org/jira/browse/IGNITE-7297 Project: Ignite Issue Type: Bug

[GitHub] ignite pull request #3282: IGNITE 7297: Javadoc warning for RProp in MLP

GitHub user YuriBabak opened a pull request: https://github.com/apache/ignite/pull/3282 IGNITE 7297: Javadoc warning for RProp in MLP fixed You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7297

[GitHub] ignite pull request #3074: IGNITE-6904 SQL: partition reservations are relea...

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

Re: IGNITE-7203 Java 8 by default

I've ran some tests for Java 8 implementation comparison and need help of fellow igniters to look through the results. Run report follows. Branch: [1] Master: [2] Problem tests: 1. Branch 1. _Licenses & Javadoc — failed 2. Ignite Basic — execution timed out 3. Ignite Basic 2 —

[GitHub] ignite pull request #3282: IGNITE 7297: Javadoc warning for RProp in MLP

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

[GitHub] ignite pull request #3283: IGNITE-6742: + GridCleaner, using one in Platform...

GitHub user x-kreator opened a pull request: https://github.com/apache/ignite/pull/3283 IGNITE-6742: + GridCleaner, using one in PlatformMemoryPool You can merge this pull request into a Git repository by running: $ git pull https://github.com/x-kreator/ignite ignite-6742

Re: IGNITE-7203 Java 8 by default

As for _Licenses & Javadoc I already create https://issues.apache.org/jira/browse/IGNITE-7297 and will fix it ASAP. Regards, Yury -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[jira] [Created] (IGNITE-7300) Allow expressions in SQL INSERTs within transactions

Alexander Paschenko created IGNITE-7300: --- Summary: Allow expressions in SQL INSERTs within transactions Key: IGNITE-7300 URL: https://issues.apache.org/jira/browse/IGNITE-7300 Project: Ignite

Re: IGNITE-7203 Java 8 by default

Hi vveider, Some .NET build configurations have been updated recently in the main "Ignite 2.0 Tests" project, we'll have to copy these changes somehow, maybe just copy configurations to Java 8 project and remove old ones. Thanks, Pavel On Mon, Dec 25, 2017 at 12:17 PM, Yury Babak

[GitHub] ignite pull request #3286: IGNITE-7288 Thin client: partial cache configurat...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/3286 IGNITE-7288 Thin client: partial cache configuration You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7288

[jira] [Created] (IGNITE-7299) Document internal CREATE TABLE SQL command

Kirill Shirokov created IGNITE-7299: --- Summary: Document internal CREATE TABLE SQL command Key: IGNITE-7299 URL: https://issues.apache.org/jira/browse/IGNITE-7299 Project: Ignite Issue

[jira] [Created] (IGNITE-7301) .NET: Cluster auto activation (baseline topology)

Pavel Tupitsyn created IGNITE-7301: -- Summary: .NET: Cluster auto activation (baseline topology) Key: IGNITE-7301 URL: https://issues.apache.org/jira/browse/IGNITE-7301 Project: Ignite Issue

Re: IGNITE-7107 Apache Ignite RPM packages

Hello Igniters! What's your take on enabling PDS in 2.4 in default config? This way we could enable it in RPM build with easy heart. The rest of your answers seem spot on. I'll happily review your amended patch when it is ready (later this week?) -- Ilya Kasnacheev 2017-12-22 18:27 GMT+03:00

[jira] [Created] (IGNITE-7298) Web console: error on web agent start

Pavel Konstantinov created IGNITE-7298: -- Summary: Web console: error on web agent start Key: IGNITE-7298 URL: https://issues.apache.org/jira/browse/IGNITE-7298 Project: Ignite Issue

[GitHub] ignite pull request #3284: IGNITE-7261 MVCC disabled

GitHub user gvvinblade opened a pull request: https://github.com/apache/ignite/pull/3284 IGNITE-7261 MVCC disabled You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7261-mvcc-off Alternatively you

[GitHub] ignite pull request #3285: IGNITE-7261 MVCC enabled

GitHub user gvvinblade opened a pull request: https://github.com/apache/ignite/pull/3285 IGNITE-7261 MVCC enabled You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7261-mvcc-on Alternatively you can

[jira] [Created] (IGNITE-7302) SQL TX: Failed to query INFORMATIONAL_SCHEMA

Vladimir Ozerov created IGNITE-7302: --- Summary: SQL TX: Failed to query INFORMATIONAL_SCHEMA Key: IGNITE-7302 URL: https://issues.apache.org/jira/browse/IGNITE-7302 Project: Ignite Issue

[GitHub] ignite pull request #3172: IGNITE-7144 Java 9: fix build issue with tools.ja...

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

[GitHub] ignite pull request #3287: IGNITE-7287 Thin client: idle connection timeout

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/3287 IGNITE-7287 Thin client: idle connection timeout You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7287

Re: Handling slashes in cache names

My preference would be to prohibit forward and backward slashes in cache names altogether, as they may create a false feeling of some directory structure, which does not exist. We should also prohibit spaces as well. D. On Mon, Dec 25, 2017 at 7:09 AM, Stanislav Lukyanov

[GitHub] ignite pull request #3281: IGNITE-7296: Update RocketMQ dependencies to 4.2....

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

[jira] [Created] (IGNITE-7305) .NET: DataStorageConfiguration.WalBufferSize

Pavel Tupitsyn created IGNITE-7305: -- Summary: .NET: DataStorageConfiguration.WalBufferSize Key: IGNITE-7305 URL: https://issues.apache.org/jira/browse/IGNITE-7305 Project: Ignite Issue

[jira] [Created] (IGNITE-7304) Node discovery through AWS ELB

Bruno Barin created IGNITE-7304: --- Summary: Node discovery through AWS ELB Key: IGNITE-7304 URL: https://issues.apache.org/jira/browse/IGNITE-7304 Project: Ignite Issue Type: New Feature

[GitHub] ignite pull request #3288: IGNITE-4585 Support CLEAR command with REST

GitHub user samaitra opened a pull request: https://github.com/apache/ignite/pull/3288 IGNITE-4585 Support CLEAR command with REST You can merge this pull request into a Git repository by running: $ git pull https://github.com/samaitra/ignite IGNITE-4585 Alternatively you

IGNITE-7135 needs review

Hello community! I've implemented IGNITE-7135 doing two improvements: 1) control remote node startup (successful or not) through IgniteCluster.startNodes(); 2) keep the first Java principle working "Compile once, run everywhere" - from now running remotely on Windows also supported.

Re: Handling slashes in cache names

It also make sense to limit cache name length to reasonable length. Because some File systems could have limitations on path length. See: https://en.wikipedia.org/wiki/Filename#Length_restrictions On Tue, Dec 26, 2017 at 1:41 AM, Dmitriy Setrakyan wrote: > My preference

[GitHub] ignite pull request #3199: IGNITE-6740: Replaced direct sun.nio.ch.DirectBuf...

Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/3199 ---