Ivan Daschinskiy created IGNITE-8120:
Summary: Improve test coverage of rebalance failing
Key: IGNITE-8120
URL: https://issues.apache.org/jira/browse/IGNITE-8120
Project: Ignite
Issue Typ
Pavel Konstantinov created IGNITE-8121:
--
Summary: Web console: import cluster from database doesn't work
correctly for second import
Key: IGNITE-8121
URL: https://issues.apache.org/jira/browse/IGNITE-8121
Igniters,
Thanks to Alex Kuznetsov, we revealed serious usability issue in our thin
JDBC driver - we user ampersand character to delimit properties:
jdbc:ignite:thin://host:port/schema?param1=val1*&*param2=val2
This leads to multiple problems:
1) This format is unusable from many console environ
I do not see any additional risks provided that authentication and
authorization will be integrated with thin clients in the same way it is
done for "thick" clients.
On Tue, Apr 3, 2018 at 7:40 AM, Dmitriy Setrakyan
wrote:
> Val, my preference would be not to have compute functionality on thin
>
Vladimir,
If we will use parentheses, do we really need "?" symbol? It looks
redundant for me in case of parentheses.
jdbc:ignite:thin://host:port/schema?(param1=val1)(param2=val2)
vs
jdbc:ignite:thin://host:port/schema(param1=val1)(param2=val2)
What do you think?
On Tue, Apr 3, 2018 at 3:30
Hi,
1. Mysql JDBC driver Conenctor/J [1] and postgres JDBC driver [2] use
ampersand to delimit properties.
2. Mysql use regular URL encoding for properties values instead of
legacy escaping (e.g braces etc.)
3. Microsoft JDBC (and ODBC) driver for SQL Server [3] use semicolon to
delimit and sq
GitHub user voipp opened a pull request:
https://github.com/apache/ignite/pull/3738
patch
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/voipp/ignite IGNITE-7481-patch
Alternatively you can review and apply these changes as the
Taras,
I spent today 30 minutes trying to connect to cluster with sqlline in Power
Shell :(
I predict 100500+ questions on user list about "Failed to connect in bash /
cmd / powershell with sqlline"
On Tue, Apr 3, 2018 at 3:55 PM, Taras Ledkov wrote:
> Hi,
>
> 1. Mysql JDBC driver Conenctor/
Hello!
I think semicolon is the way to go, since round brackets are often
interpreted by shells and will need escaping on their own. Let's get rid of
& and ?.
jdbc:ignite:thin://host:port/schema:param1=val1:param2=val2
--
Ilya Kasnacheev
2018-04-03 11:30 GMT+03:00 Vladimir Ozerov :
> Igniters
Pavel Kovalenko created IGNITE-8122:
---
Summary: Partition state restored from WAL may be lost if no
checkpoints are done
Key: IGNITE-8122
URL: https://issues.apache.org/jira/browse/IGNITE-8122
Projec
Hi,
We've been solve this problem during JDBC2 driver implementation. And
I don't know any complains about connection string format. Why we can
just use the same approach? [1]
[1]
https://issues.apache.org/jira/browse/IGNITE-1250?focusedCommentId=14706511&page=com.atlassian.jira.plugin.system.is
Pavel Konstantinov created IGNITE-8123:
--
Summary: Web console: incorrect text after all clusters have been
deleted
Key: IGNITE-8123
URL: https://issues.apache.org/jira/browse/IGNITE-8123
Project:
Pavel Konstantinov created IGNITE-8124:
--
Summary: Web console: incorrect text after all clusters have been
deleted
Key: IGNITE-8124
URL: https://issues.apache.org/jira/browse/IGNITE-8124
Project:
Siddarth sreeni created IGNITE-8125:
---
Summary: Returns null on cache querying on column type PGOBJECT
(JSONB) superset or @>
Key: IGNITE-8125
URL: https://issues.apache.org/jira/browse/IGNITE-8125
P
Pavel Konstantinov created IGNITE-8126:
--
Summary: Web console: the method 'LoadCaches' should not be
generated if cache doesn't contain cache store configuration
Key: IGNITE-8126
URL: https://issues.apache.or
GitHub user NSAmelchev opened a pull request:
https://github.com/apache/ignite/pull/3739
IGNITE-1776
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/NSAmelchev/ignite ignite-1776
Alternatively you can review and apply these chan
GitHub user SpiderRus opened a pull request:
https://github.com/apache/ignite/pull/3740
ignite-8049 Limit the number of operation cycles in B+Tree
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/SpiderRus/ignite ignite-8049
Alte
Alexey,
could you please create code review in Upsource? The PR is huge and it
would be great to have an ability to discuss changes in more
convenient way.
Thanks.
On Tue, Apr 3, 2018 at 12:42 AM, Dmitriy Setrakyan
wrote:
> I looked into the ticket and do not understand this property
> name: Ro
Hi Igniters,
Following issues for tests fixing seems have no progress . Mainteiners,
please address.
https://issues.apache.org/jira/browse/IGNITE-7766
- Alexei Scherbakov - not responding, if contributor is not interested in
this test anymore, probably we should remove it from code base?
https:/
Alexey Popov created IGNITE-8127:
Summary: .NET: Fix flaky test
ClientConnectionTest.TestClientDisposeWhileOperationsAreInProgress
Key: IGNITE-8127
URL: https://issues.apache.org/jira/browse/IGNITE-8127
Hello Ignite Community!
My name is Denis Garus. I want to contribute to Apache Ignite.
I would like to start with ticket
https://issues.apache.org/jira/browse/IGNITE-8111.
My Jira ID: garus.d.g
Thanks!
---
Это сообщение проверено на вирусы антивирусом Avast.
https://www.avast.com/antivir
Dmitriy Pavlov created IGNITE-8128:
--
Summary: PDS Indexing suite timeout: failure handler
incomatibility with test code
Key: IGNITE-8128
URL: https://issues.apache.org/jira/browse/IGNITE-8128
Projec
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/3741
IGNITE-8128 Use StopNodeFailureHandler in tests where required.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-81
Hello Denis,
Welcome to the Ignite community! I have added you to the contributors list,
you should be able to assign the issue now.
Thanks,
AG
2018-04-03 16:08 GMT+03:00 Yandex Mail :
> Hello Ignite Community!
>
>
>
> My name is Denis Garus. I want to contribute to Apache Ignite.
>
> I would l
Hi Igniters,
Thanks to all who assigned tickets. All excepting Data Structure failures
and https://issues.apache.org/jira/browse/IGNITE-8089 is now assigned.
Your contributions will help to improve TeamCity resutls so we could avoid
new failures introduction.
Sincerely,
Dmitriy Pavlov
пт, 30 ма
Hello Ignite Community!
My name is Anton Kurbanov and I want to contribute to Apache Ignite.
I would like to begin with ticket
https://issues.apache.org/jira/browse/IGNITE-8110.
My Jira ID is: antkr
Best regards,
Anton
Github user isapego closed the pull request at:
https://github.com/apache/ignite/pull/3708
---
Hello Anton,
Welcome to the Ignite community! I've added you to the list, please go
ahead with the ticket!
Thanks,
AG
2018-04-03 17:59 GMT+03:00 Anton Kurbanov :
> Hello Ignite Community!
>
> My name is Anton Kurbanov and I want to contribute to Apache Ignite.
>
> I would like to begin with tic
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3741
---
Hi, Igniters!
I got into the task [1] in agreement with Dmitry.
I’ve prepared the PR [2] with following changes:
- added Apache 2.0 license to the header of each file
- replaced prefix ‘Grid’ by ‘Ignite’ in class names
- added README.md with a simple description
- changed version 2.6.3 -> 3.0.0 b
Awesome!
Dmitriy,
please confirm donation and apply the patch.
BTW, we can relocate plugin to apache repo like we did for release scripts
[1].
[1] https://github.com/apache/ignite-release
2018-04-03 19:28 GMT+03:00 Vyacheslav Daradur :
> Hi, Igniters!
>
> I got into the task [1] in agreement
Vladimir, Taras,
Will "@" work for us as the delimiter? I would agree with Andrey to reuse
this approach for the thin client.
As for the breaking changes, if update the delimiter for the next driver
version and make sure that version understands 2 delimiters for some time
(& and the new one), the
Thank you, Vyaceslav.
Excellent patch, I've applied PR to
https://github.com/dspavlov/ignite-abbrev-plugin
If we want code style will be learned by all contributors, this donation is
unavoidable.
Dmitriy S,
what do you think?
Lets keep current code base in my github and add build and link to b
Vladimir, why can't we support both, the "&" and whatever other character
we choose? This way it will not be a breaking change.
D.
On Tue, Apr 3, 2018 at 1:30 AM, Vladimir Ozerov
wrote:
> Igniters,
>
> Thanks to Alex Kuznetsov, we revealed serious usability issue in our thin
> JDBC driver - we
Anton, I also agree here.
Personal github repo is ok for very beginning of tool development, but
eventually apache repo is better.
вт, 3 апр. 2018 г. в 19:46, Anton Vinogradov :
> Awesome!
>
> Dmitriy,
> please confirm donation and apply the patch.
>
> BTW, we can relocate plugin to apache repo
Dmitriy G., Alex G.,
Reminder. Still hope to get an answer to the question below.
--
Denis
On Fri, Mar 30, 2018 at 10:04 AM, Denis Magda wrote:
> Dmitriy G., Alexey,
>
> What happens with CacheMetrics.getOffHeapAllocatedSize metric? Don't see
> it mentioned in the tickets.
>
>- Will it ret
GitHub user antkr opened a pull request:
https://github.com/apache/ignite/pull/3742
IGNITE-8110
Fixed ms to nanos transformation.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8110
Alternatively yo
Denis,
actually params (key-value pairs) are separated by colon in provided
JIRA issue comment.
On Tue, Apr 3, 2018 at 7:55 PM, Denis Magda wrote:
> Vladimir, Taras,
>
> Will "@" work for us as the delimiter? I would agree with Andrey to reuse
> this approach for the thin client.
>
> As for the
Dmitry,
I just think that it's natural to have this functionality and that it would
drastically increase flexibility of thin client. Multiple requests from
users (one of them in this thread) seem to confirm this. At the same time,
I don't see much technical challenge here (like with near caches or
GitHub user Mikhail1988 opened a pull request:
https://github.com/apache/ignite/pull/3743
Ignite 1.9.11.b2
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-1.9.11.b2
Alternatively you can review and
GitHub user kukushal opened a pull request:
https://github.com/apache/ignite/pull/3744
Gg 13379 dev
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite gg-13379-dev
Alternatively you can review and apply these
41 matches
Mail list logo
