ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Konstantinov (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (IGNITE-32) Need to create a utility for auto-schema loading from databases
Date Sun, 08 Feb 2015 05:47:34 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Pavel Konstantinov reopened IGNITE-32:
--------------------------------------
      Assignee: Alexey Kuznetsov  (was: Pavel Konstantinov)

1. Need to fix a little typo in the CP set - add '*' to the end (%IGNITE_HOME%\bin\include\schema-load\*)
2. Warning on SchemaLoad start:
{code}
S:\work\ignite-fabric-1.0.0-SNAPSHOT\bin>ignite-schema-load.bat
Їхт 08, 2015 1:43:34 PM java.util.prefs.WindowsPreferences <init>
WARNING: Could not open/create prefs root node Software\JavaSoft\Prefs at root 0x80000002.
Windows RegCreateKeyEx(...) returned error code 5.
{code}


> Need to create a utility for auto-schema loading from databases
> ---------------------------------------------------------------
>
>                 Key: IGNITE-32
>                 URL: https://issues.apache.org/jira/browse/IGNITE-32
>             Project: Ignite
>          Issue Type: Task
>          Components: UI
>            Reporter: Dmitriy Setrakyan
>            Assignee: Alexey Kuznetsov
>            Priority: Critical
>             Fix For: sprint-1
>
>         Attachments: ignite-32-01.png, ignite-32-02.png, ignite-32-03.png, ignite-32-04.png,
ignite_patch.diff
>
>
> Need to create utility for auto-schema loading:
> # Should be written in Java
> # Preferably no additional dependencies should be added to the project. 
> The process is composed of 2 parts, schema mapping and automatic data loading.
> h3. Schema Mapping
> # Should be a standalone GUI utility
> # Users should select schemas, then tables from schemas, then fields from tables, and
automatically generate Spring XML for SQL Query metadata configuration.
> # Should also optionally automatically generate POJO classes.
> # Should automatically map SQL table names to Java standard allowing users to provide
customer Regex.
> # By default, every  table should be mapped to a separate Cache, but user should be able
to override this in any possible way.
> h3. Automatic {{GridCacheStore}} implementation
> # The new {{GridCacheStore}} implementation should read the XML configuration generated
by *Schema Mapping* step and automatically implement all CRUD and TX operations out of the
box.
> # The implementation of the {{loadCache(...)}} method should accept SQL for loading (or
where clause) as a parameter. Users should be able to preload a portion of the table based
on some search criteria on startup or at any point after.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message