Same thing with package manager for .NET (NuGet).
And same with Java, actually (Maven).
In my understanding, most people use package managers and don't download
ZIP archives.
Package managers are more convenient and easy to use. It is a modern way.
On Sun, Jun 17, 2018 at 11:28 AM, Aleksandr
partition
> > is "hash(key) % partitions". This is all we need to make default affinity
> > work.
> >
> > On Thu, Jun 14, 2018 at 11:41 AM, Pavel Tupitsyn
> > wrote:
> >
> > > AffinityFunction interface has the following method:
> > >
or will
> >turn a special flag in the response suggesting the client do that
> > manually.
> >
> > Igor, is this what you're suggesting?
> >
> > --
> > Denis
> >
> > On Wed, Jun 13, 2018 at 11:31 AM Pavel Tupitsyn
> > wrote:
>
Hi Igor,
How can we invoke the affinity function on the client, if we don't have the
implementation at hand?
Am I missing something?
Thanks,
Pavel
On Wed, Jun 13, 2018 at 5:34 PM, Igor Sapego wrote:
> Hi, Igniters,
>
> Currently, I'm working on the thin C++ client implementation.
> As you
Vladimir,
Not sure I see the point of 2 release policy.
It is not very good both for users and developers.
* Developers still have the burden on maintaining multiple protocol versions
* Users are quite limited with version choices
We should either go with a full-blown versioning so any client
NuGet (.NET) packages pushed:
https://www.nuget.org/packages?q=Apache.Ignite
On Tue, May 29, 2018 at 8:59 PM, Andrey Gura wrote:
> Dmitry,
>
> First we should check docker images. Also we are waiting for
> publishing of artifacts to Maven Central.
>
> On Tue, May 29, 2018 at 8:24 PM, Dmitriy
ncerely,
> Dmitriy Pavlov
>
> вт, 29 мая 2018 г. в 10:49, Pavel Tupitsyn :
>
> > Dmitry, the fix looks good to me, I would appreciate if you merge it.
> >
> > Thanks,
> > Pavel
> >
> > On Tue, May 29, 2018 at 12:02 AM, Dmitry Pavlov
> > wrote:
>
org/jira/browse/IGNITE-8604
> https://github.com/apache/ignite/pull/4072
>
> If you have some time you can apply the PR, or I will merge it later.
>
> Sincerely,
> Dmitriy Pavlov
>
> пн, 28 мая 2018 г. в 23:45, Pavel Tupitsyn :
>
> > Hi Dmirty,
> >
> > I
Hi Dmirty,
IGNITE-5789 merge [1] introduces this bug:
Additional cache is being started from a template (cache name ends with *).
Normally template caches are only started when a cache with matching name
has been requested.
Pavel
[1]
Hi,
No, there is no Entity Framework Core support for now.
Pavel
On Fri, May 25, 2018 at 10:14 AM, wales wang wrote:
> Hi, guys:
>
>
> I want to used Apache.Ignite.EntityFramework in the .net core 2.0,
> but this component does not support .net core 2.0.
>
>
> Is there a version
+1 (binding)
Checked .NET side of things: build from sources, run examples.
On Thu, May 24, 2018 at 8:59 PM, Andrey Gura wrote:
> Igniters,
>
> We've uploaded a 2.5.0 release candidate to
> https://dist.apache.org/repos/dist/dev/ignite/2.5.0-rc1/
>
> Git tag name is
>
Pavel Tupitsyn created IGNITE-8608:
--
Summary: .NET: Sign release NuGet packages
Key: IGNITE-8608
URL: https://issues.apache.org/jira/browse/IGNITE-8608
Project: Ignite
Issue Type
Pavel Tupitsyn created IGNITE-8588:
--
Summary: .NET: Serialization issue when derived type hides base
type member
Key: IGNITE-8588
URL: https://issues.apache.org/jira/browse/IGNITE-8588
Project
r humans. Of course, we are
> > to stay with XML if switching to another configuration format requires
> > significant effort.
> >
> > BTW, first time I heard about JSON from [1] : " JSON is like XML, except
> it
> > doesn't suck ".
> >
> > [1] https://
Hi Igor,
Thanks for creating this!
One question: what is `Multithreading` feature?
Pavel
On Tue, May 15, 2018 at 9:45 PM, Denis Magda wrote:
> Igor,
>
> That's a valid point. Will see how it goes. As for the new documentation
> engine, there are no more arguments. We will
gt; >> For servers, adding another configuration format just to make
> it
> > > > more
> > > > > > >> familiar to users with no Java background seems unreasonable
> to
> > me
> > > > > > >> as well, as there still going to b
Dmitriy,
We don't need to support different config formats on server in order to add
that to thin clients.
Thin client protocol provides a way to create a cache with custom config
[1].
It is up to thin client library authors to use any config format they like
and then convert it into
Hi,
The doc is misleading, method "bool Remove(TK key)" does not return removed
element,
just the flag indicating whether removal happened or not.
On Wed, May 9, 2018 at 4:06 AM, Raymond Wilson
wrote:
> I have some code the removes elements from a cache, and I’d
Igniters,
There is an unpleasant bug in .NET [1]:
Services do not work at all on .NET Core and sometimes on classic .NET.
I'm almost done with the fix and I think we should include it in 2.5. Users
are complaining [2].
[1] https://issues.apache.org/jira/browse/IGNITE-8434
[2]
Pavel Tupitsyn created IGNITE-8434:
--
Summary: .NET: Service proxies do not work on .NET Core
Key: IGNITE-8434
URL: https://issues.apache.org/jira/browse/IGNITE-8434
Project: Ignite
Issue
Hi Amir,
I have filed [1] for multimap in .NET, it will be done later.
In order to fix IgniteParityTest failures, please add the following to
MissingMembers array there:
"multimap" // IGNITE-8425
Thanks,
Pavel
[1] https://issues.apache.org/jira/browse/IGNITE-8425
On Sun, Apr 29, 2018 at
Pavel Tupitsyn created IGNITE-8425:
--
Summary: .NET: IIgnite.GetMultimap
Key: IGNITE-8425
URL: https://issues.apache.org/jira/browse/IGNITE-8425
Project: Ignite
Issue Type: Bug
Hi Aleksandr,
This is awesome, thank you!
However, let's make it clear that this client supports SQL only,
and none of the other Thin Client protocol features.
Pavel
On Mon, Apr 23, 2018 at 10:41 PM, Aleksandr Sokolovskii
wrote:
> Hi Oleg,
>
> Thanks for your answer.
>
> >
t's unclear for me at the moment, why do we
> get "System.InvalidOperationException: Grid is in invalid state to
> perform this operation...", but let's merge the fix [1] for
> TestTxRollbackOnly first.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-8312
>
>
Igniters, Andrey G, Andrey K,
.NET Core Linux tests started to fail and end prematurely (296 of 959 tests
started)
on 18 April, and looks like it is caused by IGNITE-7770 [1], because this
is related to transactions.
I would highly appreciate if you have a look.
Let me know if you need help with
Pavel Tupitsyn created IGNITE-8328:
--
Summary: .NET: Thin client: Run in browser with Blazor
Key: IGNITE-8328
URL: https://issues.apache.org/jira/browse/IGNITE-8328
Project: Ignite
Issue
Great job, Petr!
FYI: myget credentials can be found in [1] (PMC only)
[1] https://svn.apache.org/repos/private/pmc/ignite/credentials/myget.org
On Mon, Apr 16, 2018 at 11:49 AM, Petr Ivanov wrote:
> Hi, Igniters!
>
>
> I’m glad to inform that starting today Apache Ignite
Pavel Tupitsyn created IGNITE-8240:
--
Summary: .NET: Use default scheduler when starting Tasks
Key: IGNITE-8240
URL: https://issues.apache.org/jira/browse/IGNITE-8240
Project: Ignite
Issue
you please double check that everything is ok now? Here is latest run
> including fix:
> https://ci.ignite.apache.org/viewLog.html?buildId=1192257;
> tab=buildResultsDiv=IgniteTests24Java8_
> IgnitePlatformNetCoreLinux
>
> 2018-04-11 17:17 GMT+03:00 Pavel Tupitsyn <ptupit...@apache.org
Igniters,
There is JVM crash in .NET Core Linux tests [1] after IGNITE-7871 merge [2].
Pavel Kovalenko, Alexey Goncharuk, please have a look.
In the log [3] there are some details:
Unknown connection detected (is some other software connecting to this
Ignite port? missing SSL configuration on
> Pavel Tupitsyn, what about .NET stuff ?
1) Thank you for filing the ticket, personally I have no plans to work on
it in the near future.
2) .NET tests fail, please make sure they are fixed before merging:
https://ci.ignite.apache.org/viewLog.html?buildId=1175956
TransactionsParityTest sho
Vladimir, can you clarify your ideas from Apache projects standpoint?
Do you propose (1) to create new apache projects for every client (or for
all of them)
Or (2) move thin clients OUT of Apache ecosystem and simply host them on
Github?
I think none of these will fly with ASF.
I am strongly for
etr Ivanov <mr.wei...@gmail.com> wrote:
> No, currently nightly maven artifacts are not uploaded anywhere.
> Yet, I’d like to research firstly Apache’s way of storing and providing
> nightly artifacts.
>
>
> > On 30 Mar 2018, at 11:11, Pavel Tupitsyn <ptupit...@apac
By the way, MyGet supports Maven.
- Do we put nightly Maven artifacts somewhere already?
- If not, should we put them on MyGet?
On Fri, Mar 30, 2018 at 11:09 AM, Pavel Tupitsyn <ptupit...@apache.org>
wrote:
> Awesome, I like that version reflects the date!
>
> On Fri, Mar 30, 2
yget.org/gallery/apache-ignite-net-nightly
>
>
>
> > On 29 Mar 2018, at 10:10, Pavel Tupitsyn <ptupit...@apache.org> wrote:
> >
> > Hi Petr,
> >
> > Sure, please go ahead.
> > That was a temporary solution which has become permanent :)
> >
> >
Hi Petr,
Sure, please go ahead.
That was a temporary solution which has become permanent :)
Thank you,
Pavel
On Wed, Mar 28, 2018 at 3:02 PM, Petr Ivanov wrote:
> Hi, Pavel!
>
>
> While working on moving TC tests to new scheme, I stumbled across this
> build chain ([1] ->
mp; for java thin client.
> > >
> > > I'll add documentation for user authentication ASAP. Please feel free
> to
> > > contact if you need more info till documentation is added.
> > >
> > > [1]. https://issues.apache.org/jira/browse/IGNITE-7421
> >
?
Thanks,
Pavel
On Fri, Mar 23, 2018 at 6:44 PM, Pavel Tupitsyn <ptupit...@apache.org>
wrote:
> Thanks, got it, will do.
>
> On Fri, Mar 23, 2018 at 4:36 PM, Dmitry Pavlov <dpavlov@gmail.com>
> wrote:
>
>> Hi Pavel,
>>
>> Related ticket is http
Thanks, got it, will do.
On Fri, Mar 23, 2018 at 4:36 PM, Dmitry Pavlov <dpavlov@gmail.com>
wrote:
> Hi Pavel,
>
> Related ticket is https://issues.apache.org/jira/browse/IGNITE-7436
>
> Sincerely,
> Dmitriy Pavlov
>
> пт, 23 мар. 2018 г. в 16:24, Pavel
Please provide description in IGNITE-8034 and link Java-side ticket there.
On Fri, Mar 23, 2018 at 4:23 PM, Pavel Tupitsyn <ptupit...@apache.org>
wrote:
> Hi Vladimir,
>
> Can you provide more details?
> * What does it do?
> * Do we need to only propagate the flag to .NE
Hi Vladimir,
Can you provide more details?
* What does it do?
* Do we need to only propagate the flag to .NET or do anything else?
* Related ticket?
Thanks,
Pavel
On Fri, Mar 23, 2018 at 2:25 PM, Vladimir Ozerov
wrote:
> Pavel,
>
> We introduced new flag
Hi Alexei,
> Pavel Tupitsyn, could you lend a hand to help completing .NET part (two
new
public API methods are added as a part of working on [3], java code in
branch [2])
Please file a separate ticket for .NET changes.
I would like to help, but maybe some time later. No need to delay y
Hi,
The problem is introduced by our freshman committer Nikolay Izhikov in
"IGNITE-7756: IgniteUuid added to predefined types" [1]
IgniteUuid type id has changed on Java side, but not in .NET.
I have pushed the fix to master branch.
I can only ask everyone again to have some respect for your
vices,
> streaming, ML), then go for the regular client which is battle-tested and
> available for usage.
>
> --
> Denis
>
>
>
> On Wed, Mar 14, 2018 at 1:33 PM, Pavel Tupitsyn <ptupit...@apache.org>
> wrote:
>
> > Hi Denis,
> >
> > > There a
issing header for
> >>>>>> ignite.repo file and formatting is also wrong.
> >>>>>> Otherwise — I’m able to install and run Apache Ignite from RPM from
> >> ASF
> >>>>>> according to manual.
> >>>>>>
&g
at 15:41, Petr Ivanov <mr.wei...@gmail.com> wrote:
> >
> > I see. Will wait for result tomorrow.
> >
> >
> >
> >> On 15 Mar 2018, at 15:40, Pavel Tupitsyn <ptupit...@apache.org> wrote:
> >>
> >> Just waiting for automatic build in
Just waiting for automatic build in master branch
On Thu, Mar 15, 2018 at 3:39 PM, Petr Ivanov <mr.wei...@gmail.com> wrote:
> Nice news, Pavel!
>
> Can you point to the exact build where you are checking changes, please?
>
>
>
> > On 15 Mar 2018, at 15:34, Pavel
Hi Petr,
I've fixed that yesterday [1], waiting for the build to verify.
[1]
https://github.com/apache/ignite/commit/a69e1acba8a69f1818fa9182a1167302f81b93ec
On Thu, Mar 15, 2018 at 1:07 PM, Petr Ivanov wrote:
> HI, Pavel.
>
>
> After TeamCity update from 2017.1.3 to
I think there were plans to eventually cover whole set of existing APIs in
Thin Client mode.
Some APIs may be difficult to add (like Compute Task), but basic compute
methods (non-Task based) are easy to do.
On Wed, Mar 14, 2018 at 11:33 PM, Pavel Tupitsyn <ptupit...@apache.org>
wrote:
Hi Denis,
> There are no any plans for that level of support
Why do you think so?
We already have ScanQuery with filter in .NET Thin Client, which involves
remote code execution on server nodes.
It is quite similar to Compute.Broadcast and such.
Thanks,
Pavel
On Wed, Mar 14, 2018 at 11:32 PM,
> devise better solution for pointing to fresh release artifacts.
> >
> >
> >
> > > On 12 Mar 2018, at 13:24, Pavel Tupitsyn <ptupit...@apache.org> wrote:
> > >
> > > Hi Vladimir,
> > >
> > > I see the link for 2.4.0 on https://ig
t;:
>
>> Hi Pavel,
>>
>> Thank you!
>>
>> Let's wait for fix at TeamCity.
>>
>> Sincerely,
>> Dmitriy Pavlov
>>
>> пн, 5 мар. 2018 г. в 19:09, Pavel Tupitsyn <ptupit...@apache.org>:
>>
>>> Hi Dmitry,
>>>
n Mon, Mar 12, 2018 at 10:51 AM, Vladimir Ozerov <voze...@gridgain.com>
> wrote:
>
> > Igniters,
> >
> > Apache Ignite 2.3.0 release (RC1) has been accepted.
> >
> > 5 "+1" binding votes received:
> > - Alexey Goncharuk
> > - Alexey Ku
trics (fail rate 2,9%)
>
>Ignite Platform .NET [ tests 1 ]
> exe: CacheMetricsParityTest.TestCacheMetrics (fail rate 1,9%)
>
> Please see https://issues.apache.org/jira/browse/IGNITE-7773
>
> Igniters, who can help with adding this metric to .NET?
>
> Sincerely,
&g
Igniters, Alexey G, Pavel K,
IGNITE-6113 changes [1] caused broken .NET test [2]
Have you run TeamCity before merging?
Please fix this.
When new APIs are added to Java you should:
a) add them to .NET as well
- or -
b) file a ticket and update .NET test (see how in CacheParityTest.cs we
have a
Hi Raymond,
This is planned, but not yet implemented:
https://issues.apache.org/jira/browse/IGNITE-6707
Pavel
On Wed, Mar 7, 2018 at 5:56 AM, Raymond Wilson
wrote:
> … the reason I ask being that ML is included in the Ignite diagram in the
> Ignite.C# documentation
se it affected UX, so IMO it is important to
> notify
> > users about the fix.
> >
> > On Tue, Mar 6, 2018 at 10:30 AM, Pavel Tupitsyn <ptupit...@apache.org>
> > wrote:
> >
> > > Regarding release notes:
> > >
> > > 1.
Regarding release notes:
1. No changes in Ignite.C++?
2. > Fixed output of big numbers in SQL query results
Are we including trivial bugfixes now?
On Tue, Mar 6, 2018 at 10:26 AM, Pavel Tupitsyn <ptupit...@apache.org>
wrote:
> +1
>
> Checked Ignite.NET:
> * Build from
+1
Checked Ignite.NET:
* Build from sources
* Download binaries and run examples
* Build NuGet packages on TeamCity [1] and test them
[1] https://ci.ignite.apache.org/viewLog.html?buildId=1126956
On Mon, Mar 5, 2018 at 10:42 PM, Vladimir Ozerov
wrote:
> Igniters,
>
> We
Hi Igor,
This build did not make much sense anyway:
1) (At least) platform artifacts (.NET) can't be built there, so the
package is incomplete
2) We have TeamCity, why duplicate maintenance efforts?
Nightly release builds are very useful, but they should be done on TeamCity.
(We have them for
Agree with Vladimir and Denis.
I don't think JSON has any place in the thin client protocol,
which is a binary protocol designed to be efficient, with clearly defined
data format.
We already have JSON in "REST" client.
On Thu, Mar 1, 2018 at 8:15 PM, Denis Magda wrote:
>
> This is not part of protocol specification. Please refer to .NET client
> where it is already implemented. *Pavel*, do we have docs for this?
I don't think we have docs for SLL.
These docs should be common for any type of client (ODBC/JDBC/...),
and this is mostly about configuring certificates
Hi Dmitry,
Thanks for bringing this up.
Please see the build log, it indicates failed Java build:
Failed to execute goal
org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process
(default) on project ignite-storm: Error resolving project artifact: Could
not transfer artifact
ct name (table name, column name, etc.) are
>> > > converted to upper case by default. This is expected behavior of every
>> > SQL
>> > > engine. If you want to preserve cases please consider using qoutes
>> around
>> > > column names (e.g. CRE
Hi Alexey,
1) IMO for this task you should ALWAYS work in binary mode.
What is the use case for deserializing with a real class and then
serializing to JSON?
Looks like a waste of resources to me.
2) This should not be the case, please re-check your code.
Binary meta preserves original case
Igniters,
Any update on the 2.4 release status? Anything else to merge there?
Pavel
On Mon, Feb 19, 2018 at 9:30 PM, Dmitriy Setrakyan
wrote:
> On Mon, Feb 19, 2018 at 1:37 AM, Vladimir Ozerov
> wrote:
>
> > Alex,
> >
> > You get me right. DEFAULT
/IGNITE/Continuous+Integration
>
> I'll create new topic once it will be ready.
>
> SIncerely,
> Dmitriy Pavlov
>
> ср, 21 февр. 2018 г. в 10:26, Pavel Tupitsyn <ptupit...@apache.org>:
>
> > Dmitry, thanks for the explanation, this makes sense.
> >
> >
each case?
>
> 2) Which .Net test suite may be applicable to be included into 'run basic
> tests' (requires <30 min to run, no failed test, no flaky test with fail
> rate >1%) ?
>
> Sincerely,
> Dmitriy Pavlov
>
> пн, 19 февр. 2018 г. в 0:39, Pavel Tupitsyn <ptup
who else
> can?
>
> Anton V. could you help?
>
> вт, 20 февр. 2018 г. в 19:11, Pavel Tupitsyn <ptupit...@apache.org>:
>
> > Ilya, thanks for the fix, looks good to me.
> > Please make sure TC passes and merge.
> >
> > On Tue, Feb 20, 2018 at 6:08 PM, D
guration cfg) in
>>> C:\Projects\ignite\modules\platforms\dotnet\Apache.Ignite.Core.Tests\
>>> IgniteConfigurationTest.cs:line 551
>>>at Apache.Ignite.Core.Tests.IgniteConfigurationTest.
>>> TestDefaultConfigurationProperties() in C:\Projects\ignite\modules\
>>> platforms\dotn
inting this out.
>
> Sincerely,
> Dmitry Pavlov
>
> вт, 20 февр. 2018 г. в 11:48, Pavel Tupitsyn <ptupit...@apache.org>:
>
> > Alexey, Ilya,
> >
> > Recent merge of IGNITE-7594 has broken some tests in master,
> > AND in ignite-2.4 (which concerns me
Alexey, Ilya,
Recent merge of IGNITE-7594 has broken some tests in master,
AND in ignite-2.4 (which concerns me) [1] [2].
* Have you run the tests before merging your changes?
* Can you please fix this?
In particular, you'll have to update
the DataStorageConfiguration.DefaultWalMode on .NET
Hi,
As far as I know, Sergey Kozlov already has some
Python thin client implementation,
not sure how much functionality is in there, but it may be a good start.
Sergey, can you share something with us?
Thanks,
Pavel
On Tue, Feb 20, 2018 at 1:34 AM, Alexey Kukushkin
Igniters,
Currently we have a TeamCity trigger only on Run All aggregating project:
https://ci.ignite.apache.org/admin/editTriggers.html?id=buildType:IgniteTests24Java8_RunAll
Each change triggers it's own full run. If new changes are added while some
builds are queued,
these changes are not
Since there are no objections I have removed unused interface members.
Thank you for all the replies.
On Thu, Feb 15, 2018 at 12:51 AM, Pavel Tupitsyn <ptupit...@apache.org>
wrote:
> Igniters, Alexey, Igor,
>
> I'd like to discuss recently added ISslContextFactory int
Igniters, Alexey, Igor,
I'd like to discuss recently added ISslContextFactory interface.
https://github.com/apache/ignite/commit/e58aae48b67c74307703d2ae44fe8e3cd4b9649a
"Factory" implies a "CreateInstace" or a similar method, see
CacheConfigurationCacheStoreFactory
or ExpiryPolicyFactory as an
Pavel Tupitsyn created IGNITE-7665:
--
Summary: .NET: Target .NET Standard 2.0
Key: IGNITE-7665
URL: https://issues.apache.org/jira/browse/IGNITE-7665
Project: Ignite
Issue Type: Improvement
Dmitry, thanks a lot, works as expected now!
Pavel
On Thu, Feb 8, 2018 at 5:47 PM, Dmitry Pavlov <dpavlov@gmail.com> wrote:
> Could you please check now?
>
> чт, 8 февр. 2018 г. в 16:37, Pavel Tupitsyn <ptupit...@apache.org>:
>
> > Hi Dmitry,
> >
Sincerely,
> Dmitriy Pavlov
>
> чт, 8 февр. 2018 г. в 16:03, Pavel Tupitsyn <ptupitsyn.apa...@gmail.com>:
>
> > Igniters,
> >
> > My teamcity (ci.ignite.apache.org) account "ptupitsin" seems to be
> removed
> > or disabled.
> > Does anyone know what's going on?
> >
> > Thanks,
> > Pavel
> >
>
Igniters,
My teamcity (ci.ignite.apache.org) account "ptupitsin" seems to be removed
or disabled.
Does anyone know what's going on?
Thanks,
Pavel
Pavel Tupitsyn created IGNITE-7636:
--
Summary: .NET: SQL Client
Key: IGNITE-7636
URL: https://issues.apache.org/jira/browse/IGNITE-7636
Project: Ignite
Issue Type: Improvement
Hi John,
BinarySchema is an optimization to make serialized objects more compact.
Schema is basically int[] containing field ids. Schemas are stored by id in
the cluster.
Serialized objects themselves contain only a set of field offsets
(basically int[] or short[] or byte[]).
So to get a value
.org/jira/issues/?jql=project%
> 3Dzookeeper%20AND%20status%3D"Patch%20Available"%20AND%
> 20updated%20<%20-30d
> >
> > 2018-02-05 15:08 GMT+03:00 Pavel Tupitsyn <ptupit...@apache.org>:
> >> Fixed links:
> >>
> >> https://issues.apache
communities? For example, to Cassandra.
>
> Sincerely,
> Dmitriy Pavlov
>
>
> пн, 5 февр. 2018 г. в 14:51, Pavel Tupitsyn <ptupit...@apache.org>:
>
> > Bumping the thread.
> >
> > Denis Magda, as a PMC chair, can you please look into this?
> >
> >
Bumping the thread.
Denis Magda, as a PMC chair, can you please look into this?
On Tue, Jan 30, 2018 at 5:26 PM, Pavel Tupitsyn <ptupit...@apache.org>
wrote:
> Igniters,
>
> We have *almost 60* of PATCH AVAILABLE tickets that are inactive for more
> than a month:
> http
4 threads?
> This may speed up detecting next alive node under Windows if several
> addresses become unavailable at once.
>
> On Fri, Feb 2, 2018 at 2:09 PM, Pavel Tupitsyn <ptupit...@apache.org>
> wrote:
>
> > Dmitriy, yes, that's what I'm implementing as part of IGNIT
wrote:
> Pavel,
>
> Do I correctly understand, that if I find a typo in docs, I should commit
> fix to master and cherry-pick to all relevant branches?
>
> On Fri, Feb 2, 2018 at 2:28 PM, Pavel Tupitsyn <ptupit...@apache.org>
> wrote:
>
> > I did some resear
r, on the downside, they do not integrate with Git well,
> and
> > ASF wants all its projects to keep the documentation in Apache Git.
> >
> > Does anyone have suggestions?
> >
> > D.
> >
> > On Thu, Feb 1, 2018 at 5:57 AM, Pavel Tupitsyn <ptu
exception
On Fri, Feb 2, 2018 at 12:44 AM, Dmitriy Setrakyan <dsetrak...@apache.org>
wrote:
> On Thu, Feb 1, 2018 at 5:55 AM, Pavel Tupitsyn <ptupit...@apache.org>
> wrote:
>
> > Ok, let's add simple reconnect logic and see what will come of it.
> >
>
>
Pavel Tupitsyn created IGNITE-7609:
--
Summary: .NET: FieldsQueryCursor should expose data types too
Key: IGNITE-7609
URL: https://issues.apache.org/jira/browse/IGNITE-7609
Project: Ignite
Good news, Denis.
By the way, readme.io uses some kind of markdown dialect, and they have
"export" feature,
so it should be possible to move to some markdown-based system like Jekyll
without too much hassle.
On Thu, Feb 1, 2018 at 2:18 AM, Denis Magda wrote:
> Created a
r clients
> resilient to failures and make it way more powerful.
>
> I strongly vote to add this behavior.
>
> D.
>
>
> On Wed, Jan 31, 2018 at 3:15 AM, Pavel Tupitsyn <ptupit...@apache.org>
> wrote:
>
> > Alexey, retrieving addresses from topology make
ent connection config. Thin client
> will use ONLY this addresses (hardcoded list).
> 2) Same as #1, but in addition to specified list of addresses thin client
> collect list of "connectable" nodes from topology (extendable list).
>
> What do you think?
>
>
> On Wed,
Igniters,
I'm working on client-side failover logic for .NET Thin Client.
This will probably apply to ODBC and JDBC thin clients as well in future.
Currently all thin clients connect to a single specified Ignite node.
The idea is to have multiple known nodes (host:port pairs) and reconnect
to
Igniters,
We have *almost 60* of PATCH AVAILABLE tickets that are inactive for more
than a month:
https://issues.apache.org/jira/issues/?filter=12333285=project%3Dignite%20AND%20status%3D%22Patch%20Available%22%20AND%20updated%20%3C%20-30d
(JQL: project=ignite AND status="Patch Available" AND
>>>>>>
> >>>>>>>> Denis,
> >>>>>>>>
> >>>>>>>> I'll review https://issues.apache.org/jira/browse/IGNITE-6902
> >>>>>>>>
> >>>>>>>> On Fri, Jan 12, 20
Hi Dmitry,
Thanks for the heads up, I've moved all 2.4 tickets (except site and
documentation related) to 2.5.
Pavel
On Tue, Jan 30, 2018 at 3:36 PM, Dmitry Sherstobitov
wrote:
> Hi!
>
> We are still having issues for ignite-2.4 release in PATCH AVAILABLE or
> OPEN state:
Pavel Tupitsyn created IGNITE-7568:
--
Summary: Product version increment script
Key: IGNITE-7568
URL: https://issues.apache.org/jira/browse/IGNITE-7568
Project: Ignite
Issue Type
Yakov, thanks for trying this out.
Good point about build script, I've filed a ticket:
https://issues.apache.org/jira/browse/IGNITE-7566
As for tests - yes, these two seem to be flaky on TC as well, I'll have a
look.
Pavel
On Tue, Jan 30, 2018 at 8:34 AM, Yakov Zhdanov
Pavel Tupitsyn created IGNITE-7566:
--
Summary: .NET: Build scripts: stop build when one of the steps
fails
Key: IGNITE-7566
URL: https://issues.apache.org/jira/browse/IGNITE-7566
Project: Ignite
801 - 900 of 1759 matches
Mail list logo