Igniters,
One of our users is asking me if this is possible to have a proxy on Java
client for a service implemented in .NET (and vica versa). He tried to do
this, but without success. Is it not supported or he is doing something
wrong?
For me it sounds like a useful feature and I don't see any f
Pavel Konstantinov created IGNITE-2685:
--
Summary: Turn off REST on demo node
Key: IGNITE-2685
URL: https://issues.apache.org/jira/browse/IGNITE-2685
Project: Ignite
Issue Type: Sub-task
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/476
---
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 enab
If it’s not supported for data structures right now, we should check for it
and throw an exception, no? Also, do we have this documented?
D.
On Thu, Feb 18, 2016 at 10:58 AM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Folks,
>
> There were several questions about transactional
Yes, the fix has been merged to master.
On Feb 18, 2016 22:06, "Dmitriy Setrakyan" wrote:
> Alexey, can this be verified in master?
>
> On Thu, Feb 18, 2016 at 7:47 AM, Alexey Goncharuk <
> alexey.goncha...@gmail.com> wrote:
>
> > Hi,
> >
> > I have merged the changes fixing IGNITE-2610 and verif
Alexey, can this be verified in master?
On Thu, Feb 18, 2016 at 7:47 AM, Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:
> Hi,
>
> I have merged the changes fixing IGNITE-2610 and verified the test in
> IGNITE-1661. Please verify and close the ticket if all is ok.
>
Folks,
There were several questions about transactional queues on user forum and
it looks like this is not supported right now.
My question is: why do we have atomicity mode in CollectionConfiguration
then? Does setting it to TRANSACTIONAL change anything?
-Val
Hi Sam,
I saw some users reporting the following error
[tcp-disco-msg-worker-#2%null%] o.a.i.s.d.tcp.TcpDiscoverySpi -
TcpDiscoverSpi'smessage worker thread failed abnormally. Stopping the node in
order to prevent cluster wide instability.
java.lang.InterruptedException: null
Hi,
I have merged the changes fixing IGNITE-2610 and verified the test in
IGNITE-1661. Please verify and close the ticket if all is ok.
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/488
---
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 enab
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/497
IGNITE-2679 .NET: Implement Ignition.TryGetIgnite, returning null instead
of exception
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupit
Denis Magda created IGNITE-2684:
---
Summary: DataStreamer doesn't stream BinaryObjects created with
BinaryBuilder
Key: IGNITE-2684
URL: https://issues.apache.org/jira/browse/IGNITE-2684
Project: Ignite
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/496
IGNITE-2600 .NET: Do not serialize object if AtomicReference CAS succeeded.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite i
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/52
---
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 enabl
Igniters,
Currently we don't have binary mode (withKeepBinary) in Data Structures
(Queue, AtomicReference).
Are there any plans for implementing this, or may be a workaround?
Lack of binary mode prevents us from implementing IgniteQueue in .NET (.NET
types in most cases can't be deserialized in J
Dmitry, nothing else in mind, besides the issue with 3 different pieces of
documentation
(main website, API docs, readme.io), but it is the same with Java.
Thanks,
On Thu, Feb 18, 2016 at 4:42 AM, Dmitriy Setrakyan
wrote:
> Pavel, I think that the contributor(s) of the functionality have to add
Hi:
Thanks!
在 16/2/18 06:29, Dmitriy Setrakyan 写道:
I linked IGNITE-2610 and IGNITE-1661 in Jira. Let’s process them together.
On Wed, Feb 17, 2016 at 12:58 PM, Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:
Yes, from the description it looks related to IGNITE-2610. I will check the
te
Yakov, thank you. Sounds good. I'll do this way.
On Thu, Feb 18, 2016 at 1:43 PM, Yakov Zhdanov wrote:
> Konstantin,
>
> Here are my comments.
>
> 1. I would force same swap configuration on all servers. Therefore, I would
> add "checkClient" attribute to annotation which is "true" by default
>
Hi Denis,
Yakov and me looked at changes at ignite-2666 and we do not understand how
ring message worker can be interrupted except case when node is stopped?
Should we care about this case?
On Wed, Feb 17, 2016 at 2:18 PM, Denis Magda wrote:
> Igniters,
>
> Please review the critical minor fixe
Konstantin,
Here are my comments.
1. I would force same swap configuration on all servers. Therefore, I would
add "checkClient" attribute to annotation which is "true" by default
2. I think all users should properly configure swap along the cluster if
they want to handle possible memory overflow.
I would definitely want to include NuGet and ODBC into upcoming release.
Both issues are in review for now. I expect they will be in master in a
week or so.
LINQ is "nice to have" for me for this release. It changes .NET packaging
and moreover must be tested very thoroughly. So it would be cool to
Folks,
The current implementation of IgniteCache.lock(key).lock() has the same
semantics as the transactional locks - cache topology cannot be changed
while there exists an ongoing transaction or an explicit lock is held. The
restriction for transactions is quite fundamental, the lock() issue can
There are some important .NET features on review, like LINQ and NuGet:
https://issues.apache.org/jira/browse/IGNITE-1630
https://issues.apache.org/jira/browse/IGNITE-1626
Vova can clarify which of them are going to be included in 1.6.
Thanks,
On Thu, Feb 18, 2016 at 12:42 PM, Alexey Goncharuk <
Yakov,
Nothing major from my side is planned for 1.6. There is a ticket
IGNITE-2610 that I am currently working on (it is almost finished), but I
believe it does not make any restrictions for the schedule.
Hi all.
Sorry for asking again, but after some experiments I want to discuss
several options for grid swap policy. Some of them have odd side effects.
It's better to explicitly write them down to select the best solution.
1. Strict policy.
- @IgniteSpiConsistencyChecked(optional = false) used in
I think it makes sense to make this feature the one that drives the next
release.
There is a discussion started by Yakov on this list named "Ignite 1.6
release timelines".
https://mail-archives.apache.org/mod_mbox/ignite-dev/201602.mbox/%3CCAGcMBHiS-9SaqURK8pKQ98VKh-Ynoq_y723%2BotLDuNJJAjKgow%
26 matches
Mail list logo
