Igniters,
I want to circulate again an idea of "betas" for particular product
features.
For now we have several pretty cool features which are to be released soon:
ODBC driver and LINQ in .NET. Features like this include potentially
infinite amount of use cases and of course we cannot test all of
Val,
Comparator has two problems from user perspective:
1) User will be obligated to have comparator classes on servers.
BinaryMarshaller was designed to avoid this.
2) Code duplication - user will have to support two implementations - one
for deserialized form, and one for binary form.
As it app
The comparator is optional, so we need to have some kind of default
behavior anyway. But I'm sure that it will not work in many cases, because
user can't even control the order of fields used for comparison.
On Mon, Feb 29, 2016 at 10:06 PM, Dmitriy Setrakyan
wrote:
> Why can’t we simply compare
Why can’t we simply compare the binary arrays?
On Mon, Feb 29, 2016 at 9:18 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Igniters,
>
> We currently have a pretty serious limitation for binary objects: they can
> be used as SQL fields and can't be indexed, because we don't kno
Igniters,
We currently have a pretty serious limitation for binary objects: they can
be used as SQL fields and can't be indexed, because we don't know how to
compare them. And it seems to me that it can be easily fixed by adding an
optional comparator to BinaryConfiguration and BinaryTypeConfigura
GitHub user oddodaoddo opened a pull request:
https://github.com/apache/ignite/pull/527
IGNITE-2693: Fix withKeepBinary() to only return new cache if binary â¦
â¦marshaller is used
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
Thanks Artem! I think this test suite should go a long way towards removing
issues with different configuration property permutations.
Is this suite turned on by default?
D.
On Mon, Feb 29, 2016 at 7:07 AM, Artem Shutak wrote:
> Igniters,
>
> I'm glad to announce that Configuration Variations
GitHub user avinogradovgg opened a pull request:
https://github.com/apache/ignite/pull/526
Ignite 2650
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2650
Alternatively you can review and apply the
Sure, no problem.
I created a ticket:
https://issues.apache.org/jira/browse/IGNITE-2735
and a PR to resolve this problem.
I think this should also fix: IGNITE-1977
but the non-failover test scenario is not good anymore;
Best regards,
Vladisav
On Mon, Feb 29, 2016 at 2:32 PM, Vladimir Ozerov
GitHub user vladisav opened a pull request:
https://github.com/apache/ignite/pull/525
IGNITE-2735: Fixes distributed semaphore local node stopping issue.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vladisav/ignite ignite-2735
Vladisav Jelisavcic created IGNITE-2735:
---
Summary: Interrupt all acquires on local node after ignite.close
Key: IGNITE-2735
URL: https://issues.apache.org/jira/browse/IGNITE-2735
Project: Ignite
GitHub user agura opened a pull request:
https://github.com/apache/ignite/pull/524
ignite-2734 Binary enum type deserialization from offheap
Fix for https://issues.apache.org/jira/browse/IGNITE-2734
You can merge this pull request into a Git repository by running:
$ git pull ht
Andrey Gura created IGNITE-2734:
---
Summary: Preloading fails during entry preloading for binary enum
with OFFHEAP_VALUES cache memory mode
Key: IGNITE-2734
URL: https://issues.apache.org/jira/browse/IGNITE-2734
This is great news! Thanks, Andrey, for your efforts to make this happen!
On Mon, Feb 29, 2016 at 2:41 AM, Andrey Gura wrote:
> Igniters,
>
> JFI,
>
> Apache Ignite based cluster manager for Vert.x is part of Vert.x official
> stack now.
>
> Source code was migrated to https://github.com/vert-x3
Igniters,
I'm glad to announce that Configuration Variations test framework has been
merged to master and is ready to use.
The framework provides an opportunity to write a test-case once and to run
it in many Ignite and Cache configuration variations, for different Ignite
topologies (with and wit
Hi,
I tested your code in multi-node scenario, and semaphore is released fine
when node owning a permit has been closed. In your code sample there is
only one node, and in this case semaphore is not released. I think that
"acquire" method should throw an exception in this case (say,
InterruptedExc
Artem Shutak created IGNITE-2733:
Summary: Ignite should use actual AffinityTopologyVersion for
LOCAL cache
Key: IGNITE-2733
URL: https://issues.apache.org/jira/browse/IGNITE-2733
Project: Ignite
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/523
IGNITE-2702 .NET: Support compact footers in binary format
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite ignite-2702
Alter
Pavel Konstantinov created IGNITE-2732:
--
Summary: Store factory mismatch in generated project
Key: IGNITE-2732
URL: https://issues.apache.org/jira/browse/IGNITE-2732
Project: Ignite
Issu
Igniters,
JFI,
Apache Ignite based cluster manager for Vert.x is part of Vert.x official
stack now.
Source code was migrated to https://github.com/vert-x3/vertx-ignite
repository under vert-x3 organization.
If you have any questions or suggestions welcome to Ignite or Vert.x
mailing lists.
--
Denis Magda created IGNITE-2731:
---
Summary: Cache metrics documentation on readme.io
Key: IGNITE-2731
URL: https://issues.apache.org/jira/browse/IGNITE-2731
Project: Ignite
Issue Type: Bug
Vlad, that's great! I will take a look this week. Reassigning ticket to
myself.
--Yakov
2016-02-26 18:37 GMT+03:00 Vladisav Jelisavcic :
> Hi,
>
> i recently implemented distributed ReentrantLock - IGNITE-642,
> i made a pull request, so hopefully this could be added to the next
> release.
>
> B
Github user ilantukh closed the pull request at:
https://github.com/apache/ignite/pull/506
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is en
23 matches
Mail list logo
