[jira] [Commented] (SOLR-6614) SolrCloud graph viz truncates port designation

["Stefan Matheis (steffkes) (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-6614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212315#comment-14212315 ] 

Stefan Matheis (steffkes) commented on SOLR-6614:
-------------------------------------------------

as i've explained to [~ralph.tice] yesterday on the conference party, i don't believe that it's an explicit problem with the port number .. to me it looks more like the svg-drawing area just ends - and the content doesn't completely fit.

{{-100}} might be a bit to much, since that really moves the area out of the content-area (if looking at html-elements), Ralph for me, reducing the first param to zero works fine as well, can you confirm that?

{code}-      .attr( 'transform', 'translate(100, 0)' );
+      .attr( 'transform', 'translate(0, 0)' );{code}

the underlying problem is .. a tree in d3.js uses one top-node, which doesn't work in our case .. so i'm faking here a bit by leaving that blank. looking at the rendered source-code you can see classes like {{lvl-1}} which indicate the invisible tree-nodes. they are taking up a bit space, which is why reducing the position from 100 to 0 still leaves some white space on the left side. but avoids that elements are actually overlapping - which might lead to problems like "i can see button xy, but i can't click on it" which can happens in some browsers in such a case.

> SolrCloud graph viz truncates port designation
> ----------------------------------------------
>
>                 Key: SOLR-6614
>                 URL: https://issues.apache.org/jira/browse/SOLR-6614
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud, web gui
>    Affects Versions: 4.10.1
>            Reporter: Ralph Tice
>            Priority: Minor
>         Attachments: SOLR-6614.patch
>
>
> I believe this is a regression but I didn't see anything jump out at me from the history on cloud.js.  The port designation for shards is truncated.  I am pretty sure the port designation only appears if you have multiple JVMs on the same hostname in your SolrCloud.
> Here is a visual depiction of the problem: http://monosnap.com/image/WzETqptfhcuDGKXjpJPR854lIzriyI
> I have a very minor patch which addresses this as well as an issue with the legend being overlaid on top of shard designations.  It's pretty simple, but I generally only have the use case of dozens or hundreds of shards so I'm not sure how this looks in other situations.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org