aklein-1s opened a new issue, #34673:
URL: https://github.com/apache/superset/issues/34673

   ### Bug description
   
   I'm creating a very simple handlebar chart to test this component and I 
noticed that I have big delays to render it. It's rather fluid with 1 column, 
but when I add 3 column, the browser freeze during about 10 seconds, and after 
that, it is very slow.
   I think I have understood the problem, when I have one column, I choose the 
"aggregate" query mode, and I have only 18 rows to render, but if I choose "raw 
records", all records are displayed, so it freeze too.
   
   My example : 
   `<table class="events">
     {{#each data}}
       <tr>
         <td class="icon"><!--<img 
src="/static/assets/images/superset-logo-horiz.png" />--></td>
         <td class="content">
           <dl>
             <dt><strong>{{this.type_evt}}</strong></dt>
             <dd></dd>
           </dl>
         </td>
       </tr>
     {{/each}}
   </table>`
   
   So, I need server pagination for handlebars to avoid this, but I found [this 
thread](https://github.com/apache/superset/issues/29657) which indicates that 
the server pagination doesn't work on handlebar.
   Is there a workaround about that ?
   
   I don't know how to use handlebars without server pagination, but I guess it 
isn't possible with good performance, or it requires a small dataset. 
   Is it planned to add server pagination for the handlebars ?
   
   Thank you.
   
   ### Screenshots/recordings
   
   _No response_
   
   ### Superset version
   
   5.0.0
   
   ### Python version
   
   3.9
   
   ### Node version
   
   16
   
   ### Browser
   
   Firefox
   
   ### Additional context
   
   _No response_
   
   ### Checklist
   
   - [x] I have searched Superset docs and Slack and didn't find a solution to 
my problem.
   - [x] I have searched the GitHub issue tracker and didn't find a similar bug 
report.
   - [x] I have checked Superset's logs for errors and if I found a relevant 
Python stacktrace, I included it here as text in the "additional context" 
section.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to