March 2015 - overlord-issues - Jboss List Archives

[JBoss JIRA] (ARTIF-260) Free Text Search for artifacts Enhancement

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-260?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-260: ------------------------------ Fix Version/s: (was: 1.0.0.Alpha1) > Free Text Search for artifacts Enhancement > ------------------------------------------ > > Key: ARTIF-260 > URL: https://issues.jboss.org/browse/ARTIF-260 > Project: Artificer > Issue Type: Feature Request > Components: Client > Environment: N/A > Reporter: Cojan van Ballegooijen > Assignee: Brett Meyer > > The search field in Repository -> Artifacts of the S-RAMP UI web application looks like a free text search field. > One need to use the S-RAMP Query language. > https://github.com/Governance/s-ramp/wiki/GuideSrampQueryLanguage > Would be nice to have a free text search capability to search for artifacts. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-659) Test and support Java 8

by Brett Meyer (JIRA)

Brett Meyer created ARTIF-659: --------------------------------- Summary: Test and support Java 8 Key: ARTIF-659 URL: https://issues.jboss.org/browse/ARTIF-659 Project: Artificer Issue Type: Task Reporter: Brett Meyer Assignee: Brett Meyer -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-658) Upgrade to ModeShape 4.2.0

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-658?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-658: ------------------------------ Fix Version/s: (was: 1.0.0.Alpha1) > Upgrade to ModeShape 4.2.0 > -------------------------- > > Key: ARTIF-658 > URL: https://issues.jboss.org/browse/ARTIF-658 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-658) Upgrade to ModeShape 4.2.0

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-658?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on ARTIF-658: ----------------------------------- On hold. The WF8 distro is only available in MS 4.0. Check on 4.2 plans. > Upgrade to ModeShape 4.2.0 > -------------------------- > > Key: ARTIF-658 > URL: https://issues.jboss.org/browse/ARTIF-658 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-658) Upgrade to ModeShape 4.2.0

by Brett Meyer (JIRA)

Brett Meyer created ARTIF-658: --------------------------------- Summary: Upgrade to ModeShape 4.2.0 Key: ARTIF-658 URL: https://issues.jboss.org/browse/ARTIF-658 Project: Artificer Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer Fix For: 1.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-260) Free Text Search for artifacts Enhancement

by Randall Hauch (JIRA)

[ https://issues.jboss.org/browse/ARTIF-260?page=com.atlassian.jira.plugin.... ] Randall Hauch commented on ARTIF-260: ------------------------------------- I agree that full-text search performance is currently an issue with MS 4.x. Someone in the ModeShape community is working on a Lucene index provider, so you could ask and collaborate. We sure could use the help. > Free Text Search for artifacts Enhancement > ------------------------------------------ > > Key: ARTIF-260 > URL: https://issues.jboss.org/browse/ARTIF-260 > Project: Artificer > Issue Type: Feature Request > Components: Client > Environment: N/A > Reporter: Cojan van Ballegooijen > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > The search field in Repository -> Artifacts of the S-RAMP UI web application looks like a free text search field. > One need to use the S-RAMP Query language. > https://github.com/Governance/s-ramp/wiki/GuideSrampQueryLanguage > Would be nice to have a free text search capability to search for artifacts. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-260) Free Text Search for artifacts Enhancement

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-260?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-260: ------------------------------ Fix Version/s: 1.0.0.Alpha1 > Free Text Search for artifacts Enhancement > ------------------------------------------ > > Key: ARTIF-260 > URL: https://issues.jboss.org/browse/ARTIF-260 > Project: Artificer > Issue Type: Feature Request > Components: Client > Environment: N/A > Reporter: Cojan van Ballegooijen > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > The search field in Repository -> Artifacts of the S-RAMP UI web application looks like a free text search field. > One need to use the S-RAMP Query language. > https://github.com/Governance/s-ramp/wiki/GuideSrampQueryLanguage > Would be nice to have a free text search capability to search for artifacts. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-260) Free Text Search for artifacts Enhancement

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-260?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on ARTIF-260: ----------------------------------- [~rhauch], any thoughts/caveats on this? We're interested in full-text search, both for node properties as well as file content. But, concerned about scalability, as we have a few Artificer uses on the table that involve 10+ million primary artifacts, the bulk of which would have binary content. 1.) Am I correct that MS 4 does not currently support a query index on the file content itself? 2.) Would we be better off using a combination of MS full-text queries on metadata, then an external Lucene/ElasticSearch instance on the file contents (we use the filesystem for binary storage)? Would we be able to use the file's binary storage pathname (looks to be a UUID) to then lookup the associated nodes that reference it? > Free Text Search for artifacts Enhancement > ------------------------------------------ > > Key: ARTIF-260 > URL: https://issues.jboss.org/browse/ARTIF-260 > Project: Artificer > Issue Type: Feature Request > Components: Client > Environment: N/A > Reporter: Cojan van Ballegooijen > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > The search field in Repository -> Artifacts of the S-RAMP UI web application looks like a free text search field. > One need to use the S-RAMP Query language. > https://github.com/Governance/s-ramp/wiki/GuideSrampQueryLanguage > Would be nice to have a free text search capability to search for artifacts. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-575) Support stored query templates/parameter-substitution

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-575?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-575: ------------------------------ Fix Version/s: (was: 1.0.0.Alpha1) > Support stored query templates/parameter-substitution > ----------------------------------------------------- > > Key: ARTIF-575 > URL: https://issues.jboss.org/browse/ARTIF-575 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > From the Atom Binding spec, 3.3.1: > {quote} > Stored Query Entry documents MAY also be used as templates, allowing simple substitution of client specified parameter values during execution. The syntax for parameter substitution follows the XPath2 style to represent a variable within the query filter: > > $\{var-name\} > > A value for the var-name can then be specified as part of the query invocation. Default values are not supported. > {quote} > {code}s-ramp/serviceImplementation/ServiceInstance[@version >= ${MINVERSION}]>{code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-657) updateContent may not be recreating relationships correctly

by Brett Meyer (JIRA)

Brett Meyer created ARTIF-657: --------------------------------- Summary: updateContent may not be recreating relationships correctly Key: ARTIF-657 URL: https://issues.jboss.org/browse/ARTIF-657 Project: Artificer Issue Type: Bug Reporter: Brett Meyer Assignee: Brett Meyer In the middle of ImpactAnalysisDemo, after all artifacts and relationships have been created, run updateContent on the XSD, using the same .xsd file. The demo will still run successfully. But when finished, pull up the UI and hit one of the Part 'parameter" artifacts, then hit their Relationship tab. It fails, most likely because the relationship wasn't re-created. Not sure how to handle that. Should the relationships really be re-generated? If so, what happens if, for example, a WSDL Part uses a type that's been modified or removed? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues March 2015