Config gaps are also captured by tests in same folder.
As for queues, I'm no expert, but I think all Ignite data structures use
cache underneath,
and any cache can be configured to enable persistence.
On Tue, Dec 5, 2017 at 2:53 AM, Raymond Wilson
wrote:
> I was reading into this a little more
1) Thin Client Connector (server part) and .NET Thin Client are in master
and ready for release. See `thin client` component in JIRA.
2) .NET Core cross-platform support (Ignite.NET on Linux and macOS) also
are in master and ready:
https://issues.apache.org/jira/browse/IGNITE-2662
https://issues.a
Hi Anton,
Looks like none of the new metrics are added on .NET side.
Please make sure it happens, either as part of existing tickets or
separately.
Thanks,
Pavel
On Thu, Nov 16, 2017 at 4:32 AM, Denis Magda wrote:
> Ok, closed the previously existed as a duplicate and add another usability
> i
Hi Pavel,
I am trying to use the OP_CACHE_CREATE_WITH_NAME operation, but can't get
it to work. Digging deeper into the source code, it seems like I have to
provide a flag, string length, and position, in addition to the type code
and the actual string. Is that correct?
Here is the request I am
I was reading into this a little more to see if queues are persistent.
It appears they are not? https://issues.apache.org/jira/browse/IGNITE-2389
Thanks,
Raymond.
*From:* Alexey Popov [mailto:tank2.a...@gmail.com]
*Sent:* Saturday, December 2, 2017 4:49 AM
*To:* u...@ignite.apache.org
*Cc
First part of Spark dataframe integration is likely to get into 2.4:
https://issues.apache.org/jira/browse/IGNITE-3084
-Val
On Mon, Dec 4, 2017 at 1:11 PM, Denis Magda wrote:
> Igniters,
>
> Basing on the amount of improvements, fixes and features stacked in the
> master branch I think it’s a r
Denis,
Nikolay was doing final changes and TC stabilization. I'm planning to do
final review this week, so hopefully we will merge the code soon.
-Val
On Mon, Dec 4, 2017 at 1:31 PM, Denis Magda wrote:
> Nikolay, Val,
>
> Since we agreed to release the feature without the strategy support, can
Please join me for a webinar on Wednesday, 6 December 2017 @ 11:00 am PT.
https://ignite.apache.org/events.html#meeting-challenges-fast-data-in-healthcare-in-memory-technologies
Thank you.
GitHub user alex-plekhanov opened a pull request:
https://github.com/apache/ignite/pull/3139
IGNITE-6871 Group name added to group metrics MXBean
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/alex-plekhanov/ignite ignite-6871-f
Pavel,
I took a look at the test; thanks!
I don’t think this captures the configuration gaps between spring config
and C# config, correct?
Thanks,
Raymond.
*From:* Pavel Tupitsyn [mailto:ptupit...@apache.org]
*Sent:* Tuesday, December 5, 2017 5:46 AM
*To:* u...@ignite.apache.org
*Cc:*
Nikolay, Val,
Since we agreed to release the feature without the strategy support, can the
current integration meet the world in 2.4 release? Please chime in this
conversation:
http://apache-ignite-developers.2346864.n4.nabble.com/Time-and-scope-for-Apache-Ignite-2-4-td24987.html
—
Denis
> On
Igniters,
Basing on the amount of improvements, fixes and features stacked in the master
branch I think it’s a right time to negotiate the scope and time of the next
Apache Ignite 2.4 release. I’m ready to step in as a release manager if none of
the committers wants to try on this role.
Here i
Pavel,
Thanks! While we're at it, are there any plans to add cluster-related
operations? For example, I think it'd be nice to allow the thin clients to
obtain a current topology snapshot. This would make it possible the clients to
send requests directly to the affinity host for colocated comput
GitHub user tonyschak opened a pull request:
https://github.com/apache/ignite/pull/3138
Ignite 7090
ignite-7090 added onNodeRelease to the stop method to ensure a node
stopping will release permits for future use.
You can merge this pull request into a Git repository by running:
Ken,
For access control, you can either implement the GridSecurityProcessor
interface as part of a custom plugin [1], or choose to use a 3rd party
implementation [2].
[1] https://apacheignite.readme.io/docs/plugins
[2] https://docs.gridgain.com/docs/security-and-audit
On Sat, Dec 2, 2017 at 5:4
Sergey Kozlov created IGNITE-7110:
-
Summary: Javadoc package descriptions missed for ML
Key: IGNITE-7110
URL: https://issues.apache.org/jira/browse/IGNITE-7110
Project: Ignite
Issue Type: Bug
Github user tonyschak closed the pull request at:
https://github.com/apache/ignite/pull/2939
---
GitHub user anton-vinogradov opened a pull request:
https://github.com/apache/ignite/pull/3137
IGNITE-6411 WIP
Signed-off-by: Anton Vinogradov
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7003
Al
GitHub user tonyschak reopened a pull request:
https://github.com/apache/ignite/pull/2939
IGNITE-6767 reset of the topVer on loading of the entry
I added though the loadedValue method should reset the topVer since it
could be inval
You can merge this pull request into a Git reposit
Github user tonyschak closed the pull request at:
https://github.com/apache/ignite/pull/2939
---
You did not set CacheConfiguration#indexedTypes property. See documentation
for more details:
https://apacheignite.readme.io/docs/cache-queries#query-configuration-by-annotations
-Val
On Sat, Dec 2, 2017 at 12:24 AM, kcheng.mvp wrote:
> by the way, here is my maven dependency.
>
> the unit test
Prachi,
Added "Cache flags" note to the doc.
Thanks,
Pavel
On Mon, Dec 4, 2017 at 7:46 PM, Prachi Garg wrote:
> Pavel,
>
> How do you specify the flags (withSkipStore, withExpiryPolicy, etc..) in
> bytes? Do you have a code for each of them?
>
> On Sun, Dec 3, 2017 at 9:23 AM, Pavel Tupitsyn
Pavel Tupitsyn created IGNITE-7109:
--
Summary: .NET: Thin client: Async cache operations
Key: IGNITE-7109
URL: https://issues.apache.org/jira/browse/IGNITE-7109
Project: Ignite
Issue Type: Im
Pavel,
How do you specify the flags (withSkipStore, withExpiryPolicy, etc..) in
bytes? Do you have a code for each of them?
On Sun, Dec 3, 2017 at 9:23 AM, Pavel Tupitsyn wrote:
> Hi Andrey,
>
> Compute and other APIs are certainly planned, cache is just a start.
> We intentionally limit the sc
Raymond,
There is no document. We keep track of missing stuff with tests.
I've just added that for root level APIs, see MissingMembers:
https://github.com/apache/ignite/blob/master/modules/platforms/dotnet/Apache.Ignite.Core.Tests/ApiParity/IgniteParityTest.cs#L39
Pavel
On Sun, Dec 3, 2017 at 11
GitHub user ezhuravl opened a pull request:
https://github.com/apache/ignite/pull/3136
IGNITE-7088 Fix implementation of DIRECT comparator for ordering caches
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
GitHub user nizhikov opened a pull request:
https://github.com/apache/ignite/pull/3135
IGNITE-6903: Index size metric implemented.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nizhikov/ignite IGNITE-6903
Alternatively you can
vveider
> On 4 Dec 2017, at 18:42, Yakov Zhdanov wrote:
>
> Hello!
>
> What is your JIRA username?
>
> --Yakov
>
> 2017-12-04 18:25 GMT+03:00 Иванов Петр :
>
>> Hi, Igniters!
>>
>>
>> I'd like to contribute into Apache Ignite and can take a task of creating
>> RPM and DEB packages in order
Hello!
What is your JIRA username?
--Yakov
2017-12-04 18:25 GMT+03:00 Иванов Петр :
> Hi, Igniters!
>
>
> I'd like to contribute into Apache Ignite and can take a task of creating
> RPM and DEB packages in order to try to include correctly packed future
> releases into main linux distributions
Hi, Igniters!
I'd like to contribute into Apache Ignite and can take a task of creating
RPM and DEB packages in order to try to include correctly packed future
releases into main linux distributions (Fedora / CentOS / RHEL / Ubuntu /
Debian, etc.)
Created corresponding tasks:
- https://issues.a
Peter Ivanov created IGNITE-7108:
Summary: Apache Ignite DEB packages
Key: IGNITE-7108
URL: https://issues.apache.org/jira/browse/IGNITE-7108
Project: Ignite
Issue Type: Improvement
Peter Ivanov created IGNITE-7107:
Summary: Apache Ignite RPM packages
Key: IGNITE-7107
URL: https://issues.apache.org/jira/browse/IGNITE-7107
Project: Ignite
Issue Type: Improvement
Alexey Kuznetsov created IGNITE-7106:
Summary: Add option to VisorNodeDataCollectorTask to not collect
cache metrics
Key: IGNITE-7106
URL: https://issues.apache.org/jira/browse/IGNITE-7106
Project
GitHub user agura opened a pull request:
https://github.com/apache/ignite/pull/3134
Ignite-602
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/agura/incubator-ignite ignite-602
Alternatively you can review and apply these change
Github user agura closed the pull request at:
https://github.com/apache/ignite/pull/3104
---
Github user agura closed the pull request at:
https://github.com/apache/ignite/pull/3102
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3037
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3096
---
Pavel Tupitsyn created IGNITE-7105:
--
Summary: .NET: IIgnite.ReentrantLock
Key: IGNITE-7105
URL: https://issues.apache.org/jira/browse/IGNITE-7105
Project: Ignite
Issue Type: Improvement
Pavel Tupitsyn created IGNITE-7104:
--
Summary: .NET: IIgnite.AtomicStamped
Key: IGNITE-7104
URL: https://issues.apache.org/jira/browse/IGNITE-7104
Project: Ignite
Issue Type: Improvement
Pavel Tupitsyn created IGNITE-7103:
--
Summary: .NET: IIgnite.Semaphore
Key: IGNITE-7103
URL: https://issues.apache.org/jira/browse/IGNITE-7103
Project: Ignite
Issue Type: Improvement
Pavel Tupitsyn created IGNITE-7102:
--
Summary: .NET: IIgnite.AddCacheConfiguration
Key: IGNITE-7102
URL: https://issues.apache.org/jira/browse/IGNITE-7102
Project: Ignite
Issue Type: Improvem
Pavel Tupitsyn created IGNITE-7101:
--
Summary: .NET: IIgnite.GetVersion
Key: IGNITE-7101
URL: https://issues.apache.org/jira/browse/IGNITE-7101
Project: Ignite
Issue Type: Improvement
Pavel Tupitsyn created IGNITE-7100:
--
Summary: .NET: IIgnite CreateCaches, DestroyCaches
Key: IGNITE-7100
URL: https://issues.apache.org/jira/browse/IGNITE-7100
Project: Ignite
Issue Type: Im
Vasiliy Sisko created IGNITE-7099:
-
Summary: Cache public API should generate exceptions when cluster
is not active.
Key: IGNITE-7099
URL: https://issues.apache.org/jira/browse/IGNITE-7099
Project: Ig
GitHub user apopovgg opened a pull request:
https://github.com/apache/ignite/pull/3133
Ignite 2.1.1.b6
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.1.1.b6
Alternatively you can review and apply
Teun Hoogendoorn created IGNITE-7098:
Summary: DelayQueue as distributed data structure
Key: IGNITE-7098
URL: https://issues.apache.org/jira/browse/IGNITE-7098
Project: Ignite
Issue Type:
Github user NSAmelchev closed the pull request at:
https://github.com/apache/ignite/pull/2015
---
Github user NSAmelchev closed the pull request at:
https://github.com/apache/ignite/pull/1883
---
Github user NSAmelchev closed the pull request at:
https://github.com/apache/ignite/pull/1884
---
Github user NSAmelchev closed the pull request at:
https://github.com/apache/ignite/pull/2518
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3125
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3129
---
53 matches
Mail list logo