Hi Roman,
Do you mean that key expiration is not supported in Ignite? If so, then
this is not true, see the last example here:
https://apacheignite.readme.io/docs/expiry-policies
-Val
On Fri, Nov 18, 2016 at 7:55 PM, Roman Shtykh
wrote:
> Dmitriy,
> I think additions of some operations on sets
Dmitriy,
I think additions of some operations on sets and hashes are pretty
straightforward.
But I think we need to extend REST implementation to cover even more Redis
commands (it won't probably remove all limitations we have now though, like not
having expiration on keys), or create a Redis pr
Well,
The example still fails in the multi-node mode
(SpatialQueryExampleMultiNodeSelfTest) which means that a similar filtering,
that is applied in the patch from the previous message, has to be done in some
other place. Unfortunately, I can’t keep at investigating the issue at the
moment any
Alexandr,
This has been tested many times already by our users and the answer is
simple - it depends :) Any approach has its pros and cons and you never
know which one will better for particular use case, database, data model,
hardware, etc.
Having said that, you will never find the best way to l
Valentin Kulichenko created IGNITE-4250:
---
Summary: Add Ignition.getOrStart method that starts from Spring
XML file
Key: IGNITE-4250
URL: https://issues.apache.org/jira/browse/IGNITE-4250
Project
Andrey,Ok, now I see why the functionality has been broken. Basically, to fix the issue we should avoid the conversion of all “com.vividsolutions.jts” parameters to the binary form. Please see in attach a possible fix. It would be more elegant to register the geospatial classes in BinaryContext but
Igor Sapego created IGNITE-4249:
---
Summary: 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
Valentin Kulichenko created IGNITE-4248:
---
Summary: Slf4jLogger ignores IGNITE_QUIET system property
Key: IGNITE-4248
URL: https://issues.apache.org/jira/browse/IGNITE-4248
Project: Ignite
Query parameters are converted to binary since commit "ae77653". This is
result of IGNITE-2208[1].
However, spatial queries work fine with OptimizedMarshaller configured. We
already have test GridH2IndexingGeoSelfTest, and we can run it with
BinaryMarshaller as well.
[1] https://issues.apache.or
Valentin Kulichenko created IGNITE-4247:
---
Summary: Table aliases not supported for SqlQuery
Key: IGNITE-4247
URL: https://issues.apache.org/jira/browse/IGNITE-4247
Project: Ignite
Issue
Folks,
Is there anyone who understands the purpose of including ignite-spark
module in the Hadoop Accelerator build? I can't figure out a use case for
which it's needed.
In case we actually need it there, there is an issue then. We actually have
two ignite-spark modules, for 2.10 and 2.11. In Fab
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1249
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is ena
2. Most likely we don’t need to convert the spatial objects into the binary
form.
I would investigate what has changed since the recent release where everything
worked fine. Also don’t forget to add a test for the broken functionality.
—
Denis
> On Nov 18, 2016, at 8:54 AM, Sergi Vladykin wro
1. The change itself is buggy because if the parameter is null, then we
will call setNull and setObject after that. It must be `else if ...`
2. I'm not sure how this deserialization fits to our "no classes on server"
ideology.
Sergi
2016-11-18 14:26 GMT+03:00 Andrey Mashenkov :
> Hi Denis,
>
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/1249
IGNITE-4246 .NET: Fix IgniteDbConfiguration initialization
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite ignite-4246
Alte
Dmitriy,
I will not be fully confident that partition ID is the best approach in all
cases. Even if we have full access to the database structure, there are
another problems.
Assume we have a table PERSON (ID NUMBER, NAME VARCHAR, SURNAME VARCHAR,
AGE NUMBER, EMPL_DATE DATE). And we add our colum
Pavel Tupitsyn created IGNITE-4246:
--
Summary: .NET: IgniteDbConfiguration initializes incorrectly
Key: IGNITE-4246
URL: https://issues.apache.org/jira/browse/IGNITE-4246
Project: Ignite
Issu
Alexandr Kuramshin created IGNITE-4245:
--
Summary: Get EXCEPTION_ACCESS_VIOLATION with OFFHEAP_TIRED cache
Key: IGNITE-4245
URL: https://issues.apache.org/jira/browse/IGNITE-4245
Project: Ignite
Hi Denis,
Sql query parameters have being converted to binary before query is sent to
QueryProcessor. But they haven't being deserialized by QueryProcessor on
binding.
So, H2 failed to execute query due to wrong parameter type.
I've added PR [1] with fix. Sergi, please review if it correct place
Andrey,
I found a problem in INCR/DECR implementation.I think I misunderstood how it
works in the current memcached/rest implementation of Ignite, but I modified
Redis INCR/DECR now to behave the same way as memcached/rest.
Can you please have a look at https://issues.apache.org/jira/browse/IGNIT
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/1248
IGNITE-4238: example spatial queries fails
Fixed: deserialize binary sql arguments before binding
You can merge this pull request into a Git repository by running:
$ git pull https://github
GitHub user shroman opened a pull request:
https://github.com/apache/ignite/pull/1247
IGNITE-4244: INCR/DECR to operate on AtomicLong.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/shroman/ignite ignite-4244
Alternatively you
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1234
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is ena
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1245
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is ena
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1246
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is ena
Thanks, Roman! I looked at the content and it looks OK.
Are we going to be adding more Redis commands? If yes, would be nice if we
would mention which commands we plan to add in the nearest future.
D.
On Fri, Nov 18, 2016 at 4:23 AM, Roman Shtykh
wrote:
> Dmitriy,
> I have contents prepared fo
Roman Shtykh created IGNITE-4244:
Summary: Redis INCR/DECR should be able to operate on strings
Key: IGNITE-4244
URL: https://issues.apache.org/jira/browse/IGNITE-4244
Project: Ignite
Issue T
27 matches
Mail list logo
