I fixed this issue with not release locks (
https://issues.apache.org/jira/browse/IGNITE-2008), fix will be available
in 1.5 release.
On Thu, Dec 3, 2015 at 9:28 AM, Dmitriy Setrakyan
wrote:
> Thanks Semyon!
>
> On Wed, Dec 2, 2015 at 10:13 PM, Semyon Boikov
> wrote:
>
> > Dmitry, Valentin,
>
GitHub user nva opened a pull request:
https://github.com/apache/ignite/pull/292
IGNITE-2019 Fixed schema import on Mac OSX El Capitan.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nva/ignite ignite-2019
Alternatively you can
I created the ticket for this issue:
https://issues.apache.org/jira/browse/IGNITE-2083
Alexey G., can you please share your thoughts in this ticket?
-Val
On Thu, Dec 3, 2015 at 2:56 PM, Andrey Kornev
wrote:
> Dmitriy,
>
> Alexey's point is just an explanation of the existing implementation and
Valentin Kulichenko created IGNITE-2083:
---
Summary: EntryProcessor is called twice on primary node in
transactional cache
Key: IGNITE-2083
URL: https://issues.apache.org/jira/browse/IGNITE-2083
P
Dmitriy,
Alexey's point is just an explanation of the existing implementation and not
how it is supposed to be. And while nobody really knows what the correct
behavior should be, the one implemented by Ignite is incredibly
over-engineered. As I argued in a different thread, other vendors provi
Sergey Kozlov created IGNITE-2082:
-
Summary: Documentationd for C++/.Net missed in fabric binary
package
Key: IGNITE-2082
URL: https://issues.apache.org/jira/browse/IGNITE-2082
Project: Ignite
Igniters,
The release notes for 1.5-b1 [1] are missing the Deadlock-free
transactions. Should we add them?
[1]
https://github.com/apache/ignite/blob/ignite-1.5.0-b1-rc1/RELEASE_NOTES.txt
D.
Point taken.
However I still don’t get why it should be called twice in PESSIMISTIC
mode. Can someone explain?
D.
On Thu, Dec 3, 2015 at 10:04 AM, Andrey Gura wrote:
> Hi,
>
> Recently Alexey Goncharuk wrote in thread "EntryProcessor execution
> semantics":
>
> For example, in a case of explic
Hi,
Recently Alexey Goncharuk wrote in thread "EntryProcessor execution
semantics":
For example, in a case of explicit optimistic
> READ_COMMITTED transaction it may be called more than once because Ignite
> needs to calculate a return value for the first invoke() and then it should
> be called s
Dmitry,
Counter will not be incremented twice, because the entry is locked and EP
is guaranteed to be called both times for the same old value. So there is
no critical bug here in my view, but I just don't see the reason why we
call it two times instead of one for one operation.
-Val
On Thu, Dec
Romain,
I believe it is a good idea to stick to well-known Maven qualifiers which
already exist.
*RELEASE* is not in this list and I'd prefer to avoid surprises, if this
will be changed later.
Also our release cycle is different from Eclipse and Spring (instead of
milestones
we have betas, but RC
Sergey Kozlov created IGNITE-2081:
-
Summary: Javadoc: org.apache.ignite.yarn.utils has no description
in overview-summary.html
Key: IGNITE-2081
URL: https://issues.apache.org/jira/browse/IGNITE-2081
P
On Thu, Dec 3, 2015 at 3:11 PM, Dmitriy Setrakyan
wrote:
> Where did you click?
Unfortunately it's a manual process:
https://help.github.com/articles/syncing-a-fork/.
*Raúl Kripalani*
PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
Messaging Engineer
http://about.me/r
Fork is just another git repository, so "git merge" will sync it:
https://help.github.com/articles/syncing-a-fork/
Personally, I never use or sync master branch in my fork (I only work in
feature branches and merge to them from upstream).
Thanks,
On Thu, Dec 3, 2015 at 6:11 PM, Dmitriy Setrakyan
Hi Igniter,
Just to be a pain ...
I like the Spring (I think derive from Eclipse) version numbering approach.
And it works like a charm with OSGi and maven.
For the sprint they deliver milestone : 1.6.0.M1, 1.6.0.M2...
MX imply no guaranty of stable model / classes.
When they enter into release p
On Thu, Dec 3, 2015 at 3:12 AM, Raul Kripalani wrote:
> On Thu, Dec 3, 2015 at 3:30 AM, Dmitriy Setrakyan
> wrote:
>
> > Specifically, your pretty Readme.md is not showing. Any ideas how to fix?
> >
>
> I had to sync it up manually. I thought that GH had an option to keep forks
> synced as long
Andrey Gura created IGNITE-2080:
---
Summary: JVM crashes on SunOS with SIGBUS (0xa) on frame
[libjvm.so+0xc7c438] Unsafe_SetInt+0x14c
Key: IGNITE-2080
URL: https://issues.apache.org/jira/browse/IGNITE-2080
Hi：
As of today, the InteractiveSQL and Streaming parts have been translated
to complete, the relevant page has been updated to zybuluo.com, the
address is: https://www.zybuluo.com/liyuj/note/230739.
In addition, I have the Markdown of the source file to the GitHub, the
address is: https://g
https://issues.apache.org/jira/browse/IGNITE-2079
On Thu, Dec 3, 2015 at 11:26 AM, Yakov Zhdanov wrote:
> This method was introduced exactly to prevent cluster from hanging in case
> of unexpected problems during message processing. The thing is that the one
> who has added new message has not a
Anton Vinogradov created IGNITE-2079:
Summary: GridCacheIoManager eats exception trail if it falls into
the directed case
Key: IGNITE-2079
URL: https://issues.apache.org/jira/browse/IGNITE-2079
Pr
On Thu, Dec 3, 2015 at 9:20 AM, Romain Gilles
wrote:
> Some times maven-bundle-plugin can have side effect on
> split package but I hope Raul has already checked it.
>
Not sure which side effect you mean. But anyway, the maven-bundle-plugin
has several goals. There is a goal to delegate packagin
Is it possible to remove folder D:\sandbox\ignite\modules\gce\target\apidocs
?
Also there is should no be any target folder in case it's a clean branch.
Please check this point.
On Thu, Dec 3, 2015 at 3:22 PM, Ken Cheng wrote:
> Still run into the same issue. As it's a clean branch.
> but this i
Still run into the same issue. As it's a clean branch.
but this issue only happens in Windows
On Thursday, December 3, 2015, Anton Vinogradov
wrote:
> Ken,
>
> I can't understand, did my tip helped?
>
> On Thu, Dec 3, 2015 at 3:11 PM, Ken Cheng wrote:
>
>> HI Anton,
>>
>> it's wired, as I did no
Ken,
I can't understand, did my tip helped?
On Thu, Dec 3, 2015 at 3:11 PM, Ken Cheng wrote:
> HI Anton,
>
> it's wired, as I did not nothing just try to build the the jar.
>
> Thanks,
> kcheng
>
> On Thu, Dec 3, 2015 at 8:08 PM, Anton Vinogradov >
> wrote:
>
> > Ken,
> >
> > Seems some other
GitHub user agoncharuk opened a pull request:
https://github.com/apache/ignite/pull/291
IGNITE-2050 - Remove duplicates from the configuration.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/agoncharuk/ignite ignite-2050
Altern
HI Anton,
it's wired, as I did not nothing just try to build the the jar.
Thanks,
kcheng
On Thu, Dec 3, 2015 at 8:08 PM, Anton Vinogradov
wrote:
> Ken,
>
> Seems some other application used files at
> D:\sandbox\ignite\modules\gce\target\apidocs.
> Possible it's an Explorer.
>
> On Thu, Dec 3,
Ken,
Seems some other application used files at
D:\sandbox\ignite\modules\gce\target\apidocs.
Possible it's an Explorer.
On Thu, Dec 3, 2015 at 3:04 PM, Ken Cheng wrote:
> Hi All,
>
> Here is my environment details:
>
> OS : Windows 64
> jdk 1.7
>
> here is error message
>
>
> -
Hi All,
Here is my environment details:
OS : Windows 64
jdk 1.7
here is error message
[INFO] ignite-apache-license-gen .. SUCCESS [
3.689 s]
[INFO] ignite-tools ... SUCCESS [
23.021
Ilya Suntsov created IGNITE-2078:
Summary: Need to clean cache after query in CacheQueryExample
Key: IGNITE-2078
URL: https://issues.apache.org/jira/browse/IGNITE-2078
Project: Ignite
Issue T
Raul, I did review as well. I added my comments to the ticket and committed
some changes to ignite-1270.
Given that this feature is desperately desired, can we merge it to 1.5? To
do that you can squash all the differences between 1270 and master and pick
that commit to ignite-1.5. If someone know
On Thu, Dec 3, 2015 at 3:30 AM, Dmitriy Setrakyan
wrote:
> Specifically, your pretty Readme.md is not showing. Any ideas how to fix?
>
I had to sync it up manually. I thought that GH had an option to keep forks
synced as long as they hadn't diverged. I was mistaken.
If the community feels keepin
GitHub user ashutakGG opened a pull request:
https://github.com/apache/ignite/pull/290
IGNITE-1864 Custom TX manager configuration
https://issues.apache.org/jira/browse/IGNITE-1864
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/a
Igniters,
Ingite tests at Teamcity migrated from 'Ignite' project to "Ignite Tests"
project.
Old project (Ignite) paused now and will be removed next week.
Please use "Ignite Tests" project only.
Pavel Tupitsyn created IGNITE-2077:
---
Summary: .Net: Create builds on TeamCity
Key: IGNITE-2077
URL: https://issues.apache.org/jira/browse/IGNITE-2077
Project: Ignite
Issue Type: Task
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/289
Ignite 1692 Test Suite and extended logging for DataStreamProcessorSelfTest.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ilantukh/ignite ig
Github user ilantukh closed the pull request at:
https://github.com/apache/ignite/pull/286
---
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
Alexey,
As agreed in the chatroom, let’s fix the example by moving the data source
factory from anonymous class to a static class, which will allow the error
message on the server side specify the full class name of the missing class.
Seems like this is the best we can do for this problem.
D.
O
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/288
IGNITE-2074 Platforms C++ files have 1.5.0-EA version
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite ignite-2074
Alternativ
Pavel Konstantinov created IGNITE-2076:
--
Summary: Failed to send time request to remote node
Key: IGNITE-2076
URL: https://issues.apache.org/jira/browse/IGNITE-2076
Project: Ignite
Issue
I think this is definitely a bug. Imagine that EP is used to maintain a
counter, and the counter is incremented with every update. In this case the
counter will be updated 2 times instead of 1.
Alexey G., would be nice to hear your thoughts here.
D.
On Wed, Dec 2, 2015 at 9:08 PM, Valentin Kulic
Hi Igniters,
I did the review. I term of impact the Raul commits change the manifest of
the overall produced jar files to introduce OSGi specific headers. This
will not impact original ignite usage as OSGi headers does are only for
OSGi environments. Some times maven-bundle-plugin can have side eff
Pavel Konstantinov created IGNITE-2075:
--
Summary: We must deny access to admin page to unauthorized users
Key: IGNITE-2075
URL: https://issues.apache.org/jira/browse/IGNITE-2075
Project: Ignite
Sergey Kozlov created IGNITE-2074:
-
Summary: Platforms C++ files hasve 1.5.0-EA version
Key: IGNITE-2074
URL: https://issues.apache.org/jira/browse/IGNITE-2074
Project: Ignite
Issue Type: Bug
Raul,
Thanks a lot, gitter is great!
It seems that the Ignite fork in GIT is not automatically updated.
Specifically, your pretty Readme.md is not showing. Any ideas how to fix?
I see new MD here: https://github.com/apache/ignite
--Yakov
Pavel Konstantinov created IGNITE-2073:
--
Summary: GridLocalAtomicCache cannot be cast to GridDhtCacheAdapter
Key: IGNITE-2073
URL: https://issues.apache.org/jira/browse/IGNITE-2073
Project: Ignite
This method was introduced exactly to prevent cluster from hanging in case
of unexpected problems during message processing. The thing is that the one
who has added new message has not added corresponding block to mentioned
method.
Agree with the point about original error message should not be su
Pavel Konstantinov created IGNITE-2072:
--
Summary: Chart settings doesn't contain fields with UUID type
Key: IGNITE-2072
URL: https://issues.apache.org/jira/browse/IGNITE-2072
Project: Ignite
On Wed, Dec 2, 2015 at 9:31 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Igniters,
>
> Can someone please explain the purpose
> of GridCacheIoManager.processFailedMessage() method? I've already seen
> several reports on user@ about "Unsupported direct type" exception thrown
>
48 matches
Mail list logo
