Alexey Kuznetsov created IGNITE-1807:
Summary: Visor console should write logs to file in quite mode
Key: IGNITE-1807
URL: https://issues.apache.org/jira/browse/IGNITE-1807
Project: Ignite
On Wed, Oct 28, 2015 at 8:12 AM, Vladimir Ozerov
wrote:
> I do not like idea of predefined alogrithms, because we will lack
> flexibility. What if user has backing Java/.Net class where hash code is
> calculated differently? What if user *cannot change* this class for some
> reason?
> Any hard-co
On Wed, Oct 28, 2015 at 9:23 PM, Alexey Kuznetsov
wrote:
> Prachi,
>
> From my experience users usually like to click "Next -> Next -> Next ->
> OK".
> I don't think it is a good idea to force user to see error message "No
> tables selected" if he/she just clicks as described above.
> Does it mak
Prachi,
>From my experience users usually like to click "Next -> Next -> Next -> OK".
I don't think it is a good idea to force user to see error message "No
tables selected" if he/she just clicks as described above.
Does it make sense for you?
On Thu, Oct 29, 2015 at 10:14 AM, Prachi Garg wrote:
Vasiliy Sisko created IGNITE-1806:
-
Summary: Rework UI and code generation to new query configuration
Key: IGNITE-1806
URL: https://issues.apache.org/jira/browse/IGNITE-1806
Project: Ignite
I
I see. What about the tables being selected? Can we have them cleared when the
popup launches?
-P
> On Oct 28, 2015, at 7:49 PM, Alexey Kuznetsov wrote:
>
> Prach,
>
> Thanks for typos. I fixed them.
>
> Let's discuss issue about load metadata popup.
>
> I have a lot of experience with da
Prach,
Thanks for typos. I fixed them.
Let's discuss issue about load metadata popup.
I have a lot of experience with databases admin tools and it was very
painful
when some tool does not save settings that I entered in previous session.
So, I implemented saving previous values in metadata po
Hey guys,
When I try to load metadata from the database, the fields in the popup
contain values that were previously used to load the metadata. For example,
the JDBC url and username fields already have values I had entered
previously, and the tables previously selected for loading the metadata ar
Prachi Garg created IGNITE-1805:
---
Summary: Implement 'Reset' button for 'Load metadata from
database' popup
Key: IGNITE-1805
URL: https://issues.apache.org/jira/browse/IGNITE-1805
Project: Ignite
I do not like idea of predefined alogrithms, because we will lack
flexibility. What if user has backing Java/.Net class where hash code is
calculated differently? What if user *cannot change* this class for some
reason?
Any hard-coded hash code algorithm looks like a shortcut for me.
Moreover, has
Vladimir Ozerov created IGNITE-1803:
---
Summary: Optimize random portable field lookup.
Key: IGNITE-1803
URL: https://issues.apache.org/jira/browse/IGNITE-1803
Project: Ignite
Issue Type: Tas
Igniters,
After some thinking on hash code generation for portables and POJO store we
could do the following:
1) As Dmitriy suggested in [1] a boolean flag "isHashCode" to
JdbcTypeField. If true then this field will be used for hash code
calculation by pojo store.
2) Add to all PortableBuilder.se
Artem Shutak created IGNITE-1802:
Summary: Ignite.countDownLatch() can return null if latch has been
already created.
Key: IGNITE-1802
URL: https://issues.apache.org/jira/browse/IGNITE-1802
Project: I
Pavel Konstantinov created IGNITE-1801:
--
Summary: Warning message printing out in wrong place
Key: IGNITE-1801
URL: https://issues.apache.org/jira/browse/IGNITE-1801
Project: Ignite
Issu
GitHub user agura opened a pull request:
https://github.com/apache/ignite/pull/180
ignite-1717 Portable marshaller fixed for cases when serialization proxy
should be serialized by optimized marshaller
You can merge this pull request into a Git repository by running:
$ git pul
Github user agura closed the pull request at:
https://github.com/apache/ignite/pull/169
---
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 enabl
Hello all,
I've regrouped Ignite streamer modules in TeamCity into the existing Ignite
Streamers build configuration. Thus, the separate Ignite JMS and Ignite
MQTT have disappeared.
I faced some troubles with the ActiveMQ KahaDB file locks in TeamCity,
hence my commits today in that module, as I
Hello,
I've pushed a new Apache Camel streamer in the ignite-1790 branch.
Build and tests ran successfully on TC (Ignite Streamers build config).
Could someone please review it before I merge it into master?
Thanks,
*Raúl Kripalani*
PMC & Committer @ Apache Ignite, Apache Camel | Integration,
Artem Shutak created IGNITE-1800:
Summary: Annotation MBeanServerResource should be deleted as
unsupported.
Key: IGNITE-1800
URL: https://issues.apache.org/jira/browse/IGNITE-1800
Project: Ignite
19 matches
Mail list logo
