[jira] [Created] (IGNITE-4269) Implement query rewriting in JDBC driver for batch statements
Alexander Paschenko created IGNITE-4269: --- Summary: Implement query rewriting in JDBC driver for batch statements Key: IGNITE-4269 URL: https://issues.apache.org/jira/browse/IGNITE-4269 Project: Ignite Issue Type: New Feature Reporter: Alexander Paschenko Assignee: Alexander Paschenko In the course of review of initial DML implementation, it has been agreed that the first attempt to implement batching (via series of individual queries) is rather incorrect (effectively series of individual queries instead of one larger query). So it's been decided not to include batching into initial release and rather implement it the right way shortly in nearest releases. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4268) Allow UPDATEs of the key and its fields in DML statements
Alexander Paschenko created IGNITE-4268:
---
Summary: Allow UPDATEs of the key and its fields in DML statements
Key: IGNITE-4268
URL: https://issues.apache.org/jira/browse/IGNITE-4268
Project: Ignite
Issue Type: New Feature
Reporter: Alexander Paschenko
Assignee: Alexander Paschenko
Initial DML implementation does not allow to UPDATE columns that correspond to
key or its fields - direct modification would probably damage the index as well
as hash map integrity, so UPDATE for such cases would need to do first
{{remove}}, then {{put}}.
In the course of review, it has been agreed that this feature will be
implemented in later releases shortly to deliver initial implementation on time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-4116) .NET: documentation and example for client reconnect feature
[ https://issues.apache.org/jira/browse/IGNITE-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn reassigned IGNITE-4116: -- Assignee: Pavel Tupitsyn (was: Prachi Garg) > .NET: documentation and example for client reconnect feature > > > Key: IGNITE-4116 > URL: https://issues.apache.org/jira/browse/IGNITE-4116 > Project: Ignite > Issue Type: Sub-task >Affects Versions: 1.7 >Reporter: Denis Magda >Assignee: Pavel Tupitsyn > Fix For: 1.8 > > Attachments: Screen Shot 2016-10-31 at 8.53.01 AM.png > > > Presently the documentation and example about the client reconnect feature is > missing on .NET side. Let's fill this gap. > - Documentation can be taken from Java side > (https://apacheignite.readme.io/docs/clients-vs-servers#client-reconnect) > - The example that can be (should be) added to the distribution is the > following > https://github.com/gridgain/apache-ignite/blob/ignite-net-advanced-examples/modules/platforms/dotnet/examples/Apache.Ignite.Examples/Advanced/ClientReconnectExample.cs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4265) Need to revisit compute grid checkpoints
[ https://issues.apache.org/jira/browse/IGNITE-4265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yakov Zhdanov updated IGNITE-4265: -- Description: I. Shared fs checkpoint SPI seems to be totally wrong Problems spotted in code # Blocking IO API # No locks or synchronization Please see GridSharedFsCheckpointSpiMultiThreadedSelfTest I would think of removing shared FS checkpoints and move to distributed cache. II. Having the above I would do: # Revisit checkpoints SPI/manager. I would probably replace it with checkoints processor using distributed cache(s) # distributed caches can be configured in configuration or on the fly using templates. This needs to be elaborated further. # org.apache.ignite.internal.managers.checkpoint.GridCheckpointManager#onSessionEnd seems to be handy for clean up and can be implemented with cache queries - session ID should be added to each entry was: I. Shared fs checkpoint SPI seems to be totally wrong Problems spotted in code # Blocking IO API # No locks or synchronization Please see GridSharedFsCheckpointSpiMultiThreadedSelfTest I would think of removing shared FS checkpoints and move to distributed cache. II. Having the above I would do: # Revisit checkpoints SPI/manager. I would probably replace it with checkoints processor using distributed cache(s) # distributed caches can be configured in configuration or on the fly using templates. This needs to be elaborated further. # org.apache.ignite.internal.managers.checkpoint.GridCheckpointManager#onSessionEnd seems to be handy for clean up and can be implemented with cache queries - session ID should be added to each entry # > Need to revisit compute grid checkpoints > > > Key: IGNITE-4265 > URL: https://issues.apache.org/jira/browse/IGNITE-4265 > Project: Ignite > Issue Type: Task >Reporter: Yakov Zhdanov >Priority: Minor > > I. Shared fs checkpoint SPI seems to be totally wrong > Problems spotted in code > # Blocking IO API > # No locks or synchronization > Please see GridSharedFsCheckpointSpiMultiThreadedSelfTest > I would think of removing shared FS checkpoints and move to distributed cache. > II. Having the above I would do: > # Revisit checkpoints SPI/manager. I would probably replace it with > checkoints processor using distributed cache(s) > # distributed caches can be configured in configuration or on the fly using > templates. This needs to be elaborated further. > # > org.apache.ignite.internal.managers.checkpoint.GridCheckpointManager#onSessionEnd > seems to be handy for clean up and can be implemented with cache queries - > session ID should be added to each entry -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4267) Need to revisit JTA functionality
Yakov Zhdanov created IGNITE-4267:
-
Summary: Need to revisit JTA functionality
Key: IGNITE-4267
URL: https://issues.apache.org/jira/browse/IGNITE-4267
Project: Ignite
Issue Type: Task
Reporter: Yakov Zhdanov
I have found this in older emails:
I found 2 problem:
1) We threw XAException without error code in GridCacheXAResource
2) I debugged 2 different transaction managers - jotm and narayana (JBoss).
Both doesn't trigger rollback logic in our GridCacheXAResource if exception was
thrown during JTA commit (and I didn't found such logic in its sources, so I
suppose we should trigger it ourself). Added GridCacheJtaRollbackSelfTest which
emulate this situation.
===
{noformat}
/**
* Tests for JTA rollback scenarios.
*/
public class GridCacheJtaRollbackSelfTest extends GridCacheAbstractSelfTest {
/** Java Open Transaction Manager facade. */
private static Jotm jotm;
@Override protected int gridCount() {
return 1;
}
/** {@inheritDoc} */
@Override protected void beforeTest() throws Exception {
super.beforeTest();
jotm = new Jotm(true, false);
}
/** {@inheritDoc} */
@Override protected void afterTest() throws Exception {
super.afterTest();
jotm.stop();
}
/** {@inheritDoc} */
@Override protected GridCacheMode cacheMode() {
return PARTITIONED;
}
/** {@inheritDoc} */
@Override protected GridCacheConfiguration cacheConfiguration(String
gridName) throws Exception {
GridCacheConfiguration cfg = super.cacheConfiguration(gridName);
cfg.setTransactionManagerLookupClassName(TestTmLookup.class.getName());
cfg.setStore(new GridCacheFailureStore(10));
return cfg;
}
public void testJta() throws Exception {
for (int i = 0; i < 10; i++) {
UserTransaction jtaTx = jotm.getUserTransaction();
try {
jtaTx.begin();
info("Transaction started.");
cache().put("key1", 1);
cache().put("key2", 2);
cache().get("key1");
cache().remove("key2");
info("Start commit...");
jtaTx.commit();
info("Transaction commited.");
}
catch (Exception e) {
e.printStackTrace();
info("Got expected exception, status=" + jtaTx.getStatus());
}
finally {
if (jtaTx.getStatus() == Status.STATUS_ACTIVE) {
System.out.println("Start rollback...");
jtaTx.rollback();
}
}
}
}
/**
*
*/
private static final class GridCacheFailureStore extends
GridCacheStoreAdapter {
/** */
private final AtomicInteger putCnt = new AtomicInteger();
/** */
private final int failStep;
private GridCacheFailureStore(int failStep) {
this.failStep = failStep;
}
/** {@inheritDoc} */
@Override public Object load(@Nullable GridCacheTx tx, Object key) {
return null;
}
/** {@inheritDoc} */
@Override public void put(@Nullable GridCacheTx tx, Object key,
@Nullable Object val) throws GridException {
int cnt = putCnt.incrementAndGet();
if (cnt == failStep)
throw new GridException("Test exception (need to rollback JTA
transactions).");
}
/** {@inheritDoc} */
@Override public void remove(@Nullable GridCacheTx tx, Object key) {
}
}
/**
*
*/
@SuppressWarnings("PublicInnerClass")
public static class TestTmLookup implements GridCacheTmLookup {
/** {@inheritDoc} */
@Override public TransactionManager getTm() throws GridException {
return jotm.getTransactionManager();
}
}
}
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-4266) GridSessionCancelSiblings* tests can be refactored with extraction of single parent
Yakov Zhdanov created IGNITE-4266: - Summary: GridSessionCancelSiblings* tests can be refactored with extraction of single parent Key: IGNITE-4266 URL: https://issues.apache.org/jira/browse/IGNITE-4266 Project: Ignite Issue Type: Task Reporter: Yakov Zhdanov Priority: Minor GridSessionCancelSiblingsFromFutureSelfTest GridSessionCancelSiblingsFromJobSelfTest GridSessionCancelSiblingsFromTaskSelfTest These three classes seems to be almost identical but test different parts of functionality. I would refactor this to merge everything to one class, but different test methods. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4265) Need to revisit compute grid checkpoints
Yakov Zhdanov created IGNITE-4265: - Summary: Need to revisit compute grid checkpoints Key: IGNITE-4265 URL: https://issues.apache.org/jira/browse/IGNITE-4265 Project: Ignite Issue Type: Task Reporter: Yakov Zhdanov Priority: Minor I. Shared fs checkpoint SPI seems to be totally wrong Problems spotted in code # Blocking IO API # No locks or synchronization Please see GridSharedFsCheckpointSpiMultiThreadedSelfTest I would think of removing shared FS checkpoints and move to distributed cache. II. Having the above I would do: # Revisit checkpoints SPI/manager. I would probably replace it with checkoints processor using distributed cache(s) # distributed caches can be configured in configuration or on the fly using templates. This needs to be elaborated further. # org.apache.ignite.internal.managers.checkpoint.GridCheckpointManager#onSessionEnd seems to be handy for clean up and can be implemented with cache queries - session ID should be added to each entry # -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4243) Add examples of using Redis
[
https://issues.apache.org/jira/browse/IGNITE-4243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Shtykh updated IGNITE-4243:
-
Fix Version/s: 1.8
> Add examples of using Redis
> ---
>
> Key: IGNITE-4243
> URL: https://issues.apache.org/jira/browse/IGNITE-4243
> Project: Ignite
> Issue Type: Sub-task
>Affects Versions: 1.8
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
> Labels: redis
> Fix For: 1.8
>
>
> Add examples of using Redis with Python/PHP/etc. clients to {{examples/}}
> similarly to memcached and rest.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-4264) Offheap cache entries statistics is broken in master
[ https://issues.apache.org/jira/browse/IGNITE-4264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15688716#comment-15688716 ] ASF GitHub Bot commented on IGNITE-4264: GitHub user wmz7year opened a pull request: https://github.com/apache/ignite/pull/1263 IGNITE-4264: fix cache metrics error between server and client. You can merge this pull request into a Git repository by running: $ git pull https://github.com/wmz7year/ignite ignite-4264 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/1263.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1263 commit af739867d50218dd47990ce17e81cce06615db85 Author: jiangwei Date: 2016-11-23T03:01:37Z fix cache metrics error between server and client. > Offheap cache entries statistics is broken in master > > > Key: IGNITE-4264 > URL: https://issues.apache.org/jira/browse/IGNITE-4264 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Andrew Mashenkov >Assignee: wmz7year > Fix For: 1.8 > > Attachments: Test.java > > > Reproducer is attached. Test is fine on 1.7 release branch, but fails in > master > cache.metrics().getOffHeapPrimaryEntriesCount() returns wrong number. Also it > seems the number grows with increasing number of clients. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4116) .NET: documentation and example for client reconnect feature
[ https://issues.apache.org/jira/browse/IGNITE-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15688683#comment-15688683 ] Prachi Garg commented on IGNITE-4116: - Fixed the Java documentation. Please review [1] For the .NET documentation [2], the following is not clear to me- "There are Ignite events for client reconnect (these events are local, i.e. they are fired only on client node): `EventType.ClientNodeDisconnected` and `EventType.ClientNodeReconnected`. Also there are `ClientDisconnected` and `ClientReconnected` events in `IIgnite`." Are there 4 types of events for client reconnection? [1] http://apacheignite.gridgain.org/v1.7/docs/clients-vs-servers#client-reconnection [2] https://apacheignite-net.readme.io/v1.7/docs/clients-and-servers#client-reconnection > .NET: documentation and example for client reconnect feature > > > Key: IGNITE-4116 > URL: https://issues.apache.org/jira/browse/IGNITE-4116 > Project: Ignite > Issue Type: Sub-task >Affects Versions: 1.7 >Reporter: Denis Magda >Assignee: Prachi Garg > Fix For: 1.8 > > Attachments: Screen Shot 2016-10-31 at 8.53.01 AM.png > > > Presently the documentation and example about the client reconnect feature is > missing on .NET side. Let's fill this gap. > - Documentation can be taken from Java side > (https://apacheignite.readme.io/docs/clients-vs-servers#client-reconnect) > - The example that can be (should be) added to the distribution is the > following > https://github.com/gridgain/apache-ignite/blob/ignite-net-advanced-examples/modules/platforms/dotnet/examples/Apache.Ignite.Examples/Advanced/ClientReconnectExample.cs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-4264) Offheap cache entries statistics is broken in master
[ https://issues.apache.org/jira/browse/IGNITE-4264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wmz7year reassigned IGNITE-4264: Assignee: wmz7year > Offheap cache entries statistics is broken in master > > > Key: IGNITE-4264 > URL: https://issues.apache.org/jira/browse/IGNITE-4264 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Andrew Mashenkov >Assignee: wmz7year > Fix For: 1.8 > > Attachments: Test.java > > > Reproducer is attached. Test is fine on 1.7 release branch, but fails in > master > cache.metrics().getOffHeapPrimaryEntriesCount() returns wrong number. Also it > seems the number grows with increasing number of clients. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-3699) CreatedExpiryPolicy doesn't work if entry is loaded from store
[
https://issues.apache.org/jira/browse/IGNITE-3699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-3699:
Priority: Critical (was: Major)
> CreatedExpiryPolicy doesn't work if entry is loaded from store
> --
>
> Key: IGNITE-3699
> URL: https://issues.apache.org/jira/browse/IGNITE-3699
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Amir Akhmedov
>Priority: Critical
> Fix For: 2.0
>
> Attachments: LoadWithExpiryTest.java
>
>
> According to JCache spec, {{ExpiryPolicy.getExpiryForCreation()}} must be
> triggered on {{get()}} operation if the entry is loaded from the store.
> Currently this is not happening.
> Test reproducing the issue is attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-4033) Streamline platform callback interface
[ https://issues.apache.org/jira/browse/IGNITE-4033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15687207#comment-15687207 ] Pavel Tupitsyn commented on IGNITE-4033: Cache, store, compute, queries, streamer - done. > Streamline platform callback interface > -- > > Key: IGNITE-4033 > URL: https://issues.apache.org/jira/browse/IGNITE-4033 > Project: Ignite > Issue Type: Sub-task > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 2.0 > > > Similar to PlatformTarget calls (.NET -> Java), we need a symmetrical > universal Java -> .NET callback interface. > All current specialized callbacks should be refactored to use common callback > methods. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4219) Hive job submsiion failed with exception ”java.io.UTFDataFormatException“
[
https://issues.apache.org/jira/browse/IGNITE-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Mashenkov updated IGNITE-4219:
-
Priority: Minor (was: Major)
> Hive job submsiion failed with exception ”java.io.UTFDataFormatException“
> -
>
> Key: IGNITE-4219
> URL: https://issues.apache.org/jira/browse/IGNITE-4219
> Project: Ignite
> Issue Type: Bug
> Components: hadoop
>Reporter: Andrew Mashenkov
>Priority: Minor
> Fix For: 2.0
>
>
> Long property passing to Hadoop causes an exception:
> {code}
> Caused by: java.io.UTFDataFormatException
>at
> java.io.ObjectOutputStream$BlockDataOutputStream.writeUTF(ObjectOutputStream.java:2144)
>
>at
> java.io.ObjectOutputStream$BlockDataOutputStream.writeUTF(ObjectOutputStream.java:1987)
>
>at java.io.ObjectOutputStream.writeUTF(ObjectOutputStream.java:865)
>at
> org.apache.ignite.internal.util.IgniteUtils.writeUTFStringNullable(IgniteUtils.java:5029)
>
>at
> org.apache.ignite.internal.util.IgniteUtils.writeStringMap(IgniteUtils.java:4989)
>
>at
> org.apache.ignite.internal.processors.hadoop.HadoopDefaultJobInfo.writeExternal(HadoopDefaultJobInfo.java:137)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-4219) Hive job submsiion failed with exception ”java.io.UTFDataFormatException“
[
https://issues.apache.org/jira/browse/IGNITE-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Mashenkov updated IGNITE-4219:
-
Fix Version/s: 2.0
> Hive job submsiion failed with exception ”java.io.UTFDataFormatException“
> -
>
> Key: IGNITE-4219
> URL: https://issues.apache.org/jira/browse/IGNITE-4219
> Project: Ignite
> Issue Type: Bug
> Components: hadoop
>Reporter: Andrew Mashenkov
> Fix For: 2.0
>
>
> Long property passing to Hadoop causes an exception:
> {code}
> Caused by: java.io.UTFDataFormatException
>at
> java.io.ObjectOutputStream$BlockDataOutputStream.writeUTF(ObjectOutputStream.java:2144)
>
>at
> java.io.ObjectOutputStream$BlockDataOutputStream.writeUTF(ObjectOutputStream.java:1987)
>
>at java.io.ObjectOutputStream.writeUTF(ObjectOutputStream.java:865)
>at
> org.apache.ignite.internal.util.IgniteUtils.writeUTFStringNullable(IgniteUtils.java:5029)
>
>at
> org.apache.ignite.internal.util.IgniteUtils.writeStringMap(IgniteUtils.java:4989)
>
>at
> org.apache.ignite.internal.processors.hadoop.HadoopDefaultJobInfo.writeExternal(HadoopDefaultJobInfo.java:137)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-4157) Use discovery custom messages instead of marshaller and system cache
[ https://issues.apache.org/jira/browse/IGNITE-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15687126#comment-15687126 ] Sergey Chugunov commented on IGNITE-4157: - Implemented requesting of mapping by client when it doesn't have a mapping in local cache it needs to unmarshal some data. This may happen because discovery events are sent to clients asynchronously so it is possible that servers already accepted new mapping but clients aren't aware of it. > Use discovery custom messages instead of marshaller and system cache > > > Key: IGNITE-4157 > URL: https://issues.apache.org/jira/browse/IGNITE-4157 > Project: Ignite > Issue Type: Improvement > Components: cache >Reporter: Alexey Goncharuk >Assignee: Sergey Chugunov > Fix For: 2.0 > > > Currently we use system caches for keeping classname to class ID mapping and > for storing binary metadata > This has several serious disadvantages: > 1) We need to introduce at least two additional thread pools for each of > these caches > 2) Since cache operations require stable topology, registering a class ID or > updating metadata inside a transaction or another cache operation is tricky > and deadlock-prone. > 3) It may be beneficial in some cases to have nodes with no caches at all, > currently this is impossible because system caches are always present. > 4) Reading binary metadata leads to huge local contention, caching metadata > values in a local map doubles memory consumption > I suggest we use discovery custom events for these purposes. Each node will > have a corresponding local map (state) which will be updated inside custom > event handler. From the first point of view, this should remove all the > disadvantages above. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4238) Example for spatial queries
[ https://issues.apache.org/jira/browse/IGNITE-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15687080#comment-15687080 ] Denis Magda commented on IGNITE-4238: - Roman, good catch, thanks! Added the header. > Example for spatial queries > --- > > Key: IGNITE-4238 > URL: https://issues.apache.org/jira/browse/IGNITE-4238 > Project: Ignite > Issue Type: Task > Components: SQL >Affects Versions: 1.7 >Reporter: Denis Magda >Assignee: Vladimir Ozerov >Priority: Blocker > Fix For: 1.8 > > > The geospatial example is missing in Apache examples. It makes sense to add > it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4238) Example for spatial queries
[ https://issues.apache.org/jira/browse/IGNITE-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-4238: Assignee: Vladimir Ozerov (was: Denis Magda) > Example for spatial queries > --- > > Key: IGNITE-4238 > URL: https://issues.apache.org/jira/browse/IGNITE-4238 > Project: Ignite > Issue Type: Task > Components: SQL >Affects Versions: 1.7 >Reporter: Denis Magda >Assignee: Vladimir Ozerov >Priority: Blocker > Fix For: 1.8 > > > The geospatial example is missing in Apache examples. It makes sense to add > it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4238) Example for spatial queries
[
https://issues.apache.org/jira/browse/IGNITE-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15687076#comment-15687076
]
Denis Magda commented on IGNITE-4238:
-
[~vozerov], the example has been already merged but still fails because the
fix from IGNITE-4259 is not in the master. Please merged the fix and validate
it against the example.
To validate the example:
- run the example {{SpatialQueryExample}} from the master;
- run the tests that were added deliberately for it
{{SpatialQueryExampleSelfTest, SpatialQueryExampleMultiNodeSelfTest}}
If the validation of the example succeeds then close this ticket.
> Example for spatial queries
> ---
>
> Key: IGNITE-4238
> URL: https://issues.apache.org/jira/browse/IGNITE-4238
> Project: Ignite
> Issue Type: Task
> Components: SQL
>Affects Versions: 1.7
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Blocker
> Fix For: 1.8
>
>
> The geospatial example is missing in Apache examples. It makes sense to add
> it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-4264) Offheap cache entries statistics is broken in master
[ https://issues.apache.org/jira/browse/IGNITE-4264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-4264: - Description: Reproducer is attached. Test is fine on 1.7 release branch, but fails in master cache.metrics().getOffHeapPrimaryEntriesCount() returns wrong number. Also it seems the number grows with increasing number of clients. was: Reproducer is attached. cache.metrics().getOffHeapPrimaryEntriesCount() returns wrong number. Also it seems the number grows with increasing number of clients. > Offheap cache entries statistics is broken in master > > > Key: IGNITE-4264 > URL: https://issues.apache.org/jira/browse/IGNITE-4264 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Andrew Mashenkov > Fix For: 1.8 > > Attachments: Test.java > > > Reproducer is attached. Test is fine on 1.7 release branch, but fails in > master > cache.metrics().getOffHeapPrimaryEntriesCount() returns wrong number. Also it > seems the number grows with increasing number of clients. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4259) Geospatial functionality is broken in master
[
https://issues.apache.org/jira/browse/IGNITE-4259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15687073#comment-15687073
]
Denis Magda commented on IGNITE-4259:
-
[~amashenkov], [~vozerov], please the changes in the master and after this make
sure that the example from this ticket executes successfully
https://issues.apache.org/jira/browse/IGNITE-4238
To validate the example:
- run the example {{SpatialQueryExample}} from the master;
- run the tests that were added deliberately for it
{{SpatialQueryExampleSelfTest, SpatialQueryExampleMultiNodeSelfTest}}
> Geospatial functionality is broken in master
>
>
> Key: IGNITE-4259
> URL: https://issues.apache.org/jira/browse/IGNITE-4259
> Project: Ignite
> Issue Type: Bug
> Components: binary, SQL
>Reporter: Andrew Mashenkov
>Assignee: Vladimir Ozerov
>Priority: Blocker
> Fix For: 1.8
>
>
> GridH2IndexingGeoSelfTest fails with binary marshaller configured.
> Query parameters are converted to binary since commit "ae77653" as a result
> of [https://issues.apache.org/jira/browse/IGNITE-2208]
> Also see [https://issues.apache.org/jira/browse/IGNITE-4238].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-4264) Offheap cache entries statistics is broken in master
[ https://issues.apache.org/jira/browse/IGNITE-4264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-4264: - Fix Version/s: 1.8 > Offheap cache entries statistics is broken in master > > > Key: IGNITE-4264 > URL: https://issues.apache.org/jira/browse/IGNITE-4264 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Andrew Mashenkov > Fix For: 1.8 > > Attachments: Test.java > > > Reproducer is attached. > cache.metrics().getOffHeapPrimaryEntriesCount() returns wrong number. Also it > seems the number grows with increasing number of clients. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4264) Offheap cache entries statistics is broken in master
[ https://issues.apache.org/jira/browse/IGNITE-4264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-4264: - Description: Reproducer is attached. cache.metrics().getOffHeapPrimaryEntriesCount() returns wrong number. Also it seems the number grows with increasing number of clients. > Offheap cache entries statistics is broken in master > > > Key: IGNITE-4264 > URL: https://issues.apache.org/jira/browse/IGNITE-4264 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Andrew Mashenkov > Attachments: Test.java > > > Reproducer is attached. > cache.metrics().getOffHeapPrimaryEntriesCount() returns wrong number. Also it > seems the number grows with increasing number of clients. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4264) Offheap cache entries statistics is broken in master
[ https://issues.apache.org/jira/browse/IGNITE-4264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-4264: - Attachment: Test.java > Offheap cache entries statistics is broken in master > > > Key: IGNITE-4264 > URL: https://issues.apache.org/jira/browse/IGNITE-4264 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Andrew Mashenkov > Attachments: Test.java > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4264) Offheap cache entries statistics is broken in master
Andrew Mashenkov created IGNITE-4264: Summary: Offheap cache entries statistics is broken in master Key: IGNITE-4264 URL: https://issues.apache.org/jira/browse/IGNITE-4264 Project: Ignite Issue Type: Bug Components: cache Reporter: Andrew Mashenkov -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-3640) IGFS: Local secondary: Investigate whether we need BufferedInputStream for open operation.
[
https://issues.apache.org/jira/browse/IGNITE-3640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15686963#comment-15686963
]
Taras Ledkov edited comment on IGNITE-3640 at 11/22/16 3:01 PM:
Here are results with our simple IgfsBenchmark:
Buffered read: *7048 +/- 125*
Not buffered read: *7150 +/- 127*
Look like the difference is less than dispersion. But the benchmark checks only
serial read file from begin to EOF.
May be if we check repeatable read with changing position inside the buffer the
difference will be more significant.
Should we check it?
was (Author: tledkov-gridgain):
Here are results with our simple IgfsBenchmark:
Buffered read: *7048 +/- 125*
Not buffered read: *7150 +/- 127*
Look like the difference is less then dispersion. But the benchmark checks only
serial read file from begin to EOF.
May be if we check repeatable read with changing position inside the buffer the
difference will be more significant.
Should we check it?
> IGFS: Local secondary: Investigate whether we need BufferedInputStream for
> open operation.
> --
>
> Key: IGNITE-3640
> URL: https://issues.apache.org/jira/browse/IGNITE-3640
> Project: Ignite
> Issue Type: Task
> Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 2.0
>
>
> We need to accurately investigate IGFS input stream workflow. I have doubts
> we really need to extend from {{BufferedInputStream}} here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-4167) Add an option to avoid printing out sensitive data into logs
[ https://issues.apache.org/jira/browse/IGNITE-4167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Kuramshin reassigned IGNITE-4167: -- Assignee: Alexandr Kuramshin > Add an option to avoid printing out sensitive data into logs > > > Key: IGNITE-4167 > URL: https://issues.apache.org/jira/browse/IGNITE-4167 > Project: Ignite > Issue Type: Improvement >Reporter: Denis Kholodov >Assignee: Alexandr Kuramshin > > > We are seeing sensitive cache data being output in ignite debug logging. I've > tracked it down to at least two places: > 1. GridToStringBuilder uses reflection to print all fields in cache objects > that are not annotated with @GridToStringExclude > 2. GridCacheMapEntry does a direct toString() call on the value objects in a > debug log > As a fabric platform, we won't always have control over the object classes > being added to/retrieved from the cache. > We must always assume that all keys and values are sensitive and should not > be outputted in logs except in local debugging situations. To this end, we > need a configuration option (turned OFF by default) that allows keys/values > to be written to log messages. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-3640) IGFS: Local secondary: Investigate whether we need BufferedInputStream for open operation.
[
https://issues.apache.org/jira/browse/IGNITE-3640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15686963#comment-15686963
]
Taras Ledkov edited comment on IGNITE-3640 at 11/22/16 3:00 PM:
Here are results with our simple IgfsBenchmark:
Buffered read: *7048 +/- 125*
Not buffered read: *7150 +/- 127*
Look like the difference is less then dispersion. But the benchmark checks only
serial read file from begin to EOF.
May be if we check repeatable read with changing position inside the buffer the
difference will be more significant.
Should we check it?
was (Author: tledkov-gridgain):
Here are results with our simple IgfsBenchmark:
Buffered read: *7048 +/- 125*
Not buffered read: *7150 +/- 127*
Look like the the difference is less then dispersion. But the benchmark checks
only serial read file from begin to EOF.
May be if we check repeatable read with changing position inside the buffer the
difference will be more significant.
Should we check it?
> IGFS: Local secondary: Investigate whether we need BufferedInputStream for
> open operation.
> --
>
> Key: IGNITE-3640
> URL: https://issues.apache.org/jira/browse/IGNITE-3640
> Project: Ignite
> Issue Type: Task
> Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 2.0
>
>
> We need to accurately investigate IGFS input stream workflow. I have doubts
> we really need to extend from {{BufferedInputStream}} here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3640) IGFS: Local secondary: Investigate whether we need BufferedInputStream for open operation.
[
https://issues.apache.org/jira/browse/IGNITE-3640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15686963#comment-15686963
]
Taras Ledkov commented on IGNITE-3640:
--
Here are results with our simple IgfsBenchmark:
Buffered read: *7048 +/- 125*
Not buffered read: *7150 +/- 127*
Look like the the difference is less then dispersion. But the benchmark checks
only serial read file from begin to EOF.
May be if we check repeatable read with changing position inside the buffer the
difference will be more significant.
Should we check it?
> IGFS: Local secondary: Investigate whether we need BufferedInputStream for
> open operation.
> --
>
> Key: IGNITE-3640
> URL: https://issues.apache.org/jira/browse/IGNITE-3640
> Project: Ignite
> Issue Type: Task
> Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 2.0
>
>
> We need to accurately investigate IGFS input stream workflow. I have doubts
> we really need to extend from {{BufferedInputStream}} here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-4263) Hadoop: abstract out offheap/heap memory management.
Vladimir Ozerov created IGNITE-4263: --- Summary: Hadoop: abstract out offheap/heap memory management. Key: IGNITE-4263 URL: https://issues.apache.org/jira/browse/IGNITE-4263 Project: Ignite Issue Type: Sub-task Components: hadoop Affects Versions: 2.0 Reporter: Vladimir Ozerov Assignee: Vladimir Ozerov Fix For: 2.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4262) Hadoop Accelerator performance improvements.
Vladimir Ozerov created IGNITE-4262: --- Summary: Hadoop Accelerator performance improvements. Key: IGNITE-4262 URL: https://issues.apache.org/jira/browse/IGNITE-4262 Project: Ignite Issue Type: Task Components: hadoop Reporter: Vladimir Ozerov Assignee: Vladimir Ozerov Fix For: 2.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4033) Streamline platform callback interface
[ https://issues.apache.org/jira/browse/IGNITE-4033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15686747#comment-15686747 ] ASF GitHub Bot commented on IGNITE-4033: GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/1261 IGNITE-4033 Streamline platform callback interface You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4033 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/1261.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1261 commit 8fd47a7cd55d1e2dc20d82317c6edecfae17a422 Author: Pavel Tupitsyn Date: 2016-10-27T11:46:32Z IGNITE-4033 Streamline platform callback interface commit 5514c524c4d7fdcbdd3a829b7a6ec6ea543bb978 Author: Pavel Tupitsyn Date: 2016-10-27T12:50:02Z wip commit bd2db702e3a9790a41f6139ad3779bc3b98fcb6d Author: Pavel Tupitsyn Date: 2016-10-27T13:59:54Z wip commit 4cd4268319b14f55f889b016fa5756bbc042e0b7 Author: Pavel Tupitsyn Date: 2016-11-21T12:12:36Z Merge branch 'master' into ignite-4033 commit 5f45226d3c855e44d804455b495529c8699e78cb Author: Pavel Tupitsyn Date: 2016-11-21T12:54:09Z wip commit dc0e632746d18882954aedfb3ce6ab4e66360e13 Author: Pavel Tupitsyn Date: 2016-11-21T13:10:25Z wip commit e95037af839eb7801ece2f7af51a36f99a5b8256 Author: Pavel Tupitsyn Date: 2016-11-21T13:12:46Z wip commit e3ffdf1777b2752eba890b730b7881fb32a3de0f Author: Pavel Tupitsyn Date: 2016-11-21T13:15:08Z wip commit 7f198bdfdd11c447d4b2c760809bce17f070a7d1 Author: Pavel Tupitsyn Date: 2016-11-21T13:40:18Z wip commit afc9b040dcdebf65ea4b96e128b4ca9bed9e02e0 Author: Pavel Tupitsyn Date: 2016-11-21T14:00:32Z wip commit bf9bfcca4355891d107962b0ac7ce8b89763794e Author: Pavel Tupitsyn Date: 2016-11-21T14:01:08Z wip commit 2631bb81c8bbc5de0e026871e68956f86635a08f Author: Pavel Tupitsyn Date: 2016-11-21T14:05:22Z Callbacks propagated commit 351309904cdf5d4a881810280bcddc12dd65acb4 Author: Pavel Tupitsyn Date: 2016-11-21T14:35:24Z Fix jobject arg passing commit 637fdca20d59536b80e973f604d76f7f1af70fff Author: Pavel Tupitsyn Date: 2016-11-21T14:49:49Z wip commit b855921ec23852e8b54ff2f26bcf7be26d6059dd Author: Pavel Tupitsyn Date: 2016-11-21T14:57:16Z wip op codes commit 98df61ffa9d1110caf50cbeef1e0deda94294d61 Author: Pavel Tupitsyn Date: 2016-11-21T15:05:47Z Java op codes commit e98a711cd64e0bcf46c1304c5e016f951b1eeb2d Author: Pavel Tupitsyn Date: 2016-11-21T15:11:04Z wip refactor callbacks commit 44b88c2267e3d8a79ae4c8ad11abd04e97c85e2a Author: Pavel Tupitsyn Date: 2016-11-21T15:13:03Z wip commit 6f33517683f52546249886846f39e5f87f0545f1 Author: Pavel Tupitsyn Date: 2016-11-21T15:17:56Z CacheStoreInvoke commit d9f67fa08f8ec4fbd219231968e08d0b48f09a3c Author: Pavel Tupitsyn Date: 2016-11-21T19:25:46Z Fix longs commit 945b831a1047404dc24d2b97f8049befbfffa8ed Author: Pavel Tupitsyn Date: 2016-11-21T19:36:05Z fix longs commit 64eb2784376be06d5f97a20bb457375c99ef47b8 Author: Pavel Tupitsyn Date: 2016-11-21T20:12:13Z wip commit 9e36fb199e852e1786010595b16fbd0aeeb2f7d6 Author: Pavel Tupitsyn Date: 2016-11-22T07:16:16Z Fix BinaryReader initialization commit c799949cd179eb114232a14fe5d4d5b63812e44a Author: Pavel Tupitsyn Date: 2016-11-22T08:22:28Z Merge branch 'master' into ignite-4033 commit b5945c3b6001b2e14f63e378af1b80caa8f61fec Author: Pavel Tupitsyn Date: 2016-11-22T11:13:39Z Cache store refactored commit 18f7fed4fbfc0424420c6c0ce6a201453be4154d Author: Pavel Tupitsyn Date: 2016-11-22T11:23:28Z wip commit 9099c5b6cc881ac2cb8221ce250b827e40e3b9f3 Author: Pavel Tupitsyn Date: 2016-11-22T12:06:15Z Cache entry filter refactored commit bbfadbf21c636d02e05a1018acf05b3b57eb574c Author: Pavel Tupitsyn Date: 2016-11-22T12:59:04Z Merge branch 'master' into ignite-4033 commit bb20efc8572a90b761a9d71a5c1afc33fe4d92a0 Author: Pavel Tupitsyn Date: 2016-11-22T13:15:46Z Refactor CacheInvoke > Streamline platform callback interface > -- > > Key: IGNITE-4033 > URL: https://issues.apache.org/jira/browse/IGNITE-4033 > Project: Ignite > Issue Type: Sub-task > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 2.0 > > > Similar to PlatformTarget calls (.NET -> Java), we need a symmetrical > universal Java -> .NET callback interface. > All current specialized callbacks should be refactored t
[jira] [Resolved] (IGNITE-4261) .NET: ScanQuery tests are ignored by NUnit
[ https://issues.apache.org/jira/browse/IGNITE-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn resolved IGNITE-4261. Resolution: Fixed Assignee: (was: Pavel Tupitsyn) > .NET: ScanQuery tests are ignored by NUnit > -- > > Key: IGNITE-4261 > URL: https://issues.apache.org/jira/browse/IGNITE-4261 > Project: Ignite > Issue Type: Bug > Components: platforms >Reporter: Pavel Tupitsyn > Labels: .NET > Fix For: 1.8 > > > CacheQueriesTest.TestScanQuery are ignored both on TC and locally: "unable to > determine type arguments for fixture". > This is due to type arguments. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4261) .NET: ScanQuery tests are ignored by NUnit
[ https://issues.apache.org/jira/browse/IGNITE-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-4261: --- Description: CacheQueriesTest.TestScanQuery are ignored both on TC and locally: "unable to determine type arguments for fixture". This is due to type arguments. was: CacheQueriesTest.TestScanQuery are ignored both on TC and locally: "unable to determine type arguments for fixture". Looks like a NUnit bug, we should probably get rid of parametrization here. > .NET: ScanQuery tests are ignored by NUnit > -- > > Key: IGNITE-4261 > URL: https://issues.apache.org/jira/browse/IGNITE-4261 > Project: Ignite > Issue Type: Bug > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 1.8 > > > CacheQueriesTest.TestScanQuery are ignored both on TC and locally: "unable to > determine type arguments for fixture". > This is due to type arguments. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4261) .NET: ScanQuery tests are ignored by NUnit
[ https://issues.apache.org/jira/browse/IGNITE-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-4261: --- Description: CacheQueriesTest.TestScanQuery are ignored both on TC and locally: "unable to determine type arguments for fixture". Looks like a NUnit bug, we should probably get rid of parametrization here. was: Both on TC and locally: "unable to determine type arguments for fixture" Looks like a NUnit bug, we should probably get rid of parametrization here. > .NET: ScanQuery tests are ignored by NUnit > -- > > Key: IGNITE-4261 > URL: https://issues.apache.org/jira/browse/IGNITE-4261 > Project: Ignite > Issue Type: Bug > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 1.8 > > > CacheQueriesTest.TestScanQuery are ignored both on TC and locally: "unable to > determine type arguments for fixture". > Looks like a NUnit bug, we should probably get rid of parametrization here. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4261) .NET: ScanQuery tests are ignored by NUnit
Pavel Tupitsyn created IGNITE-4261: -- Summary: .NET: ScanQuery tests are ignored by NUnit Key: IGNITE-4261 URL: https://issues.apache.org/jira/browse/IGNITE-4261 Project: Ignite Issue Type: Bug Components: platforms Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 1.8 Both on TC and locally: "unable to determine type arguments for fixture" Looks like a NUnit bug, we should probably get rid of parametrization here. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1943) ignitevisorcmd: wrong behavior for "mclear" command
[
https://issues.apache.org/jira/browse/IGNITE-1943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-1943:
Fix Version/s: (was: 1.8)
2.0
> ignitevisorcmd: wrong behavior for "mclear" command
> ---
>
> Key: IGNITE-1943
> URL: https://issues.apache.org/jira/browse/IGNITE-1943
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.5.0.final
>Reporter: Vasilisa Sidorova
>Assignee: Saikat Maitra
> Fix For: 2.0
>
>
> -
> DESCRIPTION
> -
> "mclear" should clears all Visor console variables before they will be
> updated during next run of the corresponding command. It OK for all type of
> shortcut (@cX, @tX, @aX, @eX) exept shortcut for node-id variables. After
> "mclear" @nX are disappear from any statistics
> -
> STEPS FOR REPRODUCE
> -
> # Start cluster
> # Start visorcmd ([IGNITE_HOME]/bin/ignitevisorcmd.sh)
> # Connect to the started cluster (visor> open)
> # Execute any tasks in it (for example, run any example from EventsExample,
> DeploymentExample, ComputeContinuousMapperExample, ComputeTaskMapExample,
> ComputeTaskSplitExample)
> # Create several alerts (visor> alert)
> # Run visor "mclear" command
> # Run visor "node" command
> -
> ACTUAL RESULT
> -
> There isn't @nX values in the first table's column:
> {noformat}
> visor> node
> Select node from:
> +==+
> | # | Node ID8(@), IP | Up Time | CPUs | CPU Load | Free Heap |
> +==+
> | 0 | 6B3E4033, 127.0.0.1 | 00:38:41 | 8| 0.20 % | 97.00 % |
> | 1 | 0A0D6989, 127.0.0.1 | 00:38:22 | 8| 0.17 % | 97.00 % |
> | 2 | 0941E33F, 127.0.0.1 | 00:35:46 | 8| 0.23 % | 97.00 % |
> +--+
> {noformat}
> -
> EXPECTED RESULT
> -
> There is @nX values in the first table's column:
> {noformat}
> visor> node
> Select node from:
> +===+
> | # | Node ID8(@), IP | Up Time | CPUs | CPU Load | Free Heap |
> +===+
> | 0 | 6B3E4033(@n0), 127.0.0.1 | 00:38:13 | 8| 0.23 % | 97.00 % |
> | 1 | 0A0D6989(@n1), 127.0.0.1 | 00:37:54 | 8| 0.27 % | 97.00 % |
> | 2 | 0941E33F(@n2), 127.0.0.1 | 00:35:18 | 8| 0.20 % | 97.00 % |
> +---+
> {noformat}
> "mclear" should get effect only for "mget @nX" command (with result "Missing
> variable with name: '@nX'") and @nX variables should get new values after
> "node" (or "tasks") command execution. Like in case for all others @
> variables (@cX, @tX, @aX, @eX)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-4238) Example for spatial queries
[ https://issues.apache.org/jira/browse/IGNITE-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15686563#comment-15686563 ] Vladimir Ozerov commented on IGNITE-4238: - Guys, Problem with geo indexes is fixed. > Example for spatial queries > --- > > Key: IGNITE-4238 > URL: https://issues.apache.org/jira/browse/IGNITE-4238 > Project: Ignite > Issue Type: Task > Components: SQL >Affects Versions: 1.7 >Reporter: Denis Magda >Assignee: Denis Magda >Priority: Blocker > Fix For: 1.8 > > > The geospatial example is missing in Apache examples. It makes sense to add > it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-4259) Geospatial functionality is broken in master
[ https://issues.apache.org/jira/browse/IGNITE-4259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov reassigned IGNITE-4259: --- Assignee: Vladimir Ozerov (was: Andrew Mashenkov) > Geospatial functionality is broken in master > > > Key: IGNITE-4259 > URL: https://issues.apache.org/jira/browse/IGNITE-4259 > Project: Ignite > Issue Type: Bug > Components: binary, SQL >Reporter: Andrew Mashenkov >Assignee: Vladimir Ozerov >Priority: Blocker > Fix For: 1.8 > > > GridH2IndexingGeoSelfTest fails with binary marshaller configured. > Query parameters are converted to binary since commit "ae77653" as a result > of [https://issues.apache.org/jira/browse/IGNITE-2208] > Also see [https://issues.apache.org/jira/browse/IGNITE-4238]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-4259) Geospatial functionality is broken in master
[ https://issues.apache.org/jira/browse/IGNITE-4259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov resolved IGNITE-4259. - Resolution: Fixed > Geospatial functionality is broken in master > > > Key: IGNITE-4259 > URL: https://issues.apache.org/jira/browse/IGNITE-4259 > Project: Ignite > Issue Type: Bug > Components: binary, SQL >Reporter: Andrew Mashenkov >Assignee: Vladimir Ozerov >Priority: Blocker > Fix For: 1.8 > > > GridH2IndexingGeoSelfTest fails with binary marshaller configured. > Query parameters are converted to binary since commit "ae77653" as a result > of [https://issues.apache.org/jira/browse/IGNITE-2208] > Also see [https://issues.apache.org/jira/browse/IGNITE-4238]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3432) Multiple IGFS on the same caches.
[ https://issues.apache.org/jira/browse/IGNITE-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15686508#comment-15686508 ] ASF GitHub Bot commented on IGNITE-3432: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1201 > Multiple IGFS on the same caches. > - > > Key: IGNITE-3432 > URL: https://issues.apache.org/jira/browse/IGNITE-3432 > Project: Ignite > Issue Type: Bug > Components: IGFS >Affects Versions: 1.6 >Reporter: Vasiliy Sisko >Assignee: Taras Ledkov > Fix For: 1.8 > > Attachments: test2IGFS-client.xml, test2IGFS-server.xml > > > # Configure grid with two IGFSs which use the same caches. > # Run two server nodes. > #* Topology is runned. Written data marked in both IGFSs. > # Run client node. > #* On node start showed validation message that two IGFSs cannot use the same > caches. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4239) Public thread pool starvation is cause of deadlock when user's jobs calls cache.size()
[
https://issues.apache.org/jira/browse/IGNITE-4239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15686504#comment-15686504
]
ASF GitHub Bot commented on IGNITE-4239:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1250
> Public thread pool starvation is cause of deadlock when user's jobs calls
> cache.size()
> --
>
> Key: IGNITE-4239
> URL: https://issues.apache.org/jira/browse/IGNITE-4239
> Project: Ignite
> Issue Type: Bug
> Components: cache, compute
>Affects Versions: 1.6
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Critical
> Fix For: 1.9
>
>
> The users job are hang when a lot of jobs that calculates cache size are
> submitted.
> The log contains message:
> {code}
> WARNING: Possible thread pool starvation detected (no task completed in last
> 3ms, is executorService pool size large enough?)
> {code}
> After a while all the thread of a public thread pool are locked on waiting
> the SizeTask future.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3705) Warnings when build ignite and ignite-example cpp projects with Visual Studio 2015 (v140) toolset
[
https://issues.apache.org/jira/browse/IGNITE-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15686510#comment-15686510
]
ASF GitHub Bot commented on IGNITE-3705:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1169
> Warnings when build ignite and ignite-example cpp projects with Visual Studio
> 2015 (v140) toolset
> -
>
> Key: IGNITE-3705
> URL: https://issues.apache.org/jira/browse/IGNITE-3705
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 1.7
> Environment: Windows 2010, Visual Studio 2015
>Reporter: Ksenia Rybakova
>Assignee: Ksenia Rybakova
>Priority: Minor
> Labels: cpp
> Fix For: 1.8
>
>
> The following warnings apper when build ignite and ignite-example cpp
> projects with Visual Studio 2015 (v140) toolset:
> {noformat}
> platforms\cpp\common\include\ignite/ignite_error.h(90): warning C4275: non
> dll-interface class 'std::exception' used as base for dll-interface class
> 'ignite::IgniteError'
> C:\Program Files (x86)\Microsoft Visual Studio
> 14.0\VC\include\vcruntime_exception.h(43): note: see declaration of
> 'std::exception'
> platforms\cpp\common\include\ignite/ignite_error.h(89): note: see declaration
> of 'ignite::IgniteError'
> cl : Command line warning D9025: overriding '/sdl-' with '/GS-'
> {noformat}
> Steps to reproduce:
> - Install VS 2015 and SDK 8.1
> - Open %IGNITE_HOME%\platforms\cpp\project\vs\ignite.sln and
> %IGNITE_HOME%\platforms\cpp\examples\project\vs\ignite-examples.sln solutions
> in VS
> - Set "Visual Studio 2015 (v140)" as Platform Toolset and "8.1" as Target
> Platform Version in projects properties
> - Build solutions
> Expected:
> - no errors and warnings
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-4053) Task error is always printed to the console.
[
https://issues.apache.org/jira/browse/IGNITE-4053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15686507#comment-15686507
]
ASF GitHub Bot commented on IGNITE-4053:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1160
> Task error is always printed to the console.
>
>
> Key: IGNITE-4053
> URL: https://issues.apache.org/jira/browse/IGNITE-4053
> Project: Ignite
> Issue Type: Bug
> Components: compute
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Minor
> Fix For: 1.8
>
>
> Currently if something wrong happens to the task, it prints error to the
> console:
> {code}
> java.lang.Throwable.printStackTrace(java.lang.Throwable$PrintStreamOrWriter)
> (line: 653)
> java.lang.Throwable.printStackTrace(java.io.PrintStream) (line: 643)
> org.apache.ignite.internal.util.IgniteUtils.error(org.apache.ignite.IgniteLogger,
> java.lang.Object, java.lang.Object, java.lang.Throwable) (line: 4171)
> org.apache.ignite.internal.util.IgniteUtils.error(org.apache.ignite.IgniteLogger,
> java.lang.Object, java.lang.Throwable) (line: 4189)
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(org.apache.ignite.lang.IgniteInClosure)
> (line: 269)
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListeners()
> (line: 250)
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(java.lang.Object,
> java.lang.Throwable, boolean) (line: 380)
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(java.lang.Object,
> java.lang.Throwable)
> org.apache.ignite.internal.processors.task.GridTaskWorker.finishTask(java.lang.Object,
> java.lang.Throwable, boolean) (line: 1475)
> org.apache.ignite.internal.processors.task.GridTaskWorker.finishTask(java.lang.Object,
> java.lang.Throwable) (line: 1443)
> org.apache.ignite.internal.processors.task.GridTaskWorker$4.apply() (line:
> 988)
> org.apache.ignite.internal.processors.task.GridTaskWorker$4.apply()
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(java.lang.ClassLoader,
> org.apache.ignite.lang.IgniteOutClosure) (line: 6516)
> org.apache.ignite.internal.processors.task.GridTaskWorker.result(org.apache.ignite.compute.ComputeJobResult,
> java.util.List)
> org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(org.apache.ignite.internal.GridJobExecuteResponse)
> (line: 810)
> {code}
> This happens because there is no logger in the future, hence error is
> unconditionally printed to the console.
> We need to fix that. Probably we can inject logger into the task future.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-4062) BinaryObject header should not participate in equals test
[
https://issues.apache.org/jira/browse/IGNITE-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15686505#comment-15686505
]
ASF GitHub Bot commented on IGNITE-4062:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1182
> BinaryObject header should not participate in equals test
> -
>
> Key: IGNITE-4062
> URL: https://issues.apache.org/jira/browse/IGNITE-4062
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Taras Ledkov
>Priority: Critical
> Fix For: 1.8
>
>
> {{BinaryObject.equals()}} compares the full byte array, which can give
> incorrect results in come cases. For example, we sometimes write full class
> name instead of type ID, so two objects that are equal from user's standpoint
> will have different binary representation and {{equals()}} will return false.
> We should make {{equals()}} implementation more smart and compare separately:
> * type ID
> * hash code
> * portion of byte array that contains actual data, i.e. fields without header
> and footer
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-4227) ODBC: Implement SQLError function
[
https://issues.apache.org/jira/browse/IGNITE-4227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15686509#comment-15686509
]
ASF GitHub Bot commented on IGNITE-4227:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1237
> ODBC: Implement SQLError function
> -
>
> Key: IGNITE-4227
> URL: https://issues.apache.org/jira/browse/IGNITE-4227
> Project: Ignite
> Issue Type: Task
> Components: odbc
>Affects Versions: 1.7
>Reporter: Igor Sapego
>Assignee: Vladimir Ozerov
> Labels: odbc
> Fix For: 1.8
>
>
> Some driver managers use this function even though {{SQLGetDiagRec}} was
> called.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-4145) "No query result found for request" exception when running multiple queries concurrently.
[
https://issues.apache.org/jira/browse/IGNITE-4145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15686506#comment-15686506
]
ASF GitHub Bot commented on IGNITE-4145:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1218
> "No query result found for request" exception when running multiple queries
> concurrently.
> -
>
> Key: IGNITE-4145
> URL: https://issues.apache.org/jira/browse/IGNITE-4145
> Project: Ignite
> Issue Type: Bug
> Components: SQL
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Assignee: Andrew Mashenkov
> Fix For: 1.8
>
>
> When many queries are executed simultaneously in multi-node cluster, the
> following exception might appear from time to time:
> {code}
> Exception in thread "qry-exec-20" javax.cache.CacheException: Failed to fetch
> data from node: 3432842f-2fa2-44b9-b69b-cadba286d317
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$3.fetchNextPage(GridReduceQueryExecutor.java:298)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridMergeIndex.fetchNextPage(GridMergeIndex.java:229)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridMergeIndexUnsorted$1.hasNext(GridMergeIndexUnsorted.java:106)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridMergeIndex$IteratorCursor.next(GridMergeIndex.java:351)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridMergeIndex$FetchingCursor.next(GridMergeIndex.java:382)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:640)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$4.iterator(IgniteH2Indexing.java:1057)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:81)
> at
> org.apache.ignite.yardstick.ringcentral.AdgRunner$QueryExecutor.run(AdgRunner.java:394)
> at java.lang.Thread.run(Thread.java:745)
> Suppressed: javax.cache.CacheException: Failed to execute map query on
> the node: c51bc4f2-7038-4df6-88a9-eb87506c2f86, class
> javax.cache.CacheException:No query result found for request:
> GridQueryNextPageRequest [qryReqId=93, qry=0, pageSize=1024]
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.fail(GridReduceQueryExecutor.java:259)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onFail(GridReduceQueryExecutor.java:249)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onMessage(GridReduceQueryExecutor.java:230)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.onMessage(GridReduceQueryExecutor.java:178)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:1900)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1080)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:708)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:101)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:671)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> ... 1 more
> {code}
> Quick analysis shows that next-page request could possibly arrive before
> original query message is processed. Need to confirm it with deeper debugging
> first.
> The best way to reproduce it:
> 1) Generate some data
> 2) Start several data nodes (e.g. 4)
> 3) Start client node
> 4) Concurrently execute multiple SQL queries from the client in different
> threads.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-4249) ODBC: Even simple request takes a lot of time.
[ https://issues.apache.org/jira/browse/IGNITE-4249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15686477#comment-15686477 ] ASF GitHub Bot commented on IGNITE-4249: GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/1260 IGNITE-4249: TCP message sended by ODBC driver in single call now. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4249 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/1260.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1260 commit 7290d88e14a15a3d030b7381dbd0a3f14cb65a12 Author: Pavel Tupitsyn Date: 2016-10-18T14:17:17Z IGNITE-4030 Streamline PlatformTarget operation methods This closes #1167 commit 66c76d1f30f024b58db8cab07ba9e7d429f596f8 Author: tledkov-gridgain Date: 2016-10-18T15:45:06Z IGNITE-2355 Fixed the test HadoopClientProtocolMultipleServersSelfTest. Clear connection poll after the test, cosmetic. commit f37fbcab1ae2c7553696e96b7a9c3194a570d7af Author: isapego Date: 2016-10-19T10:06:42Z IGNITE-3705: Fixed compiliation warnings. This closes #1169. commit 7ed2bb7e341701d052220a36a2b2f8f0a46fd644 Author: AMRepo Date: 2016-10-19T15:33:59Z IGNITE-3448 Support SQL queries with distinct aggregates added. This closes #3448. commit 551a4dfae6169a07a5e28f9b266f90311f3216b7 Author: tledkov-gridgain Date: 2016-10-21T10:25:57Z IGNITE-2355 Fixed the test HadoopClientProtocolMultipleServersSelfTest. Clear connection poll before and after the test commit ec12a9db2265180f96be72e2217e60ced856164e Author: vozerov-gridgain Date: 2016-10-24T14:52:36Z Minor fix for flags passed to GridCacheMapEntry.initialValue from data streamer isolated updater. commit 44740465677c39068dc813dabd464e60f09e5f49 Author: tledkov-gridgain Date: 2016-10-26T13:00:11Z IGNITE-4062: fix BinaryObject.equals: compare only bytes containing the fields' data (without header and footer). This closes #1182. commit 9ddb8be1243df8e489f7ebc716d315415775439a Author: Dmitriy Govorukhin Date: 2016-10-27T14:52:22Z IGNITE-2079 GridCacheIoManager eats exception trail if it falls into the directed case merger from ignite-2079-2 # Conflicts: # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/query/GridCacheQueryMetricsAdapter.java commit 6f160728c544d252f77bdb85c0ff2857559707a3 Author: Valentin Kulichenko Date: 2016-10-28T23:18:14Z IGNITE-4110 - Fixed BUFFER_UNDERFLOW and BUFFER_OVERFLOW handling in BlockingSslHandler commit 6b78ad0cbbcf286cb083136c49cebd5dd85de58c Author: sboikov Date: 2016-10-31T07:35:44Z TcoDiscovery: reduced amount of debug logging (heartbeat/connection check messages are logged trace level). commit 175da6b7e394dd76c27d5155ff98a5b2ef03bb9d Author: tledkov-gridgain Date: 2016-11-07T06:16:58Z IGNITE-3432: check data/meta cache names are different for different IGFS instances. This closes #1201 commit 40ef2f5ae42826fe8fd077e3013e8f55c8512bdd Author: Dmitriy Govorukhin Date: 2016-11-07T09:09:41Z ignite-4178 support permission builder commit fc7ce5a4d72145f2e8a86debeda264ef0a5b37e3 Author: isapego Date: 2016-11-07T10:26:05Z IGNITE-4090: Added flags so stdint and limits can be used in C++. commit a98804a249496ba9bafbc96daa7aaf25b3d36724 Author: Igor Sapego Date: 2016-11-07T11:00:00Z IGNITE-4113: Added tests. Added Statement::Set/GetAttribute. commit 950bad474ef29f9b808e74034c49a69d57eb2740 Author: dkarachentsev Date: 2016-11-08T11:03:34Z GG-11655 - Restore service compatibility with releases before 1.5.30. commit 3d19bfc2b66574e3945ce17c7a4dfe77d0070b8d Author: dkarachentsev Date: 2016-11-08T11:04:36Z Merge remote-tracking branch 'origin/ignite-1.6.11' into ignite-1.6.11 commit e821dc0083003bc81058b1cb223d8a8a2ee44daf Author: Dmitriy Govorukhin Date: 2016-11-08T12:09:21Z IGNITE-2079 (revert commit) GridCacheIoManager eats exception trail if it falls into the directed case commit c2c82ca44befe4570325dd6cf2ba885e0d90596c Author: Dmitriy Govorukhin Date: 2016-11-08T12:10:10Z Merge remote-tracking branch 'professional/ignite-1.6.11' into ignite-1.6.11 commit 865bbcf0f41a0c4944e0928f1758d43a0eae82c5 Author: Dmitriy Govorukhin Date: 2016-11-08T12:18:29Z Revert "Merge remote-tracking branch 'professional/ignite-1.6.11' into ignite-1.6.11" This reverts commit c2c82ca44befe4570325dd6cf2ba885e0d90596c, reversing changes made to e821dc0083003bc81058b1cb223d8a8a2ee44daf. commit 9726421ff9efb2b19813b2fd6ad27a3728b5ab1a Author: Dmitriy Govorukhin Date: 2016-11-08T12:59:00Z Revert Revert Merg
[jira] [Commented] (IGNITE-4249) ODBC: Even simple request takes a lot of time.
[
https://issues.apache.org/jira/browse/IGNITE-4249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15686464#comment-15686464
]
ASF GitHub Bot commented on IGNITE-4249:
Github user isapego closed the pull request at:
https://github.com/apache/ignite/pull/1254
> ODBC: Even simple request takes a lot of time.
> --
>
> Key: IGNITE-4249
> URL: https://issues.apache.org/jira/browse/IGNITE-4249
> Project: Ignite
> Issue Type: Bug
> Components: odbc
>Affects Versions: 1.7
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.8
>
>
> Even if you submit very simple request with {{SQLExecute}} on a small data
> set, it's going to take ~40ms to be processed, while the same request in C++
> client takes ~200us.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-4259) Geospatial functionality is broken in master
[
https://issues.apache.org/jira/browse/IGNITE-4259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15686376#comment-15686376
]
Vladimir Ozerov commented on IGNITE-4259:
-
Add {{isGeometryClass}} to {{GridQueryProcessor.initializeCache}} fixes the
problem with incorrect type passed to H2 engine:
{code}
if (binaryEnabled && !keyOrValMustDeserialize) {
// Safe to check null.
if (SQL_TYPES.contains(valCls) || isGeometryClass(valCls))
desc.valueClass(valCls);
else
desc.valueClass(Object.class);
if (SQL_TYPES.contains(keyCls) || isGeometryClass(keyCls))
desc.keyClass(keyCls);
else
desc.keyClass(Object.class);
}
{code}
> Geospatial functionality is broken in master
>
>
> Key: IGNITE-4259
> URL: https://issues.apache.org/jira/browse/IGNITE-4259
> Project: Ignite
> Issue Type: Bug
> Components: binary, SQL
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
>Priority: Blocker
> Fix For: 1.8
>
>
> GridH2IndexingGeoSelfTest fails with binary marshaller configured.
> Query parameters are converted to binary since commit "ae77653" as a result
> of [https://issues.apache.org/jira/browse/IGNITE-2208]
> Also see [https://issues.apache.org/jira/browse/IGNITE-4238].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-4238) Example for spatial queries
[ https://issues.apache.org/jira/browse/IGNITE-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15686326#comment-15686326 ] ASF GitHub Bot commented on IGNITE-4238: Github user AMashenkov closed the pull request at: https://github.com/apache/ignite/pull/1248 > Example for spatial queries > --- > > Key: IGNITE-4238 > URL: https://issues.apache.org/jira/browse/IGNITE-4238 > Project: Ignite > Issue Type: Task > Components: SQL >Affects Versions: 1.7 >Reporter: Denis Magda >Assignee: Denis Magda >Priority: Blocker > Fix For: 1.8 > > > The geospatial example is missing in Apache examples. It makes sense to add > it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-3178) Add escaping of string in generated Java code.
[ https://issues.apache.org/jira/browse/IGNITE-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-3178: - Assignee: Pavel Konstantinov (was: Vasiliy Sisko) > Add escaping of string in generated Java code. > -- > > Key: IGNITE-3178 > URL: https://issues.apache.org/jira/browse/IGNITE-3178 > Project: Ignite > Issue Type: Task > Components: wizards >Affects Versions: 1.7 >Reporter: Vasiliy Sisko >Assignee: Pavel Konstantinov > > F.e a input *"* symbol breaks generated string. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3178) Add escaping of string in generated Java code.
[ https://issues.apache.org/jira/browse/IGNITE-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15686319#comment-15686319 ] Vasiliy Sisko commented on IGNITE-3178: --- Implemented escaping of invalid symbols in: # Generated Java and XML code for string fields. # Names of configuration files on download of project for cluster with wrong file name characters in name. > Add escaping of string in generated Java code. > -- > > Key: IGNITE-3178 > URL: https://issues.apache.org/jira/browse/IGNITE-3178 > Project: Ignite > Issue Type: Task > Components: wizards >Affects Versions: 1.7 >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko > > F.e a input *"* symbol breaks generated string. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4238) Example for spatial queries
[ https://issues.apache.org/jira/browse/IGNITE-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15686315#comment-15686315 ] Roman Shtykh commented on IGNITE-4238: -- Denis, Do the three new files need ASF headers? > Example for spatial queries > --- > > Key: IGNITE-4238 > URL: https://issues.apache.org/jira/browse/IGNITE-4238 > Project: Ignite > Issue Type: Task > Components: SQL >Affects Versions: 1.7 >Reporter: Denis Magda >Assignee: Denis Magda >Priority: Blocker > Fix For: 1.8 > > > The geospatial example is missing in Apache examples. It makes sense to add > it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4259) Geospatial functionality is broken in master
[ https://issues.apache.org/jira/browse/IGNITE-4259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-4259: - Description: GridH2IndexingGeoSelfTest fails with binary marshaller configured. Query parameters are converted to binary since commit "ae77653" as a result of [https://issues.apache.org/jira/browse/IGNITE-2208] Also see [https://issues.apache.org/jira/browse/IGNITE-4238]. was: See [https://issues.apache.org/jira/browse/IGNITE-4238]. GridH2IndexingGeoSelfTest fails with binary marshaller configured. > Geospatial functionality is broken in master > > > Key: IGNITE-4259 > URL: https://issues.apache.org/jira/browse/IGNITE-4259 > Project: Ignite > Issue Type: Bug > Components: binary, SQL >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov >Priority: Blocker > Fix For: 1.8 > > > GridH2IndexingGeoSelfTest fails with binary marshaller configured. > Query parameters are converted to binary since commit "ae77653" as a result > of [https://issues.apache.org/jira/browse/IGNITE-2208] > Also see [https://issues.apache.org/jira/browse/IGNITE-4238]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4260) Web Console: For project with SQLServer add dependency on mssql-jdbc driver from maven central
[ https://issues.apache.org/jira/browse/IGNITE-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov updated IGNITE-4260: --- Affects Version/s: 1.7 Component/s: wizards > Web Console: For project with SQLServer add dependency on mssql-jdbc driver > from maven central > -- > > Key: IGNITE-4260 > URL: https://issues.apache.org/jira/browse/IGNITE-4260 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 1.7 >Reporter: Andrey Novikov >Priority: Minor > > https://github.com/Microsoft/mssql-jdbc/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4260) Web Console: For project with SQLServer add dependency on mssql-jdbc driver from maven central
[ https://issues.apache.org/jira/browse/IGNITE-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov updated IGNITE-4260: --- Priority: Minor (was: Major) > Web Console: For project with SQLServer add dependency on mssql-jdbc driver > from maven central > -- > > Key: IGNITE-4260 > URL: https://issues.apache.org/jira/browse/IGNITE-4260 > Project: Ignite > Issue Type: Bug >Reporter: Andrey Novikov >Priority: Minor > > https://github.com/Microsoft/mssql-jdbc/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4260) Web Console: For project with SQLServer add dependency on mssql-jdbc driver from maven central
Andrey Novikov created IGNITE-4260: -- Summary: Web Console: For project with SQLServer add dependency on mssql-jdbc driver from maven central Key: IGNITE-4260 URL: https://issues.apache.org/jira/browse/IGNITE-4260 Project: Ignite Issue Type: Bug Reporter: Andrey Novikov https://github.com/Microsoft/mssql-jdbc/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4259) Geospatial functionality is broken in master
[ https://issues.apache.org/jira/browse/IGNITE-4259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15686277#comment-15686277 ] ASF GitHub Bot commented on IGNITE-4259: GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1257 IGNITE-4259: Geospatial functionality is broken in master Tests added. Feasible fix added. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4259 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/1257.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1257 commit bfb00b6e61f9709718c30971997aeb0ac79e86b4 Author: Alexandr Kuramshin Date: 2016-11-18T20:12:28Z IgniteTcpCommunicationBigClusterTest added commit 02dd92e605b9b53f5a16c7ec5f8e7b5698b15ba4 Author: Alexandr Kuramshin Date: 2016-11-18T21:55:37Z IgniteTcpCommunicationBigClusterTest update commit 6acf193a3d356d1bad4c02a53ac76833ed1008d0 Author: Alexandr Kuramshin Date: 2016-11-19T09:55:45Z Have got TcpCommunicationSpi error commit 4fd39653d24f62f19f70b4dffba8497185cc46fb Author: Alexandr Kuramshin Date: 2016-11-19T16:39:10Z Some discovery have been done commit c2c181922c7c24ea457577e32d2af897c8bec87f Author: Alexandr Kuramshin Date: 2016-11-19T20:11:28Z Prove that problem is not in the onFirstMessage hang commit f8076edba097f6077229b2090ee3ff1a3369878c Author: Alexandr Kuramshin Date: 2016-11-19T20:26:37Z Revert: Prove that problem is not in the onFirstMessage hang commit 6e1f2dfc2acb3dbb8f24aa51ed67b2ee447b4585 Author: Alexandr Kuramshin Date: 2016-11-21T08:55:09Z Revert: pushing unnecessary changes to the master commit ed794ca815f6bb1471af15779279d287576b39cc Author: Alexandr Kuramshin Date: 2016-11-21T09:08:00Z Revert: pushing unnecessary changes to the master commit dd550060b810d78cbf7ead7859723fc280be2b5f Author: Andrey V. Mashenkov Date: 2016-11-22T10:02:37Z Exclude geo-classes from serialization in binary marshaller. Tests added. > Geospatial functionality is broken in master > > > Key: IGNITE-4259 > URL: https://issues.apache.org/jira/browse/IGNITE-4259 > Project: Ignite > Issue Type: Bug > Components: binary, SQL >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov >Priority: Blocker > Fix For: 1.8 > > > See [https://issues.apache.org/jira/browse/IGNITE-4238]. > GridH2IndexingGeoSelfTest fails with binary marshaller configured. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4238) Example for spatial queries
[ https://issues.apache.org/jira/browse/IGNITE-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-4238: - Assignee: Denis Magda (was: Andrew Mashenkov) > Example for spatial queries > --- > > Key: IGNITE-4238 > URL: https://issues.apache.org/jira/browse/IGNITE-4238 > Project: Ignite > Issue Type: Task > Components: SQL >Affects Versions: 1.7 >Reporter: Denis Magda >Assignee: Denis Magda >Priority: Blocker > Fix For: 1.8 > > > The geospatial example is missing in Apache examples. It makes sense to add > it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-4259) Geospatial functionality is broken in master
[ https://issues.apache.org/jira/browse/IGNITE-4259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov reassigned IGNITE-4259: Assignee: Andrew Mashenkov > Geospatial functionality is broken in master > > > Key: IGNITE-4259 > URL: https://issues.apache.org/jira/browse/IGNITE-4259 > Project: Ignite > Issue Type: Bug > Components: binary, SQL >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov >Priority: Blocker > Fix For: 1.8 > > > See [https://issues.apache.org/jira/browse/IGNITE-4238]. > GridH2IndexingGeoSelfTest fails with binary marshaller configured. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4259) Geospatial functionality is broken in master
[ https://issues.apache.org/jira/browse/IGNITE-4259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-4259: - Description: See [https://issues.apache.org/jira/browse/IGNITE-4238]. GridH2IndexingGeoSelfTest fails with binary marshaller configured. was: See [https://issues.apache.org/jira/browse/IGNITE-4238]. > Geospatial functionality is broken in master > > > Key: IGNITE-4259 > URL: https://issues.apache.org/jira/browse/IGNITE-4259 > Project: Ignite > Issue Type: Bug > Components: binary, SQL >Reporter: Andrew Mashenkov >Priority: Blocker > Fix For: 1.8 > > > See [https://issues.apache.org/jira/browse/IGNITE-4238]. > GridH2IndexingGeoSelfTest fails with binary marshaller configured. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4259) Geospatial functionality is broken in master
[ https://issues.apache.org/jira/browse/IGNITE-4259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-4259: - Description: See [https://issues.apache.org/jira/browse/IGNITE-4238]. was:See [https://issues.apache.org/jira/browse/IGNITE-4238] > Geospatial functionality is broken in master > > > Key: IGNITE-4259 > URL: https://issues.apache.org/jira/browse/IGNITE-4259 > Project: Ignite > Issue Type: Bug > Components: binary, SQL >Reporter: Andrew Mashenkov >Priority: Blocker > Fix For: 1.8 > > > See [https://issues.apache.org/jira/browse/IGNITE-4238]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4259) Geospatial functionality is broken in master
Andrew Mashenkov created IGNITE-4259: Summary: Geospatial functionality is broken in master Key: IGNITE-4259 URL: https://issues.apache.org/jira/browse/IGNITE-4259 Project: Ignite Issue Type: Bug Components: binary, SQL Reporter: Andrew Mashenkov Priority: Blocker Fix For: 1.8 See [https://issues.apache.org/jira/browse/IGNITE-4238] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4179) ExampleNodeStartup fails with IllegalStateException: Cache stopped: CacheQueryExamplePersons for CacheQueryExample
[
https://issues.apache.org/jira/browse/IGNITE-4179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-4179:
Priority: Major (was: Critical)
> ExampleNodeStartup fails with IllegalStateException: Cache stopped:
> CacheQueryExamplePersons for CacheQueryExample
> ---
>
> Key: IGNITE-4179
> URL: https://issues.apache.org/jira/browse/IGNITE-4179
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.7
>Reporter: Sergey Kozlov
> Fix For: 1.8
>
>
> 1. Start two {{ExampleNodeStartup}}
> 2. Run {{CacheQueryExample}}
> 3. All server nodes threw the following exception:
> {noformat}
> java.lang.IllegalStateException: Cache stopped: CacheQueryExamplePersons
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.topology(GridCacheContext.java:827)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionsReservation.release(GridDhtPartitionsReservation.java:207)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2QueryContext.clearContext(GridH2QueryContext.java:419)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2QueryContext.doClear(GridH2QueryContext.java:402)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2QueryContext.clearAfterDeadNode(GridH2QueryContext.java:437)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor$1.onEvent(GridMapQueryExecutor.java:156)
> at
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:770)
> at
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:755)
> at
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record(GridEventStorageManager.java:295)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.recordEvent(GridDiscoveryManager.java:2102)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body0(GridDiscoveryManager.java:2310)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body(GridDiscoveryManager.java:2142)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2294) Implement SQL DML (insert, update, delete) clauses.
[ https://issues.apache.org/jira/browse/IGNITE-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-2294: Issue Type: New Feature (was: Wish) > Implement SQL DML (insert, update, delete) clauses. > --- > > Key: IGNITE-2294 > URL: https://issues.apache.org/jira/browse/IGNITE-2294 > Project: Ignite > Issue Type: New Feature > Components: SQL >Reporter: Sergi Vladykin >Assignee: Alexander Paschenko > Labels: important > Fix For: 1.8 > > > We need to add parsing for all the listed SQL commands and translate them > into respective cache operations (putIfAbstent, put, remove). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2294) Implement SQL DML (insert, update, delete) clauses.
[ https://issues.apache.org/jira/browse/IGNITE-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-2294: Component/s: SQL > Implement SQL DML (insert, update, delete) clauses. > --- > > Key: IGNITE-2294 > URL: https://issues.apache.org/jira/browse/IGNITE-2294 > Project: Ignite > Issue Type: Wish > Components: SQL >Reporter: Sergi Vladykin >Assignee: Alexander Paschenko > Labels: important > Fix For: 1.8 > > > We need to add parsing for all the listed SQL commands and translate them > into respective cache operations (putIfAbstent, put, remove). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4200) ODBC: Integrate generation of the ODBC installer to build process.
[ https://issues.apache.org/jira/browse/IGNITE-4200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4200: Fix Version/s: (was: 1.8) 2.0 > ODBC: Integrate generation of the ODBC installer to build process. > -- > > Key: IGNITE-4200 > URL: https://issues.apache.org/jira/browse/IGNITE-4200 > Project: Ignite > Issue Type: Task > Components: build, odbc >Affects Versions: 1.7 >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 2.0 > > > We are going to have ability to generate ODBC driver soon. We should add > generation of such an installer as a build step. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4200) ODBC: Integrate generation of the ODBC installer to build process.
[ https://issues.apache.org/jira/browse/IGNITE-4200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4200: Labels: (was: build odbc) > ODBC: Integrate generation of the ODBC installer to build process. > -- > > Key: IGNITE-4200 > URL: https://issues.apache.org/jira/browse/IGNITE-4200 > Project: Ignite > Issue Type: Task > Components: build, odbc >Affects Versions: 1.7 >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 2.0 > > > We are going to have ability to generate ODBC driver soon. We should add > generation of such an installer as a build step. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-3999) Support case insensitive search in SQL
[
https://issues.apache.org/jira/browse/IGNITE-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-3999:
Fix Version/s: (was: 1.8)
2.0
> Support case insensitive search in SQL
> --
>
> Key: IGNITE-3999
> URL: https://issues.apache.org/jira/browse/IGNITE-3999
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Amir Akhmedov
>Priority: Critical
> Fix For: 2.0
>
>
> Currently case insensitive search is possible only with the help of
> {{lower()}} function:
> {code}
> select name from MyValue where lower(name) = 'abc_5'
> {code}
> But this will always be a full scan, even if {{name}} field is indexed.
> We need to correctly support {{VARCHAR_IGNORECASE}} H2 type in Ignite and add
> a respective property to {{@QuerySqlField}} annotation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3997) .NET: Readme.io documentation update for 1.8
[ https://issues.apache.org/jira/browse/IGNITE-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-3997: Component/s: documentation > .NET: Readme.io documentation update for 1.8 > > > Key: IGNITE-3997 > URL: https://issues.apache.org/jira/browse/IGNITE-3997 > Project: Ignite > Issue Type: Task > Components: documentation, platforms >Affects Versions: 1.8 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 1.8 > > > Update documentation for new features: > * Logging > * ASP.NET Session State > * Entity Framework caching > etc > Mention EF6 2nd level cache on StackOverflow: > google.com/search?q=efcache.codeplex.com+site%3Astackoverflow.com -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-3699) CreatedExpiryPolicy doesn't work if entry is loaded from store
[
https://issues.apache.org/jira/browse/IGNITE-3699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-3699:
Fix Version/s: (was: 1.8)
2.0
> CreatedExpiryPolicy doesn't work if entry is loaded from store
> --
>
> Key: IGNITE-3699
> URL: https://issues.apache.org/jira/browse/IGNITE-3699
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Amir Akhmedov
> Fix For: 2.0
>
> Attachments: LoadWithExpiryTest.java
>
>
> According to JCache spec, {{ExpiryPolicy.getExpiryForCreation()}} must be
> triggered on {{get()}} operation if the entry is loaded from the store.
> Currently this is not happening.
> Test reproducing the issue is attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-4018) DML: Add documentation to Apache Ignite Readme.io
[ https://issues.apache.org/jira/browse/IGNITE-4018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4018: Component/s: documentation > DML: Add documentation to Apache Ignite Readme.io > - > > Key: IGNITE-4018 > URL: https://issues.apache.org/jira/browse/IGNITE-4018 > Project: Ignite > Issue Type: Sub-task > Components: documentation, SQL >Reporter: Denis Magda >Assignee: Alexander Paschenko >Priority: Critical > Fix For: 1.8 > > > In Apache Ignite 1.8 the community is planning to release DML support. > To adopt DML usage we need to add documentation about the feature. > Let's create a new page for now named DML and place it under SQL Queries page > [1] in the menu. The content should be the following: > - Basic overview. > - Description of INSERT, UPDATE, MERGE commands with code snippet examples. > - There should be paragraphs saying that it's supported by our JDBC and ODBC > drivers (refer to the relevant ODBC page's section IGNITE-4019). > - As a part of this ticket add a section to existed JDBC Driver page [2] > describing that it works over the driver as well. Provide a code snippet > example. Refer to this section from the main DML page. > The page should be hidden until 1.8 gets released. Once you've done assign > the ticket to [~pgarg] for polishing and review. > [1] https://apacheignite.readme.io/docs/sql-queries > [2] https://apacheignite.readme.io/docs/jdbc-driver -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4233) Add documentation for REDIS support
[ https://issues.apache.org/jira/browse/IGNITE-4233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4233: Component/s: documentation > Add documentation for REDIS support > --- > > Key: IGNITE-4233 > URL: https://issues.apache.org/jira/browse/IGNITE-4233 > Project: Ignite > Issue Type: Sub-task > Components: documentation >Affects Versions: 1.8 >Reporter: Andrey Novikov >Assignee: Roman Shtykh > Labels: redis > Fix For: 1.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4202) .NET: Document Entity Framework caching on readme.io
[ https://issues.apache.org/jira/browse/IGNITE-4202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4202: Component/s: documentation > .NET: Document Entity Framework caching on readme.io > > > Key: IGNITE-4202 > URL: https://issues.apache.org/jira/browse/IGNITE-4202 > Project: Ignite > Issue Type: Task > Components: documentation, platforms >Reporter: Pavel Tupitsyn >Assignee: Prachi Garg >Priority: Trivial > Labels: .NET > Fix For: 1.8 > > > Keep the page hidden until release > https://apacheignite-net.readme.io/docs/entity-framework-second-level-cache -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4203) .NET: Document ASP.NET Session State caching on readme.io
[ https://issues.apache.org/jira/browse/IGNITE-4203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4203: Component/s: documentation > .NET: Document ASP.NET Session State caching on readme.io > - > > Key: IGNITE-4203 > URL: https://issues.apache.org/jira/browse/IGNITE-4203 > Project: Ignite > Issue Type: Task > Components: documentation, platforms >Reporter: Pavel Tupitsyn >Assignee: Prachi Garg >Priority: Trivial > Labels: .NET > Fix For: 1.8 > > > Keep the page hidden until release > https://apacheignite-net.readme.io/docs/aspnet-session-state-caching -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4249) ODBC: Even simple request takes a lot of time.
[
https://issues.apache.org/jira/browse/IGNITE-4249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-4249:
Labels: (was: odbc)
> ODBC: Even simple request takes a lot of time.
> --
>
> Key: IGNITE-4249
> URL: https://issues.apache.org/jira/browse/IGNITE-4249
> Project: Ignite
> Issue Type: Bug
> Components: odbc
>Affects Versions: 1.7
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.8
>
>
> Even if you submit very simple request with {{SQLExecute}} on a small data
> set, it's going to take ~40ms to be processed, while the same request in C++
> client takes ~200us.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-4249) ODBC: Even simple request takes a lot of time.
[
https://issues.apache.org/jira/browse/IGNITE-4249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-4249:
Component/s: odbc
> ODBC: Even simple request takes a lot of time.
> --
>
> Key: IGNITE-4249
> URL: https://issues.apache.org/jira/browse/IGNITE-4249
> Project: Ignite
> Issue Type: Bug
> Components: odbc
>Affects Versions: 1.7
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.8
>
>
> Even if you submit very simple request with {{SQLExecute}} on a small data
> set, it's going to take ~40ms to be processed, while the same request in C++
> client takes ~200us.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-4175) SQL: JdbcResultSet class wasNull() method should return true on NULL fields
[ https://issues.apache.org/jira/browse/IGNITE-4175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15686140#comment-15686140 ] ASF GitHub Bot commented on IGNITE-4175: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1235 > SQL: JdbcResultSet class wasNull() method should return true on NULL fields > --- > > Key: IGNITE-4175 > URL: https://issues.apache.org/jira/browse/IGNITE-4175 > Project: Ignite > Issue Type: Bug > Components: SQL >Affects Versions: 1.6, 1.7 >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov > Labels: newbie > Fix For: 1.8 > > > For now wasNull() method can return false for NULL field in case of field > typed as String. > Startpoints are org.apache.ignite.internal.jdbc.JdbcResultSet class > and org.apache.ignite.internal.jdbc2.JdbcResultSet class -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4238) Example for spatial queries
[ https://issues.apache.org/jira/browse/IGNITE-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4238: Affects Version/s: 1.6 > Example for spatial queries > --- > > Key: IGNITE-4238 > URL: https://issues.apache.org/jira/browse/IGNITE-4238 > Project: Ignite > Issue Type: Task > Components: SQL >Affects Versions: 1.7 >Reporter: Denis Magda >Assignee: Andrew Mashenkov >Priority: Blocker > Fix For: 1.8 > > > The geospatial example is missing in Apache examples. It makes sense to add > it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4238) Example for spatial queries
[ https://issues.apache.org/jira/browse/IGNITE-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4238: Affects Version/s: (was: 1.6) 1.7 > Example for spatial queries > --- > > Key: IGNITE-4238 > URL: https://issues.apache.org/jira/browse/IGNITE-4238 > Project: Ignite > Issue Type: Task > Components: SQL >Affects Versions: 1.7 >Reporter: Denis Magda >Assignee: Andrew Mashenkov >Priority: Blocker > Fix For: 1.8 > > > The geospatial example is missing in Apache examples. It makes sense to add > it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4238) Example for spatial queries
[ https://issues.apache.org/jira/browse/IGNITE-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4238: Component/s: SQL > Example for spatial queries > --- > > Key: IGNITE-4238 > URL: https://issues.apache.org/jira/browse/IGNITE-4238 > Project: Ignite > Issue Type: Task > Components: SQL >Reporter: Denis Magda >Assignee: Andrew Mashenkov >Priority: Blocker > Fix For: 1.8 > > > The geospatial example is missing in Apache examples. It makes sense to add > it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4238) Example for spatial queries
[ https://issues.apache.org/jira/browse/IGNITE-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4238: Affects Version/s: (was: 1.7) > Example for spatial queries > --- > > Key: IGNITE-4238 > URL: https://issues.apache.org/jira/browse/IGNITE-4238 > Project: Ignite > Issue Type: Task > Components: SQL >Reporter: Denis Magda >Assignee: Andrew Mashenkov >Priority: Blocker > Fix For: 1.8 > > > The geospatial example is missing in Apache examples. It makes sense to add > it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4238) Example for spatial queries
[ https://issues.apache.org/jira/browse/IGNITE-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-4238: Affects Version/s: 1.7 > Example for spatial queries > --- > > Key: IGNITE-4238 > URL: https://issues.apache.org/jira/browse/IGNITE-4238 > Project: Ignite > Issue Type: Task > Components: SQL >Reporter: Denis Magda >Assignee: Andrew Mashenkov >Priority: Blocker > Fix For: 1.8 > > > The geospatial example is missing in Apache examples. It makes sense to add > it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-4258) .NET: BinaryReader ignores current stream position
[ https://issues.apache.org/jira/browse/IGNITE-4258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn reassigned IGNITE-4258: -- Assignee: (was: Pavel Tupitsyn) > .NET: BinaryReader ignores current stream position > -- > > Key: IGNITE-4258 > URL: https://issues.apache.org/jira/browse/IGNITE-4258 > Project: Ignite > Issue Type: Bug > Components: platforms >Reporter: Pavel Tupitsyn > Labels: .NET > Fix For: 1.8 > > > BinaryReader initializes _curPos to 0 always and ignores current stream > position. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4258) .NET: BinaryReader ignores current stream position
[ https://issues.apache.org/jira/browse/IGNITE-4258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15686046#comment-15686046 ] ASF GitHub Bot commented on IGNITE-4258: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1255 > .NET: BinaryReader ignores current stream position > -- > > Key: IGNITE-4258 > URL: https://issues.apache.org/jira/browse/IGNITE-4258 > Project: Ignite > Issue Type: Bug > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 1.8 > > > BinaryReader initializes _curPos to 0 always and ignores current stream > position. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-4258) .NET: BinaryReader ignores current stream position
[ https://issues.apache.org/jira/browse/IGNITE-4258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn resolved IGNITE-4258. Resolution: Fixed > .NET: BinaryReader ignores current stream position > -- > > Key: IGNITE-4258 > URL: https://issues.apache.org/jira/browse/IGNITE-4258 > Project: Ignite > Issue Type: Bug > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 1.8 > > > BinaryReader initializes _curPos to 0 always and ignores current stream > position. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4152) Make ignite-shmem lib optional
[
https://issues.apache.org/jira/browse/IGNITE-4152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-4152:
Fix Version/s: (was: 1.8)
2.0
> Make ignite-shmem lib optional
> --
>
> Key: IGNITE-4152
> URL: https://issues.apache.org/jira/browse/IGNITE-4152
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.7
>Reporter: Denis Magda
>Assignee: Vladimir Ozerov
> Fix For: 2.0
>
>
> Presently, if someone starts up a cluster and has at least two nodes running
> on a single Unix machine then those nodes will be communicating over the
> shared memory (shmem) by default.
> This approach sounds absolutely reasonable but the shmem library is not ideal
> at the moment. There are many situations when a cluster may hang in the
> production or during long running tests due to some unclear issues in shmem
> internals. Even from Ignite community side we have the following shmem
> related issues
> https://issues.apache.org/jira/browse/IGNITE-1578
> https://issues.apache.org/jira/browse/IGNITE-1294
> Let's make the shmem lib optional by putting it into
> "{{ignite-release/libs/optional}}" folder and removing any explicit reference
> we may have in a pom.xml file.
> Refer to this discussion for more details:
> http://apache-ignite-developers.2346864.n4.nabble.com/Making-Ignite-shmem-library-optional-td11874.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-4003) Slow or faulty client can stall the whole cluster.
[
https://issues.apache.org/jira/browse/IGNITE-4003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-4003:
Fix Version/s: (was: 1.8)
2.0
> Slow or faulty client can stall the whole cluster.
> --
>
> Key: IGNITE-4003
> URL: https://issues.apache.org/jira/browse/IGNITE-4003
> Project: Ignite
> Issue Type: Bug
> Components: cache, general
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Assignee: Andrey Gura
>Priority: Critical
> Fix For: 2.0
>
>
> Steps to reproduce:
> 1) Start two server nodes and some data to cache.
> 2) Start a client from Docker subnet, which is not visible from the outside.
> Client will join the cluster.
> 3) Try to put something to cache or start another node to force rabalance.
> Cluster is stuck at this moment. Root cause - servers are constantly trying
> to establish outgoing connection to the client, but fail as Docker subnet is
> not visible from the outside. It may stop virtually all cluster operations.
> Typical thread dump:
> {code}
> org.apache.ignite.IgniteCheckedException: Failed to send message (node may
> have left the grid or TCP connection cannot be established due to firewall
> issues) [node=TcpDiscoveryNode [id=a15d74c2-1ec2-4349-9640-aeacd70d8714,
> addrs=[127.0.0.1, 172.17.0.6], sockAddrs=[/127.0.0.1:0, /127.0.0.1:0,
> /172.17.0.6:0], discPort=0, order=7241, intOrder=3707,
> lastExchangeTime=1474096941045, loc=false, ver=1.5.23#20160526-sha1:259146da,
> isClient=true], topic=T4 [topic=TOPIC_CACHE,
> id1=949732fd-1360-3a58-8d9e-0ff6ea6182cc,
> id2=a15d74c2-1ec2-4349-9640-aeacd70d8714, id3=2], msg=GridContinuousMessage
> [type=MSG_EVT_NOTIFICATION, routineId=7e13c48e-6933-48b2-9f15-8d92007930db,
> data=null, futId=null], policy=2]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1129)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.sendOrderedMessage(GridIoManager.java:1347)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.sendWithRetries(GridContinuousProcessor.java:1227)
> ~[ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.sendWithRetries(GridContinuousProcessor.java:1198)
> ~[ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.sendWithRetries(GridContinuousProcessor.java:1180)
> ~[ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.sendNotification(GridContinuousProcessor.java:841)
> ~[ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.addNotification(GridContinuousProcessor.java:800)
> ~[ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.onEntryUpdate(CacheContinuousQueryHandler.java:787)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.access$700(CacheContinuousQueryHandler.java:91)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler$1.onEntryUpdated(CacheContinuousQueryHandler.java:412)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryManager.onEntryUpdated(CacheContinuousQueryManager.java:343)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryManager.onEntryUpdated(CacheContinuousQueryManager.java:250)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.initialValue(GridCacheMapEntry.java:3476)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtForceKeysFuture$MiniFuture.onResult(GridDhtForceKeysFuture.java:548)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtForceKeysFuture.onResult(GridDhtForceKeysFuture.java:207)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.processForceKeyResponse(GridDhtPreloader.java:636)
> [ignite-core-1.5.23.jar:1.5.23]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.access$1000(GridDhtPreloader.java:81)
> [ignite-core-1.5.23
[jira] [Updated] (IGNITE-3955) IgniteCache.invokeAll returns empty result set in ATOMIC cache
[
https://issues.apache.org/jira/browse/IGNITE-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-3955:
Fix Version/s: (was: 1.8)
2.0
> IgniteCache.invokeAll returns empty result set in ATOMIC cache
> --
>
> Key: IGNITE-3955
> URL: https://issues.apache.org/jira/browse/IGNITE-3955
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.7
>Reporter: Pavel Tupitsyn
>Assignee: Konstantin Dudkov
> Fix For: 2.0
>
>
> When entry processor is invoked from multiple threads, result set is
> sometimes empty.
> This happens with ATOMIC cache, but not with TRANSACTIONAL.
> To reproduce, paste the following into GridCacheAbstractFullApiSelfTest.java:
> {code}
> public void testInvokeAllMultithreaded() throws Exception {
> final IgniteCache cache = jcache();
> final int threadCnt = 4;
> final int cnt = 9;
> final Set keys = Collections.singleton("myKey");
> GridTestUtils.runMultiThreaded(new Runnable() {
> @Override public void run() {
> for (int i = 0; i < cnt; i++) {
> final Map> res =
> cache.invokeAll(keys, new CacheEntryProcessor Integer, Integer>() {
> @Override
> public Integer process(MutableEntry Integer> entry,
> Object... objects) throws
> EntryProcessorException {
> Integer val = entry.getValue();
> if (val == null)
> val = 0;
> val++;
> entry.setValue(val);
> return val;
> }
> });
> assertEquals(1, res.size());
> }
> }
> }, threadCnt, "testInvokeAllMultithreaded");
> assertEquals(cnt*threadCnt, (int)cache.get("myKey"));
> }
> {code}
> Run this test as part of GridCacheAtomicFullApiSelfTest.java.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3610) Implements RAMP transactions on top of Cassandra
[ https://issues.apache.org/jira/browse/IGNITE-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-3610: Fix Version/s: (was: 1.8) 2.0 > Implements RAMP transactions on top of Cassandra > > > Key: IGNITE-3610 > URL: https://issues.apache.org/jira/browse/IGNITE-3610 > Project: Ignite > Issue Type: Sub-task > Components: cache >Reporter: Igor Rudyak >Assignee: Igor Rudyak > Fix For: 2.0 > > > Implement RAMP transaction (http://www.bailis.org/papers/ramp-sigmod2014.pdf) > to provide atomic read isolation for cache data modified withing transaction. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2377) Docker image hangs on Mac OS
[
https://issues.apache.org/jira/browse/IGNITE-2377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-2377:
Fix Version/s: (was: 1.8)
2.0
> Docker image hangs on Mac OS
>
>
> Key: IGNITE-2377
> URL: https://issues.apache.org/jira/browse/IGNITE-2377
> Project: Ignite
> Issue Type: Wish
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Chandresh Pancholi
> Labels: newbie
> Fix For: 2.0
>
>
> Docker hangs at the point when {{CommandLineRandomNumberGenerator}} is being
> executed. The reason is that the current and previous Docker version has some
> bug that can be overcame if to put {{System.exit(0)}} at the end of
> {{main(...)}} function.
> More investigation details and steps to reproduce can be found here:
> http://stackoverflow.com/questions/34661934/ignite-running-in-docker-is-general-java-docker-issue
> It makes sense to add {{System.exit(0)}} to all our classes that are executed
> by {{ignite.bat}} or {{ignite.sh}} because it's not harmful in any case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3569) Set copyOnRead property to FALSE for marshaller cache
[ https://issues.apache.org/jira/browse/IGNITE-3569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-3569: Component/s: cache > Set copyOnRead property to FALSE for marshaller cache > - > > Key: IGNITE-3569 > URL: https://issues.apache.org/jira/browse/IGNITE-3569 > Project: Ignite > Issue Type: Improvement > Components: cache >Reporter: Yakov Zhdanov >Assignee: Yakov Zhdanov > Fix For: 2.0 > > > Ignite unmarshalls type metadata when accessing it which is an overhead. Need > to fix this for marshaller cache and, probably, for other internal caches > (this needs to be investigated). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-3569) Set copyOnRead property to FALSE for marshaller cache
[ https://issues.apache.org/jira/browse/IGNITE-3569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-3569: Fix Version/s: (was: 1.8) 2.0 > Set copyOnRead property to FALSE for marshaller cache > - > > Key: IGNITE-3569 > URL: https://issues.apache.org/jira/browse/IGNITE-3569 > Project: Ignite > Issue Type: Improvement > Components: cache >Reporter: Yakov Zhdanov >Assignee: Yakov Zhdanov > Fix For: 2.0 > > > Ignite unmarshalls type metadata when accessing it which is an overhead. Need > to fix this for marshaller cache and, probably, for other internal caches > (this needs to be investigated). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2693) withKeepBinary and non-binary marshallers
[
https://issues.apache.org/jira/browse/IGNITE-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-2693:
Fix Version/s: (was: 1.8)
2.0
> withKeepBinary and non-binary marshallers
> -
>
> Key: IGNITE-2693
> URL: https://issues.apache.org/jira/browse/IGNITE-2693
> Project: Ignite
> Issue Type: Bug
> Components: general
>Reporter: Sergey Kozlov
>Assignee: Oddo
> Labels: newbie
> Fix For: 2.0
>
>
> Currently the user is able to set {{.withKeepBinary()}} for any used
> marshaller. But it obviously causes ClassCastException for non-binary
> marshallers and should be available only for binary marshaller.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3386) Reentrant lock is lost when lock owner leaves topology
[
https://issues.apache.org/jira/browse/IGNITE-3386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-3386:
Fix Version/s: (was: 1.8)
2.0
> Reentrant lock is lost when lock owner leaves topology
> --
>
> Key: IGNITE-3386
> URL: https://issues.apache.org/jira/browse/IGNITE-3386
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Denis Magda
>Assignee: Vladisav Jelisavcic
>Priority: Critical
> Labels: important
> Fix For: 2.0
>
> Attachments: LockIssueVer2.java
>
>
> If to create a lock with the following configuration
> {{IgniteLock lock = ignite.reentrantLock("lock", true, true, true);}}
> and perform the following steps below
> 1) run the first node using {{LockIssue}} that is attached;
> 2) run the second node using {{LockIssue}};
> 3) stop the first node.
> you will get the following exception on the second node side (the lock
> information will be lost and the second node won't recreate it ignore
> "create=true" flag):
> {code}
> SEVERE: Failed to compare and set:
> o.a.i.i.processors.datastructures.GridCacheLockImpl$Sync$1@67aea87d
> class org.apache.ignite.IgniteCheckedException: Failed to find reentrant lock
> with given name: test
> at
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl$Sync$1.call(GridCacheLockImpl.java:525)
> at
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl$Sync$1.call(GridCacheLockImpl.java:518)
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils$23.call(GridCacheUtils.java:1648)
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.outTx(GridCacheUtils.java:891)
> at
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl$Sync.compareAndSetGlobalState(GridCacheLockImpl.java:517)
> at
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl$Sync.tryAcquire(GridCacheLockImpl.java:400)
> at
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl$Sync.tryAcquire(GridCacheLockImpl.java:437)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:861)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1197)
> at
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl$Sync.lock(GridCacheLockImpl.java:432)
> at
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl.lock(GridCacheLockImpl.java:1201)
> at
> com.bfm.amc.loaders.server.StartIgniteServer.main(StartIgniteServer.java:15)
> {code}
> However the issue is not 100% reproduced but it should be clear from the logs
> what happens.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3176) Need to create gc log for each client separately [ yardstick-ignite ]
[
https://issues.apache.org/jira/browse/IGNITE-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-3176:
Fix Version/s: (was: 1.8)
2.0
> Need to create gc log for each client separately [ yardstick-ignite ]
> -
>
> Key: IGNITE-3176
> URL: https://issues.apache.org/jira/browse/IGNITE-3176
> Project: Ignite
> Issue Type: Bug
> Components: clients, general
>Affects Versions: 1.6
>Reporter: Ilya Suntsov
>Assignee: Chandresh Pancholi
>Priority: Critical
> Fix For: 2.0
>
> Attachments: benchmark.properties
>
>
> In case when started more than one client/server on one host yardstick
> re-write GC logs.
> GC options contain in *.properties files:
> {noformat}
> now0=`date +'%H%M%S'`
> # JVM options.
> JVM_OPTS=${JVM_OPTS}" -DIGNITE_QUIET=false"
> # Uncomment to enable concurrent garbage collection (GC) if you encounter
> long GC pauses.
> JVM_OPTS=${JVM_OPTS}" \
> -Xloggc:./gc${now0}.log \
> -XX:+PrintGCDetails \
> -verbose:gc \
> -XX:+UseParNewGC \
> -XX:+UseConcMarkSweepGC \
> -XX:+UseTLAB \
> -XX:NewSize=128m \
> -XX:MaxNewSize=128m \
> -XX:MaxTenuringThreshold=0 \
> -XX:SurvivorRatio=1024 \
> -XX:+UseCMSInitiatingOccupancyOnly \
> -XX:CMSInitiatingOccupancyFraction=60 \
> {noformat}
> As you can see here will be created 1 log file and if you start another
> driver/server with the same properties file will be re-write.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2693) withKeepBinary and non-binary marshallers
[
https://issues.apache.org/jira/browse/IGNITE-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15686021#comment-15686021
]
Vladimir Ozerov commented on IGNITE-2693:
-
Got lots of failures. Moving to the next release.
> withKeepBinary and non-binary marshallers
> -
>
> Key: IGNITE-2693
> URL: https://issues.apache.org/jira/browse/IGNITE-2693
> Project: Ignite
> Issue Type: Bug
> Components: general
>Reporter: Sergey Kozlov
>Assignee: Oddo
> Labels: newbie
> Fix For: 1.8
>
>
> Currently the user is able to set {{.withKeepBinary()}} for any used
> marshaller. But it obviously causes ClassCastException for non-binary
> marshallers and should be available only for binary marshaller.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
