June 2015 - overlord-issues - Jboss List Archives

[JBoss JIRA] (ARTIF-725) Use new 'expandedFromArchivePath' field, rather than custom property

by Brett Meyer (JIRA)

Brett Meyer created ARTIF-725: --------------------------------- Summary: Use new 'expandedFromArchivePath' field, rather than custom property Key: ARTIF-725 URL: https://issues.jboss.org/browse/ARTIF-725 Project: Artificer Issue Type: Enhancement Affects Versions: 1.0.0.Beta1 Reporter: Brett Meyer Assignee: Brett Meyer Fix For: 1.0.0.Beta2 Currently, if an artifact is expanded, it populates a 'expanded.from.archive.path' custom property. Instead, move this to a new field on the Artifact itself. Note that, for now, this will need to be bound to an expansion entry. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-724) Creation timestamp not always persisted

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-724?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on ARTIF-724: ----------------------------------- Although we should guarantee it's persisted, also check for nulls in QueryResultSet (just in case). > Creation timestamp not always persisted > --------------------------------------- > > Key: ARTIF-724 > URL: https://issues.jboss.org/browse/ARTIF-724 > Project: Artificer > Issue Type: Bug > Affects Versions: 1.0.0.Beta1 > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Beta2 > > > To reproduce: > 1.) Upload the Artificer distro zip > 2.) click on wstx-wsba-1.1-wsdl-200702.wsdl > 3.) stack: > ... > Caused by: java.lang.NullPointerException > at java.util.Calendar.setTime(Calendar.java:1770) > at org.artificer.client.query.QueryResultSet.summary(QueryResultSet.java:176) > at org.artificer.client.query.QueryResultSet.access$000(QueryResultSet.java:34) > at org.artificer.client.query.QueryResultSet$DelegatingIterator.next(QueryResultSet.java:153) > at org.artificer.client.query.QueryResultSet$DelegatingIterator.next(QueryResultSet.java:128) > at org.artificer.ui.server.services.util.RelationshipResolver.resolveAll(RelationshipResolver.java:86) > ... 45 more -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-724) Creation timestamp not always persisted

by Brett Meyer (JIRA)

Brett Meyer created ARTIF-724: --------------------------------- Summary: Creation timestamp not always persisted Key: ARTIF-724 URL: https://issues.jboss.org/browse/ARTIF-724 Project: Artificer Issue Type: Bug Affects Versions: 1.0.0.Beta1 Reporter: Brett Meyer Assignee: Brett Meyer Fix For: 1.0.0.Beta2 To reproduce: 1.) Upload the Artificer distro zip 2.) click on wstx-wsba-1.1-wsdl-200702.wsdl 3.) stack: ... Caused by: java.lang.NullPointerException at java.util.Calendar.setTime(Calendar.java:1770) at org.artificer.client.query.QueryResultSet.summary(QueryResultSet.java:176) at org.artificer.client.query.QueryResultSet.access$000(QueryResultSet.java:34) at org.artificer.client.query.QueryResultSet$DelegatingIterator.next(QueryResultSet.java:153) at org.artificer.client.query.QueryResultSet$DelegatingIterator.next(QueryResultSet.java:128) at org.artificer.ui.server.services.util.RelationshipResolver.resolveAll(RelationshipResolver.java:86) ... 45 more -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-723) Web UI upload status never completes for large files

by Brett Meyer (JIRA)

Brett Meyer created ARTIF-723: --------------------------------- Summary: Web UI upload status never completes for large files Key: ARTIF-723 URL: https://issues.jboss.org/browse/ARTIF-723 Project: Artificer Issue Type: Bug Affects Versions: 1.0.0.Beta1 Reporter: Brett Meyer Assignee: Brett Meyer Fix For: 1.0.0.Beta2 Upload a large distro (example, the actual Artificer distro ZIP). It's expanded and processed correctly, but the upload status never completes. Timeout? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-700) Minor UI fixes for 1.0.0

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-700?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved ARTIF-700. ------------------------------- Resolution: Done > Minor UI fixes for 1.0.0 > ------------------------ > > Key: ARTIF-700 > URL: https://issues.jboss.org/browse/ARTIF-700 > Project: Artificer > Issue Type: Enhancement > Affects Versions: 1.0.0.Beta1 > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Beta2 > > > - the source text box can be taller now that Overview is a separate tab > - the login theme looks "weird" and isn't spaced out properly -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-700) Minor UI fixes for 1.0.0

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-700?page=com.atlassian.jira.plugin.... ] Work on ARTIF-700 started by Brett Meyer. ----------------------------------------- > Minor UI fixes for 1.0.0 > ------------------------ > > Key: ARTIF-700 > URL: https://issues.jboss.org/browse/ARTIF-700 > Project: Artificer > Issue Type: Enhancement > Affects Versions: 1.0.0.Beta1 > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Beta2 > > > - the source text box can be taller now that Overview is a separate tab > - the login theme looks "weird" and isn't spaced out properly -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-722) Solely use Hibernate Search if query is limited to full-text search and indexed columns

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-722?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on ARTIF-722: ----------------------------------- WIP: https://github.com/ArtificerRepo/artificer/compare/master...brmeyer:ARTIF... If we go this route, it will have to wait until we no longer support EAP 6 (or can upgrade to Hibernate 4.3.x). The DelayedPredicate concept relies on SPI that changed between 4.2/4.3. There may be a better way to do it, but... Realistically, I'm not sure how useful this is. With proper indexing at the DB level, the queries tend to be fast anyway. Users will also almost always be using paging, further reducing the necessity for this level of improvement. Re-visit sometime in the future. > Solely use Hibernate Search if query is limited to full-text search and indexed columns > --------------------------------------------------------------------------------------- > > Key: ARTIF-722 > URL: https://issues.jboss.org/browse/ARTIF-722 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > > Now that queries return a summary DTO, if a query only contains full-text search and columns indexed by Lucene, Hibernate Search can be solely used. There is no need to also execute the SQL query. For example: > /s-ramp/xsd/XsdDocument[xp2:matches(., 'FizzBuzz')] > Since 'model' and 'type' are both indexed, this could be accomplished entirely with the Lucene query, skipping SQL. > This idea implies that all properties included in ArtifactSummary would need to be indexed as well. SQL would be needed only when custom properties, ontologies, or relationships are required. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-722) Solely use Hibernate Search if query is limited to full-text search and indexed columns

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-722?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-722: ------------------------------ Parent: (was: ARTIF-711) Issue Type: Feature Request (was: Sub-task) > Solely use Hibernate Search if query is limited to full-text search and indexed columns > --------------------------------------------------------------------------------------- > > Key: ARTIF-722 > URL: https://issues.jboss.org/browse/ARTIF-722 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Beta2 > > > Now that queries return a summary DTO, if a query only contains full-text search and columns indexed by Lucene, Hibernate Search can be solely used. There is no need to also execute the SQL query. For example: > /s-ramp/xsd/XsdDocument[xp2:matches(., 'FizzBuzz')] > Since 'model' and 'type' are both indexed, this could be accomplished entirely with the Lucene query, skipping SQL. > This idea implies that all properties included in ArtifactSummary would need to be indexed as well. SQL would be needed only when custom properties, ontologies, or relationships are required. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-722) Solely use Hibernate Search if query is limited to full-text search and indexed columns

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-722?page=com.atlassian.jira.plugin.... ] Work on ARTIF-722 stopped by Brett Meyer. ----------------------------------------- > Solely use Hibernate Search if query is limited to full-text search and indexed columns > --------------------------------------------------------------------------------------- > > Key: ARTIF-722 > URL: https://issues.jboss.org/browse/ARTIF-722 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > > Now that queries return a summary DTO, if a query only contains full-text search and columns indexed by Lucene, Hibernate Search can be solely used. There is no need to also execute the SQL query. For example: > /s-ramp/xsd/XsdDocument[xp2:matches(., 'FizzBuzz')] > Since 'model' and 'type' are both indexed, this could be accomplished entirely with the Lucene query, skipping SQL. > This idea implies that all properties included in ArtifactSummary would need to be indexed as well. SQL would be needed only when custom properties, ontologies, or relationships are required. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-722) Solely use Hibernate Search if query is limited to full-text search and indexed columns

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-722?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-722: ------------------------------ Fix Version/s: (was: 1.0.0.Beta2) > Solely use Hibernate Search if query is limited to full-text search and indexed columns > --------------------------------------------------------------------------------------- > > Key: ARTIF-722 > URL: https://issues.jboss.org/browse/ARTIF-722 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > > Now that queries return a summary DTO, if a query only contains full-text search and columns indexed by Lucene, Hibernate Search can be solely used. There is no need to also execute the SQL query. For example: > /s-ramp/xsd/XsdDocument[xp2:matches(., 'FizzBuzz')] > Since 'model' and 'type' are both indexed, this could be accomplished entirely with the Lucene query, skipping SQL. > This idea implies that all properties included in ArtifactSummary would need to be indexed as well. SQL would be needed only when custom properties, ontologies, or relationships are required. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues June 2015