Pavel Tupitsyn created IGNITE-6249:
--
Summary: .NET: IgniteConfiguration.ConsistentId
Key: IGNITE-6249
URL: https://issues.apache.org/jira/browse/IGNITE-6249
Project: Ignite
Issue Type: Impro
Igniters,
As you probably know, we are working on a new protocol for thin client. It
would allow users to create integrations with other languages and platforms
(e.g. Go, R, etc). This protocol should be simple enough, otherwise no-one
would ever implement anything on top of it.
There is a proble
Pavel Tupitsyn created IGNITE-6250:
--
Summary: .NET: Thin client: Exception handling
Key: IGNITE-6250
URL: https://issues.apache.org/jira/browse/IGNITE-6250
Project: Ignite
Issue Type: Improv
Vasiliy Sisko created IGNITE-6251:
-
Summary: Web console: Selection stay on removed user.
Key: IGNITE-6251
URL: https://issues.apache.org/jira/browse/IGNITE-6251
Project: Ignite
Issue Type: B
In my understanding such objects are completely fine.
Even typeId is not necessary, since we have
GridBinaryMarshaller.UNREGISTERED_TYPE_ID mode,
where full type name is included in binary object header.
My testing shows that Ignite works fine with such objects (including SQL).
Pavel
On Mon, Se
Sunny Chan created IGNITE-6252:
--
Summary: Cassandra Cache Store Session does not retry if prepare
statement failed
Key: IGNITE-6252
URL: https://issues.apache.org/jira/browse/IGNITE-6252
Project: Ignite
Ilya, go ahead with the plan you suggested.
--Yakov
Dmitriy,
No,
We should not keep obsolete repositories to provide urls to correct repo
.
We should remove this repo and create special Benchmarking page at site or
readme.io.
On Mon, Sep 4, 2017 at 8:03 AM, Dmitriy Setrakyan
wrote:
> Igniters,
>
> Can we simply update this page with a link to th
Pavel Tupitsyn created IGNITE-6253:
--
Summary: .NET: Replace Doxygen with DocFX for API documentation
generation
Key: IGNITE-6253
URL: https://issues.apache.org/jira/browse/IGNITE-6253
Project: Ignite
GitHub user sunnychanwork opened a pull request:
https://github.com/apache/ignite/pull/2583
IGNITE-6252 Cassandra Cache Store Session does not retry if statementâ¦
⦠failed
This patch will check to ensure that we retry any prepare statement failure
when we submit the asy
We already have similar ticket -
https://issues.apache.org/jira/browse/IGNITE-5653
I suggest we prioritize it.
--Yakov
>> Why are we throwing checked exceptions without any error message? Should
we fix it?
I don't think it is important. This exception is instantiated inside
IgniteUtils.cast() and has a cause.
--Yakov
Ilya Lantukh created IGNITE-6254:
Summary: Assertion error in
IgniteTxHandler.processDhtTxFinishRequest(...)
Key: IGNITE-6254
URL: https://issues.apache.org/jira/browse/IGNITE-6254
Project: Ignite
Pavel Tupitsyn created IGNITE-6255:
--
Summary: .NET: Fix TestAffinityCall to take late affinity
assignment into account
Key: IGNITE-6255
URL: https://issues.apache.org/jira/browse/IGNITE-6255
Project:
Anton,
In this case we'll break a links in blog posts. Let's to add note in
readme.md file (about that repository contains outdate benchmarks) and link
to a repo with actual version of benchmark.
On Mon, Sep 4, 2017 at 12:30 PM, Anton Vinogradov wrote:
> Dmitriy,
>
> No,
> We should not keep ob
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/2584
IGNITE-6254 : Fixed assertions for req.txState().
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6254
Alternat
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2567
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2514
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2563
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2552
---
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/2585
Ignite 6237
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6237
Alternatively you can review and apply the
Nikolay,
Got it. Let's make a Big Warning.
But, anyway, we should create special Benchmarking page at site or readme.io
.
On Mon, Sep 4, 2017 at 1:14 PM, Nikolai Tikhonov
wrote:
> Anton,
>
> In this case we'll break a links in blog posts. Let's to add note in
> readme.md file (about that repos
Hello, Yakov.
I made a bit of investigation about your proposal of handling filter and
transformer exceptions:
1. If we cancel continuous query from remote node user can't know it.
There is no public API to check "Is continuous query still alive?".
The only consequence of canceling query
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/2586
IGNITE-6237 created script for signing and uploading artifacts to remâ¦
â¦ote staging.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gr
Github user oleg-ostanin closed the pull request at:
https://github.com/apache/ignite/pull/2585
---
+1 to keep current behavior and start new thread to solve notification
issue.
On Mon, Sep 4, 2017 at 2:05 PM, Николай Ижиков
wrote:
> Hello, Yakov.
>
> I made a bit of investigation about your proposal of handling filter and
> transformer exceptions:
>
> 1. If we cancel continuous query from rem
>> In this case we'll break a links in blog posts. Let's to add note in
>> readme.md file (about that repository contains outdate benchmarks) and link
>> to a repo with actual version of benchmark.
I've already done it in this pull request:
https://github.com/apacheignite/yardstick-ignite/pull/6.
Alexandr Fedotov created IGNITE-6256:
Summary: When a node becomes segmented an AssertionError is thrown
during GridDhtPartitionTopologyImpl.removeNode
Key: IGNITE-6256
URL: https://issues.apache.org/jira/brow
Hello everyone!
My name is Ivan Fedotov, I'm new in Apache Ignite project and i want to
contribute to Apache Ignite. So, please give me the rights to do this.
This is my username in Jira: "ivanan".
Aleksei,
I see a lot of removals, not a warning.
On Mon, Sep 4, 2017 at 2:18 PM, Aleksei Zaitsev
wrote:
> >> In this case we'll break a links in blog posts. Let's to add note in
> >> readme.md file (about that repository contains outdate benchmarks) and
> link
> >> to a repo with actual version
Stanilovsky Evgeny created IGNITE-6257:
--
Summary: non thread safe assertion exception while
processDhtTxFinishRequest
Key: IGNITE-6257
URL: https://issues.apache.org/jira/browse/IGNITE-6257
Proje
Well, let's leave it as is for now, since I don't see any easy way to
consistently solve this.
--Yakov
Yakov, Anton, thank you!
2017-09-04 15:16 GMT+03:00 Yakov Zhdanov :
> Well, let's leave it as is for now, since I don't see any easy way to
> consistently solve this.
>
> --Yakov
>
--
Nikolay Izhikov
nizhikov@gmail.com
Pavel Tupitsyn created IGNITE-6258:
--
Summary: .NET: Thin client: Define metadata exchange protocol
Key: IGNITE-6258
URL: https://issues.apache.org/jira/browse/IGNITE-6258
Project: Ignite
Iss
GitHub user mcherkasov opened a pull request:
https://github.com/apache/ignite/pull/2587
Ignite 2.1.3.b7
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.1.3.b7
Alternatively you can review and app
Dmitriy,
I like the idea of ClusterActivator interface.
>From user perspective it provides the same functionality as the setter but
in more clear and intuitive way.
Also it gives us a good place to put all the documentation about the
feature.
Any other opinions?
On Fri, Sep 1, 2017 at 2:35 PM,
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/2588
IGNITE-6253 .NET: Replace Doxygen with DocFX for API documentation
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ign
> On Thu, Aug 24, 2017 at 2:02 PM, Dmitriy Setrakyan
> wrote:
>
>> I would delete all the code from the Yardstick repo to avoid confusion and
>> in the description of the repo ask users to download Ignite directly.
That's why. But for me it's OK just to add a warning. I think it's not
critical,
Denis Mekhanikov created IGNITE-6259:
Summary: GridServiceProcessor may leave futures hanging on
unstable topology
Key: IGNITE-6259
URL: https://issues.apache.org/jira/browse/IGNITE-6259
Project:
I think we should support and clearly document both modes, with and without
metadata.
On Mon, Sep 4, 2017 at 2:06 AM, Pavel Tupitsyn wrote:
> In my understanding such objects are completely fine.
>
> Even typeId is not necessary, since we have
> GridBinaryMarshaller.UNREGISTERED_TYPE_ID mode,
>
Dmitriy Setrakyan created IGNITE-6260:
-
Summary: Need to rename setDistributedJoins to
setNonCollocatedJoins
Key: IGNITE-6260
URL: https://issues.apache.org/jira/browse/IGNITE-6260
Project: Ignite
On Mon, Sep 4, 2017 at 3:05 AM, Yakov Zhdanov wrote:
> >> Why are we throwing checked exceptions without any error message? Should
> we fix it?
>
> I don't think it is important. This exception is instantiated inside
> IgniteUtils.cast() and has a cause.
>
Why not add the same message as in the
NPE should be fixed.
NPE does not have any message, this is why top level exception does not
have it as well.
--Yakov
2017-09-04 17:19 GMT+03:00 Dmitriy Setrakyan :
> On Mon, Sep 4, 2017 at 3:05 AM, Yakov Zhdanov wrote:
>
> > >> Why are we throwing checked exceptions without any error message?
On Mon, Sep 4, 2017 at 6:13 AM, Sergey Chugunov
wrote:
> Dmitriy,
>
> I like the idea of ClusterActivator interface.
>
> From user perspective it provides the same functionality as the setter but
> in more clear and intuitive way.
>
BTW, I made a naming mistake in the original email. The setter
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/2589
IGNITE-6255 .NET: Fix TestAffinityCall to take late affinity assignment
into account
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupits
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/2590
IGNITE-5817 Changed checksum calculation methods
(cherry picked from commit 28fb8c8)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridga
Guys, if the code is wrong, let's remove it and add a warning on the
readme.md clearly stating where to go for the correct benchmarks.
Also, huge +1 for adding benchmarking page to readme.
D.
On Mon, Sep 4, 2017 at 6:37 AM, Aleksei Zaitsev
wrote:
> > On Thu, Aug 24, 2017 at 2:02 PM, Dmitriy Se
On Mon, Sep 4, 2017 at 7:30 AM, Yakov Zhdanov wrote:
> NPE should be fixed.
>
Can someone in the community create a sensible ticket here? If I do it, it
might lack proper context.
>
> NPE does not have any message, this is why top level exception does not
> have it as well.
>
Got it.
>
> --
Github user BiryukovVA closed the pull request at:
https://github.com/apache/ignite/pull/2415
---
GitHub user BiryukovVA reopened a pull request:
https://github.com/apache/ignite/pull/2415
IGNITE-5865: Test fixed.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/BiryukovVA/ignite IGNITE-5865
Alternatively you can review and a
Igniters,
All fixes related to release 2.2 merged.
But,
we still waiting for changes related to new release process (
https://issues.apache.org/jira/browse/IGNITE-5249).
Beta version of "new release process" will be used to release 2.2, final
changes will be merged to 2.3.
On Fri, Sep 1, 2017
Prachi,
I've published on github example with configured JCL logger. Please, have a
look: https://github.com/TikhonovNikolay/jcl-ignite-example
On Sat, Sep 2, 2017 at 12:36 AM, Prachi Garg wrote:
> Yes, I tried using it, but strangely this is the output I get when use
> -DIGNITE_QUIET=false
> (
GitHub user alexpaschenko opened a pull request:
https://github.com/apache/ignite/pull/2591
IGNITE-5703
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5703
Alternatively you can review and apply th
Hello, Ivan!
Welcome to the Ignite community!
You should get familiar with Ignite development process described here:
https://cwiki.apache.org/confluence/display/IGNITE/Development+Process
Instructions on how to contribute can be found here:
https://cwiki.apache.org/confluence/display/IGNITE/How
GitHub user BiryukovVA opened a pull request:
https://github.com/apache/ignite/pull/2592
Fixed wrong partitioning.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/BiryukovVA/ignite TestPessimisticDD
Alternatively you can review
Cross sending to dev@ list.
Igniters, can you please check my analysis in the thread on the user@ list
and see if it is plausible?
D.
-- Forwarded message --
From: Dmitriy Setrakyan
Date: Mon, Sep 4, 2017 at 4:17 PM
Subject: Re: Specifying location of persistent storage location
Pranas Baliuka created IGNITE-6261:
--
Summary: ODBC support for Mac OSX
Key: IGNITE-6261
URL: https://issues.apache.org/jira/browse/IGNITE-6261
Project: Ignite
Issue Type: Wish
Comp
I have configured log4j, log4j-2 in our environment, can share additional
details here if you need it.
On Mon, Sep 4, 2017 at 11:54 AM, Nikolai Tikhonov
wrote:
> Prachi,
>
> I've published on github example with configured JCL logger. Please, have a
> look: https://github.com/TikhonovNikolay/jcl
Valentin, Nikolai,
I have published my example on github -
https://github.com/pgarg/myIgniteExamples
On Mon, Sep 4, 2017 at 7:57 PM, Rishi Yagnik wrote:
> I have configured log4j, log4j-2 in our environment, can share additional
> details here if you need it.
>
> On Mon, Sep 4, 2017 at 11:54 AM
Folks,
Let's discuss how this should be handled properly. I proposed to use the
same format as regular binary object, with all data being written in "raw"
form. This would give us one critical advantage - we will be able to work
with such objects without deserialization on the server. Hence, no cl
60 matches
Mail list logo
