Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom OClusterSelectionStrategy does not appear in studio manager dropdown #8086

Closed
brian-guggino opened this issue Feb 8, 2018 · 2 comments
Assignees
Labels
Milestone

Comments

@brian-guggino
Copy link

brian-guggino commented Feb 8, 2018

OrientDB Version: 2.1 and 2.2

Java Version: 1.8

OS: centos7

Expected behavior

The name of the OClusterSelectionStrategy implementation should appear in the orientdb's schema manager (UI)

Actual behavior

The dropdown in the UI contains a blank string. When deselecting it, and re-opening the drop down, the "name" does not appear. It would be nice if the system populated the dropdown with all the "name"s of the implementation of OClusterSelectionStrategy loaded. And error appears after some time - in the lower error "bar".

See attached screen-shots:
screen_shot_2018-02-07_at_9 53 08_am
screen_shot_2018-02-08_at_9 14 42_am

Steps to reproduce

  1. Follow direction for 2.2/Cluster-Selection.html, the "random" implementation will suffice.
  2. deploy the jar into orientdb's lib folder, restart the orientdb service/server.
  3. connect to the database ->
    CONNECT remote:localhost/
  4. activate the custom implementation ->
    ALTER CLASS messages CLUSTERSELECTION random
    where "messages" is the class being altered.
  5. verify the cluster selection is activated with "info class
  6. open the orient db UI, http://:/studio/index.html#/database//schema
  7. Find the altered class in the manager...
@brian-guggino brian-guggino changed the title Custom Custom OClusterSelectionStrategy does not appear in studio manager dropdown Feb 8, 2018
@luigidellaquila
Copy link
Member

Hi @brian-guggino

Right now the drop-down menu is hard-wired in the frontend, but I think we can extend this behavior and make it more consistent.

I'm checking it now

Thanks

Luigi

@luigidellaquila luigidellaquila self-assigned this Mar 26, 2018
wolf4ood added a commit to orientechnologies/orientdb-studio that referenced this issue Mar 26, 2018
wolf4ood added a commit to orientechnologies/orientdb-studio that referenced this issue Mar 26, 2018
@wolf4ood wolf4ood added the bug label Mar 26, 2018
@wolf4ood wolf4ood added this to the 2.2.x (next hotfix) milestone Mar 26, 2018
@wolf4ood
Copy link
Member

Hi @brian-guggino

i've just pushed a fix in 2.2.x and develop. It will be available in the next release 2.2.34

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

3 participants