Hi:
I understand your approach, it should be feasible, but not very elegant.
If use ProxyFactory in spring. At runtime dynamically add interceptor,
can solve the problem, but performance will influence.
I switched to a different way of writing, using the Service mechanism,
code has been
Vasiliy Sisko created IGNITE-2424:
-
Summary: Incorect char column selection in specific case.
Key: IGNITE-2424
URL: https://issues.apache.org/jira/browse/IGNITE-2424
Project: Ignite
Issue
Artem,
My suggestion was that instead of having 3 id mappers that do almost the
same thing, have 1 ID mapper with additional configuration properties.
BTW, I still don’t get what a straight ID mapper means.
D.
On Wed, Jan 20, 2016 at 9:45 AM, Artem Shutak wrote:
>
Pavel Konstantinov created IGNITE-2423:
--
Summary: We should correctly handle a case when DB has several
shemas with the tables with te same name
Key: IGNITE-2423
URL:
Hi:
I in a very old machine simple to do the test, if open reserv mechanism,
the ID generation speed can reach 50K/s. If turn off reserv mechanism,
the performance will be dropped to 13K/s, performance degradation is
very obvious, but off reserv will enable ID increase linearly with
time,
On Wed, Jan 20, 2016 at 10:59 PM, 李玉珏 <18624049...@163.com> wrote:
> Hi:
>
> I in a very old machine simple to do the test, if open reserv mechanism,
> the ID generation speed can reach 50K/s. If turn off reserv mechanism,
> the performance will be dropped to 13K/s, performance degradation is
>
Edouard Chevalier created IGNITE-2419:
-
Summary: Ignite on YARN do not handle memory overhead
Key: IGNITE-2419
URL: https://issues.apache.org/jira/browse/IGNITE-2419
Project: Ignite
Hi all,
I'm Edouard Chevalier and I would like to contribute to the Apache
Ignite project.
I have read some of the guides on "how to contribute". If you agree I
can start with a proposal on the JIRA I have just created
(https://issues.apache.org/jira/browse/IGNITE-2419) and then go on any
Vladimir Ershov created IGNITE-2420:
---
Summary: [Test] Ignite AWS lacks amazon credentials.
Key: IGNITE-2420
URL: https://issues.apache.org/jira/browse/IGNITE-2420
Project: Ignite
Issue
Looks too busy.
Why not just have one ID mapper with config properties, like
isSimpleName(), isLowerCase()?
Also, what is a straight ID mapper?
D.
On Wed, Jan 20, 2016 at 4:01 AM, Artem Shutak wrote:
> Dmitriy, thanks for reminding me about this thread.
>
> According to
Hi Edouard!
I think it useful future and don't see any reason why you can't implement
this task. Feel free to ask if you have questions.
On Wed, Jan 20, 2016 at 6:08 PM, Edouard Chevalier <
edouard.cheval...@techmydata.net> wrote:
> Hi all,
>
> I'm Edouard Chevalier and I would like to
Hi Edouard.
Welcome to the Ignite community!
I have added you to the list of the Ignite contributors in Jira and
assigned the ticket to you. In the mean time, I have asked Vladimir to
comment on it, to see if he has anything to add.
Looking forward to your contribution.
D.
On Wed, Jan 20,
Denis Magda created IGNITE-2422:
---
Summary: Prevent serialization of BinaryObjectBuilder
Key: IGNITE-2422
URL: https://issues.apache.org/jira/browse/IGNITE-2422
Project: Ignite
Issue Type: Bug
Dmitriy,
BinaryStraightIdMapper - calculate hash code for given strings (do not
change given string and call hashCode() for it). It's simplest IdMapper. It
would be nice if we will have it out-of-the-box.
Could you please describe your approach in more details? Keep in mind, that
BinaryIdMapper
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/383
---
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
Updated the docs. Thanks for pointing out.
On 1/16/2016 12:19 PM, 李玉珏@163 wrote:
Hi:
In the 1.5.0 version, I found that CacheTypeMetadata was abandoned and
replaced by QueryEntity.
I find that two classes of related instructions exist in the manual:
Github user Dmitriyff closed the pull request at:
https://github.com/apache/ignite/pull/211
---
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
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/412
IGNITE-2414 .NET: TestWithExpiryPolicy fails
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite ignite-2414
Alternatively you
Denis Magda created IGNITE-2415:
---
Summary: Add an example of usage for CacheLoadOnlyStoreAdapter
Key: IGNITE-2415
URL: https://issues.apache.org/jira/browse/IGNITE-2415
Project: Ignite
Issue
Github user Dmitriyff closed the pull request at:
https://github.com/apache/ignite/pull/366
---
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
Github user Dmitriyff closed the pull request at:
https://github.com/apache/ignite/pull/306
---
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
Github user Dmitriyff closed the pull request at:
https://github.com/apache/ignite/pull/328
---
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
Github user Dmitriyff closed the pull request at:
https://github.com/apache/ignite/pull/199
---
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
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/413
IGNITE-2410 Fix JVM crash in DestroyCache
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite ignite-2410
Alternatively you can
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/413
---
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
Pavel Tupitsyn created IGNITE-2417:
--
Summary: peerClassLoading causes high memory usage on simple cache
operations
Key: IGNITE-2417
URL: https://issues.apache.org/jira/browse/IGNITE-2417
Project:
Hi!
I've checked your code and spot an issue. The root cause, is using of
Autowired annotation, since it cause bean to be serialized on a client
side, and that leads ClassNotFoundException on the server side during bean
deserialization, since server was started from *.sh, without necessary
spring
Sergey Kozlov created IGNITE-2418:
-
Summary: Combine .Net example configuration files into one like
for Java examples
Key: IGNITE-2418
URL: https://issues.apache.org/jira/browse/IGNITE-2418
Project:
28 matches
Mail list logo