[MAGNOLIA-340] core.search package, extend QueryResult and fix NodeData Created: 21/Apr/05 Updated: 11/Mar/08 Resolved: 27/Apr/05 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 2.1 Final |
| Fix Version/s: | 2.1 Final |
| Type: | Task | Priority: | Blocker |
| Reporter: | Sameer Charles | Assignee: | Sameer Charles |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Date of First Response: |
| Description |
|
magnolia NodeData is stored as nt:file type in jcr, that worked quite well but its a problem with simple SQL queries
|
| Comments |
| Comment by Sameer Charles [ 22/Apr/05 ] |
|
next steps : 1. refactor NodeData class so its no longer content type mgnl:nodeData but a simple jcr property
2. ContentNode will be depricated since it does not make sence to have wraper classes for nodes when we have a 3. Define QueryResult interface, implement core.search package 4. Refoctoring all effected classes. I am working on it, expecting to finish early next week. ll update bootstrap and new node type definitions once tested. Devs : please let me know if someone else also working on magnolia.core package, if yes ll wait unitil you finish. |
| Comment by Sameer Charles [ 25/Apr/05 ] |
|
just commited few changes on svn http://svn.magnolia.info/svn/magnolia/trunk/src/main/info/magnolia/cms/core/* Note : you will see all jcr system properties in tree view, I am working on it to filter. you can see the performance difference on persisting data, its 10x faster also for activation Next task : keep you posted |
| Comment by Fabrizio Giustina [ 25/Apr/05 ] |
|
Well done Sameer, looks a lot faster and simpler now... just a few comments:
|
| Comment by Sameer Charles [ 25/Apr/05 ] |
|
updated/tested search QueryResult --------
yeah my mistake, will do so. -------- Next Steps : |
| Comment by Sameer Charles [ 25/Apr/05 ] |
|
website.features.xml updated |
| Comment by Fabrizio Giustina [ 25/Apr/05 ] |
|
tested, everything works for me and bootstrap is faster than before. There is something wrong with export/import of binary properties however, don't know if this is a problem of magnolia or a jackrabbit... could you give it a look? |
| Comment by Sameer Charles [ 25/Apr/05 ] |
|
hmmm its a same problem with all other types, XML export does not maintain data type information ! strange seems like on document view import it uses "PropertyDefinition" as defined in NodeType definition to determine the data type of a property, and since magnolia nodetype definition defines a generic property "*" it does not know how to handle this. I am not sure if its a jackrabbit problem or magnolia |
| Comment by Sameer Charles [ 26/Apr/05 ] |
|
its a problem with jackrabbit, since jcr does not define any structure for xml export its open for the implementation. snippet from the specs---- "" |
| Comment by Sameer Charles [ 26/Apr/05 ] |
|
" |
| Comment by Sameer Charles [ 26/Apr/05 ] |
|
Returns the type of this Property. The type returned |
| Comment by Fabrizio Giustina [ 26/Apr/05 ] |
|
reported to jackrabbit |
| Comment by Fabrizio Giustina [ 26/Apr/05 ] |
|
see comments on http://issues.apache.org/jira/browse/JCR-115 |
| Comment by Sameer Charles [ 26/Apr/05 ] |
|
great!! opened new JIRA issue http://jira.magnolia.info/browse/MAGNOLIA-351 |
| Comment by Sameer Charles [ 27/Apr/05 ] |