Jump to content
We've recently updated our Privacy Statement, available here ×

mdahlman

Members
  • Posts

    1,332
  • Joined

  • Last visited

 Content Type 

Profiles

Forum

Events

Featured Visualizations

Knowledge Base

Documentation (PDF Downloads)

Blog

Documentation (Test Area)

Documentation

Dr. Jaspersoft Webinar Series

Downloads

Posts posted by mdahlman

  1. The quickest solution is to do everything in a single SQL query:

    SELECT items.name AS item_name, trends_uint.clock AS  trends_clock, trends_uint.`value_avg` AS mem_total_value_avg 
    FROM items, hosts, trends_uint 
    WHERE  items.itemid = trends_uint.itemid AND items.hostid=hosts.hostid AND  hosts.host='vsrvlab02' AND items.key_='vm.memory.size[total]'
    UNION ALL
    SELECT items.name AS item_name, trends_uint.clock AS  trends_clock, trends_uint.`value_avg` AS mem_total_value_avg 
    FROM items, hosts, trends_uint 
    WHERE  items.itemid = trends_uint.itemid AND items.hostid=hosts.hostid AND  hosts.host='vsrvlab02' AND items.key_='vm.memory.size[available]'

    There are other (better?) ways to write the SQL. But this one is certain to work since it just UNIONs your 2 existing queries together.

  2. First, you should enable the menu Create -> Domain for non-admin users. Edit the file .../jasperserver-pro/WEB-INF/actionModel-navigation.xml. Find this near the end:

                            [/code]

    Second, you need to enable the relevant flow. Edit the file .../jasperserver-pro/WEB-INF/applicationContext-security.xml. Find line 558:

    createSLDatasourceFlow=ROLE_USERdomainDesignerFlow=ROLE_USER[/code]

    That should give you the ability for ROLE_USER to create domains.

    From there you can improve on the solution. Maybe you only want a few users to have this option. You could instead create ROLE_DOMAIN_DESIGNER and use this so that not everyone with ROLE_USER gets this permission. Also, my first change enables Create -> Data source as well. You may not want that. It should be pretty easy to tweak my suggestion to enable only Create -> Domain.

  3. Nope, iReport is not intended as an end user tool. It might work for some superusers, but in general it's much too complex for them.

    Ad Hoc reporting in JasperReports Server is intended for end user reporting and analysis.

  4. Hi,

    This isn't a real question... but instead it's a welcome message with a few best practices about asking questions related to Jaspersoft Business Intelligence for Amazon Web Services (Jaspersoft BI for AWS).

    Some questions may really be specific to the Jaspersoft BI for AWS offering. Those should definitely get tagged with "AWS". (There are folks at Jaspersoft specifically monitoring questions that get tagged like this.) A large percentage of these users will be working with Amazon Relational Database Service or Amazon Redshift. Be sure to tag the questions appropriately with RDS and MySQL or SQL Server or whatever the database technology is.

    Most questions about Jaspersoft BI for AWS will be more general questions about JasperReports Server or iReport. So you should post those as standard JRS or iReport questions linked to those projects. BUT... please also tag the question with the "AWS" tag.

    Thanks!

    By the way, for anyone who comes across this post and has no idea what Jaspersoft BI for AWS is. You can read about it on the page Jaspersoft for AWS.

  5. Right-click the report unit and choose "New".

    From there it will be obvious. (But I understand why you wouldn't think of it at first.) It a different way to think of things, but I think the new flow is better once you're used to it.

    EDIT: Based on baumgaro's comment, it's clearly not as obvious as I claimed. But you need to choose "Link" when your goal is to link to an existing input control (or link to another type of object).

  6. Impala is not tested with the Jaspersoft Hive Connector. Impala "works like Hive". So in principle it should just work. Your test was reasonable. But it's easy to imagine the possibility of version conflicts with these technologies. Jaspersoft will certainly test with Impala, but an exact timeline is not established yet.
  7. I had the same behavior. In my case it was because I had "Page 1 of N" in the page footer. Because of this, JRS behaves like this:

    1. Renders first page as quickly as possible (including chart). Footer displays "Page 1 of"
    2. It calculates the full report.
    3. It updates the first page (includeing chart). Footer displays "Page 1 of 2".

    In the case where step 2 takes 60 seconds... this behavior is great. You see page 1 very quickly, and then you see the updated version after the rest of the report is calculated.

    But in the case where step 2 takes a few milliseconds... the report just appears to render twice. It's annoying. My immediate solution was to remove the Total Page calculation from the first page. That might work for you too.

    You should log an enhancement request. (I already did, but it definitely adds to the urgency if community members log requests as well.)

  8. Can you post a sample report with the problem? In general UTF-8 should be great for working with accented characters. And in practice it's working well for me (and others) with accents, Japanese, etc. So there must be something unusual going on.
×
×
  • Create New...