[JBoss JIRA] (WFLY-4123) Provide a 'map_reduce' operation to execute domain wide queries on the server side
by Heiko Braun (JIRA)
[ https://issues.jboss.org/browse/WFLY-4123?page=com.atlassian.jira.plugin.... ]
Heiko Braun updated WFLY-4123:
------------------------------
Summary: Provide a 'map_reduce' operation to execute domain wide queries on the server side (was: Provide a top-level 'map' operation to execute domain wide queries on the server side)
> Provide a 'map_reduce' operation to execute domain wide queries on the server side
> ----------------------------------------------------------------------------------
>
> Key: WFLY-4123
> URL: https://issues.jboss.org/browse/WFLY-4123
> Project: WildFly
> Issue Type: Feature Request
> Reporter: Heiko Braun
> Assignee: Heiko Braun
> Fix For: 9.0.0.Beta1
>
>
> See https://github.com/hpehl/map-reduce
> {code:java}
> ModelNode address = new ModelNode();
> address.add("profile", "*")
> .add("subsystem", "datasources")
> .add("data-source", "*");
> ModelNode filter = new ModelNode();
> filter.add("driver-name", "h2")
> .add("enabled", true);
> ModelNode op = new ModelNode();
> op.get(OP).set(MAP_REDUCE);
> op.get(ADDRESS_TEMPLATE).set(address);
> op.get(FILTER).set(filter);
> // To return datasources where (driver-name == h2 || enabled == true) use
> // op.get(FILTER_CONJUNCT).set(false);
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (WFLY-4123) Provide a 'map-reduce' operation to execute domain wide queries on the server side
by Heiko Braun (JIRA)
[ https://issues.jboss.org/browse/WFLY-4123?page=com.atlassian.jira.plugin.... ]
Heiko Braun updated WFLY-4123:
------------------------------
Summary: Provide a 'map-reduce' operation to execute domain wide queries on the server side (was: Provide a 'map_reduce' operation to execute domain wide queries on the server side)
> Provide a 'map-reduce' operation to execute domain wide queries on the server side
> ----------------------------------------------------------------------------------
>
> Key: WFLY-4123
> URL: https://issues.jboss.org/browse/WFLY-4123
> Project: WildFly
> Issue Type: Feature Request
> Reporter: Heiko Braun
> Assignee: Heiko Braun
> Fix For: 9.0.0.Beta1
>
>
> See https://github.com/hpehl/map-reduce
> {code:java}
> ModelNode address = new ModelNode();
> address.add("profile", "*")
> .add("subsystem", "datasources")
> .add("data-source", "*");
> ModelNode filter = new ModelNode();
> filter.add("driver-name", "h2")
> .add("enabled", true);
> ModelNode op = new ModelNode();
> op.get(OP).set(MAP_REDUCE);
> op.get(ADDRESS_TEMPLATE).set(address);
> op.get(FILTER).set(filter);
> // To return datasources where (driver-name == h2 || enabled == true) use
> // op.get(FILTER_CONJUNCT).set(false);
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (WFCORE-284) Rewrite CLI FileArgumentTestCase
by Alexey Loubyansky (JIRA)
Alexey Loubyansky created WFCORE-284:
----------------------------------------
Summary: Rewrite CLI FileArgumentTestCase
Key: WFCORE-284
URL: https://issues.jboss.org/browse/WFCORE-284
Project: WildFly Core
Issue Type: Task
Components: CLI
Reporter: Alexey Loubyansky
Assignee: Alexey Loubyansky
The test has been failing sporadically for awhile. One of the problems is to figure out the conditions under which the test fails. They haven't been determined so far. Perhaps, attempts to simplify and clean up the logic in the test will help.
The test is org.jboss.as.test.integration.management.cli.FileArgumentTestCase
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (DROOLS-146) Use .gitattributes to force linux line endings for all text files
by Geoffrey De Smet (JIRA)
[ https://issues.jboss.org/browse/DROOLS-146?page=com.atlassian.jira.plugin... ]
Geoffrey De Smet reassigned DROOLS-146:
---------------------------------------
Assignee: Michael Biarnes Kiefer (was: Geoffrey De Smet)
This has worked well for months on the optaplanner repository.
Michael,
1) All the other blessed repositories should now also get that .gitattributes file (copy it for the optaplanner repo). Possibly improve it first before copying.
2) Clean up all previous errors, as stated in the important above. Shells scripts like dos2unix etc can help here. All java files etc were dos2unixed 2 years ago, but we've seen many contributions since then ...
> Use .gitattributes to force linux line endings for all text files
> -----------------------------------------------------------------
>
> Key: DROOLS-146
> URL: https://issues.jboss.org/browse/DROOLS-146
> Project: Drools
> Issue Type: Task
> Reporter: Geoffrey De Smet
> Assignee: Michael Biarnes Kiefer
>
> With .gitattributes we can force all java files etc to have linux file endings.
> I am experimenting with this in the optaplanner repository:
> https://github.com/droolsjbpm/optaplanner/commit/40dca629262568d5e5abb379...
> If it works well, we'll want to compile a good overall .gitattributes file and commit it to all droolsjbpm repositories.
> During the refactor to .gitattributes, execute this script to detect and fix all previous errors:
> https://help.github.com/articles/dealing-with-line-endings#re-normalizing...
> *Important:*
> In OptaPlanner we just committed the file without "fixing all previous errors". It turned out we had 2.
> The person who adds the .gitattributes file doesn't get a problem, but other people who clone a new repository
> get immediate modifications to incorrect files. This is a PITA.
> So *after the commit .gitattributes files, all previous errors need to be fixed for and verified by doing a new clone and a git status on that new clone.*
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (JBWEB-305) No file name information in detail error when compiling the java file
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBWEB-305?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on JBWEB-305:
-----------------------------------------------
Radim Hatlapatka <rhatlapa(a)redhat.com> changed the Status of [bug 1155635|https://bugzilla.redhat.com/show_bug.cgi?id=1155635] from ON_QA to VERIFIED
> No file name information in detail error when compiling the java file
> ----------------------------------------------------------------------
>
> Key: JBWEB-305
> URL: https://issues.jboss.org/browse/JBWEB-305
> Project: JBoss Web
> Issue Type: Bug
> Affects Versions: JBossWeb-7.4.0.GA, JBossWeb-7.5.0.GA
> Reporter: Aaron Ogburn
> Assignee: Remy Maucherat
> Priority: Minor
>
> JBossWeb does not have a fix to https://issues.apache.org/bugzilla/show_bug.cgi?id=54466. Helpful file name information can be left off of compilation errors, for example:
> {code}
> ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/helloworld2].[jsp]] (http-/127.0.0.1:8080-1) JBWEB000236: Servlet.service() for servlet jsp threw exception: org.apache.jasper.JasperException: JBWEB004062: Unable to compile class for JSP:
> JBWEB004061: An error occurred at line: 32 in the generated java file
> The code of method _jspService(HttpServletRequest, HttpServletResponse) is exceeding the 65535 bytes limit
> JBWEB004211: Stacktrace:
> at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:85) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4]
> at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:69) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4]
> at org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:451) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (DROOLS-656) The blessed repo's should not accept a git force push
by Geoffrey De Smet (JIRA)
[ https://issues.jboss.org/browse/DROOLS-656?page=com.atlassian.jira.plugin... ]
Geoffrey De Smet updated DROOLS-656:
------------------------------------
Description:
If someone ever git forces pushes to a blessed repo all hell will break loose.
We can prevent git forces pushes, as explained here:
http://stackoverflow.com/questions/1754491/is-there-a-way-to-configure-gi...
Force pushing on blessed repo's is very bad, but force pushing on forks is very common.
Requirements:
- Enable this on 1 new dummy blessed repository
- Prove you cannot force push to
- Prove you can fork it and force push to your fork.
- Delete the dummy blessed repository
- If that works well, enable it on the real blessed repositories
was:
If someone ever git forces pushes to a blessed repo all hell will break loose.
We can prevent git forces pushes, as explained here:
http://stackoverflow.com/questions/1754491/is-there-a-way-to-configure-gi...
Requirements:
- Enable this on 1 new dummy blessed repository
- Prove you cannot force push to
- Prove you can fork it and force push to your fork.
- Delete the dummy blessed repository
- If that works well, enable it on the real blessed repositories
> The blessed repo's should not accept a git force push
> -----------------------------------------------------
>
> Key: DROOLS-656
> URL: https://issues.jboss.org/browse/DROOLS-656
> Project: Drools
> Issue Type: Task
> Reporter: Geoffrey De Smet
> Assignee: Michael Biarnes Kiefer
> Priority: Critical
>
> If someone ever git forces pushes to a blessed repo all hell will break loose.
> We can prevent git forces pushes, as explained here:
> http://stackoverflow.com/questions/1754491/is-there-a-way-to-configure-gi...
> Force pushing on blessed repo's is very bad, but force pushing on forks is very common.
> Requirements:
> - Enable this on 1 new dummy blessed repository
> - Prove you cannot force push to
> - Prove you can fork it and force push to your fork.
> - Delete the dummy blessed repository
> - If that works well, enable it on the real blessed repositories
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month