With 10 +1's; none of the -1's or 0's the [VOTE] has passed.
Thanks everyone for voting!
Cos
On Tue, Oct 13, 2015 at 03:30PM, Konstantin Boudnik wrote:
> Hi!
>
> As discussed in the "[DISCUSS] PMC Chair rotation" thread last month, I
> propose
> that we adopt a rule allowing for a Apache Igni
+1 [binding]
On Tue, Oct 13, 2015 at 03:30PM, Konstantin Boudnik wrote:
> Hi!
>
> As discussed in the "[DISCUSS] PMC Chair rotation" thread last month, I
> propose
> that we adopt a rule allowing for a Apache Ignite Chair rotation on a yearly
> basis. The proposed policy is this:
> - a positio
GitHub user vkulichenko opened a pull request:
https://github.com/apache/ignite/pull/163
IGNITE-1702 - Fixed error handling for cache updates
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vkulichenko/incubator-ignite ignite-170
I do not see any problems with object detach. This change is simply a
matter of moving some object metadata from header to footer. It is not lost
or reduced and it is still inside object's body.
On Fri, Oct 16, 2015 at 2:11 PM, Denis Magda wrote:
> Vladimir,
>
> Didn't have much time for review,
Ivan Veselovsky created IGNITE-1725:
---
Summary: [Test]
IgniteProjectionStartStopRestartSelfTest.testStopNodesByIdsC fails
Key: IGNITE-1725
URL: https://issues.apache.org/jira/browse/IGNITE-1725
Ivan Veselovsky created IGNITE-1724:
---
Summary: [Test]
IgniteProjectionStartStopRestartSelfTest.testStartOneNode fails
Key: IGNITE-1724
URL: https://issues.apache.org/jira/browse/IGNITE-1724
Project:
Ivan Veselovsky created IGNITE-1723:
---
Summary: [Test] 2 tests of "Scalar Examples" suite permanently
fail due to missing "ignite-schedule" module
Key: IGNITE-1723
URL: https://issues.apache.org/jira/browse/IGNIT
Vasilisa Sidorova created IGNITE-1722:
--
Summary: ompute
Key: IGNITE-1722
URL: https://issues.apache.org/jira/browse/IGNITE-1722
Project: Ignite
Issue Type: Bug
Reporter: Vas
Vasilisa Sidorova created IGNITE-1721:
--
Summary: Check all examples running with all types of marshallers
Key: IGNITE-1721
URL: https://issues.apache.org/jira/browse/IGNITE-1721
Project: Ignite
Ivan Veselovsky created IGNITE-1720:
---
Summary: [Test] GridVersionSelfTest.testVersions fails
Key: IGNITE-1720
URL: https://issues.apache.org/jira/browse/IGNITE-1720
Project: Ignite
Issue Ty
Ivan Veselovsky created IGNITE-1719:
---
Summary: [Test] GridUpdateNotifierSelfTest.testNotifier fails
Key: IGNITE-1719
URL: https://issues.apache.org/jira/browse/IGNITE-1719
Project: Ignite
Vasilisa Sidorova created IGNITE-1718:
--
Summary: ScalaPrimeExample fails with "Not enough data to read the
value" error when it's running with portableMarshaller
Key: IGNITE-1718
URL: https://issues.apache.o
Vasilisa Sidorova created IGNITE-1717:
--
Summary: NPE during running ScalarCreditRiskExample with
portableMarshaller
Key: IGNITE-1717
URL: https://issues.apache.org/jira/browse/IGNITE-1717
Projec
Vladimir,
Didn't have much time for review, will revisit your design proposal a
bit later.
However, have one comment for now. In your algo you're planning to use
some relative offsets.
Do you take into account that a field, that may be of portable type is
well, can be detached from its objec
Pavel Konstantinov created IGNITE-1716:
--
Summary: SQL page: rework Query UI - show Meatada types on top
level
Key: IGNITE-1716
URL: https://issues.apache.org/jira/browse/IGNITE-1716
Project: Igni
Alexey Kuznetsov created IGNITE-1715:
Summary: Add button [Reset] on Cluster, Caches and Metadata
screens
Key: IGNITE-1715
URL: https://issues.apache.org/jira/browse/IGNITE-1715
Project: Ignite
Alexey Kuznetsov created IGNITE-1714:
Summary: Refactor generation of downloaded ZIP file on summary
screen
Key: IGNITE-1714
URL: https://issues.apache.org/jira/browse/IGNITE-1714
Project: Ignite
Pavel Konstantinov created IGNITE-1713:
--
Summary: Error: notebook is null
Key: IGNITE-1713
URL: https://issues.apache.org/jira/browse/IGNITE-1713
Project: Ignite
Issue Type: Sub-task
Alexey Kuznetsov created IGNITE-1712:
Summary: Disable username and password (with proper placeholder)
in load metadata for test drive
Key: IGNITE-1712
URL: https://issues.apache.org/jira/browse/IGNITE-1712
Pavel Konstantinov created IGNITE-1711:
--
Summary: We should save notebook after Query was deleted
Key: IGNITE-1711
URL: https://issues.apache.org/jira/browse/IGNITE-1711
Project: Ignite
Alexey Kuznetsov created IGNITE-1710:
Summary: SQL test drive should update caches with random values
Key: IGNITE-1710
URL: https://issues.apache.org/jira/browse/IGNITE-1710
Project: Ignite
Alexey Kuznetsov created IGNITE-1709:
Summary: We should select cluster\cache when creating new
cache\metadata
Key: IGNITE-1709
URL: https://issues.apache.org/jira/browse/IGNITE-1709
Project: Igni
Vova,
Are we notifying listeners that a message has been sent? I thought that you
were talking about reply notifications.
D.
On Fri, Oct 16, 2015 at 2:13 AM, Vladimir Ozerov
wrote:
> Dima,
>
> If user call IgniteMessaging.send() in the thread T1, then local message
> listeners on this topic wi
Pavel Konstantinov created IGNITE-1708:
--
Summary: We should add synthetic column ROW_IDX in case when query
result contains one column only
Key: IGNITE-1708
URL: https://issues.apache.org/jira/browse/IGNITE-1
Hi, Konstantin,
Tests are grouped in suites by subsystems. You can run particular test
suite -- e.g. "Ignite Hadoop".
To run the tests with particular changes push the "Run..." button near that
test suite and chose "pull//head" in "Build
branch" field on the "Changes" tab.
On Fri, Oct 16, 2015 at
Dima,
If user call IgniteMessaging.send() in the thread T1, then local message
listeners on this topic will be notified in the same thread before
returning from send() method. This our pseudo-code:
IgniteMessaging.send(Object topic, Object msg) {
...
sendToRemoteNodes(topic, msg);
...
Igniters,
We need to implement constant or nearly-constant random field lookup in
serialized portable object to boost our queries.
With current protocol it is O(N).
I created design document with proposed solution:
https://cwiki.apache.org/confluence/display/IGNITE/Portable+object+constant-time+f
Pavel Konstantinov created IGNITE-1707:
--
Summary: Copy security tiken to clipboard dialog must be read only
Key: IGNITE-1707
URL: https://issues.apache.org/jira/browse/IGNITE-1707
Project: Ignite
Pavel Konstantinov created IGNITE-1706:
--
Summary: SQL: header of notebook has broken UI in case of long
notebook name
Key: IGNITE-1706
URL: https://issues.apache.org/jira/browse/IGNITE-1706
Proje
This behavior should definitely be fixed - exception should be thrown on
client node. I will update ticket. William, thanks for pointing this out.
--Yakov
2015-10-15 20:33 GMT+03:00 William Kemper :
> I never filed a ticket, but for what it's worth, I tried using this method
> in a test scenario
On Fri, Oct 16, 2015 at 1:04 AM, Yakov Zhdanov
wrote:
> Agree with Sam here - we also reduce network calls since we don't need to
> notify for each failed tryLock, but only for cases when tx will definitely
> loose.
>
I also like this approach. Deadlock-free transactions is a HUGE feature and
I
Agree with Sam here - we also reduce network calls since we don't need to
notify for each failed tryLock, but only for cases when tx will definitely
loose.
Thanks!
--
Yakov Zhdanov, Director R&D
*GridGain Systems*
www.gridgain.com
2015-10-16 10:22 GMT+03:00 Semyon Boikov :
> >
> > The success ra
Excellent. Thank you Dmitry!
On 16 Oct 2015 01:44, "Dmitriy Setrakyan" wrote:
> Hi Michael,
>
> I have added you to the Ignite contributors and assigned the ticket to you.
> Welcome to the Ignite community!
>
> Now you can assign any ticket to yourself, so feel free to pick any other
> ticket you
On Thu, Oct 15, 2015 at 11:00 PM, Vladimir Ozerov
wrote:
> Sorry, not very clear. "same" means the same thread that sent a message.
> This way if we have a listener and a single thread generating messages
> locally, only one CPU core will be utilizied.
>
Still confused. How can the thread that s
According to the feedback of other fellow committers, they can take weeks
to approve it (!). When did you apply?
You may contact Ross Gardler to find out what's going on.
Raúl.
On 16 Oct 2015 02:13, "Dmitriy Setrakyan" wrote:
> I still have not received any response for my MSDN subscription, so
>
> The success ratio with ordered approach is naturally going to be better.
> However, I think the performance will suffer, because queues are generally
> expensive. Have you tried comparing performance of the queue-based approach
> vs. the try-lock one?
I did not add any new queues and just use
36 matches
Mail list logo
