I deployed my datahub using helm chart, And I was extending metadata using this documentation, https://datahubproject.io/docs/metadata-models-custom. But I got this error, after I ran this command,

curl -s <http://localhost:8080/config> | jq .

curl -s http://localhost:8080/config

{
  "models": {
    "mycompany-dq-model": {
      "0.0.1": {
        "loadResult": "FAILURE",
        "registryLocation": "/etc/datahub/plugins/models/mycompany-dq-model/0.0.1",
        "failureReason": "java.lang.IllegalArgumentException: Aspect customDataQualityRules does not exist\n\tat com.linkedin.metadata.models.registry.PatchEntityRegistry.buildAspectSpec(PatchEntityRegistry.java:231)\n\tat com.linkedin.metadata.models.registry.PatchEntityRegistry.lambda$new$5(PatchEntityRegistry.java:151)\n\tat java.base/java.util.ArrayList.forEach(ArrayList.java:1541)\n\tat com.linkedin.metadata.models.registry.PatchEntityRegistry.<init>(PatchEntityRegistry.java:149)\n\tat com.linkedin.metadata.models.registry.PatchEntityRegistry.<init>(PatchEntityRegistry.java:115)\n\tat com.linkedin.metadata.models.registry.PatchEntityRegistry.<init>(PatchEntityRegistry.java:76)\n\tat com.linkedin.metadata.models.registry.PatchEntityRegistry.<init>(PatchEntityRegistry.java:82)\n\tat com.linkedin.metadata.models.registry.PluginEntityRegistryLoader.loadOneRegistry(PluginEntityRegistryLoader.java:146)\n\tat com.linkedin.metadata.models.registry.PluginEntityRegistryLoader.lambda$start$5(PluginEntityRegistryLoader.java:100)\n\tat java.base/java.util.ArrayList.forEach(ArrayList.java:1541)\n\tat com.linkedin.metadata.models.registry.PluginEntityRegistryLoader.lambda$start$6(PluginEntityRegistryLoader.java:100)\n\tat java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)\n\tat java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)\n\tat java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)\n\tat java.base/java.lang.Thread.run(Thread.java:829)\n",
        "failureCount": 5
      }
    }
  },
  "patchCapable": true,
  "versions": {
    "linkedin/datahub": {
      "version": "v0.10.1",
      "commit": "864ac2da9f7ebc3ca035b610b295e9d8689db445"
    }
  },
  "managedIngestion": {
    "defaultCliVersion": "0.10.0",
    "enabled": true
  },
  "statefulIngestionCapable": true,
  "supportsImpactAnalysis": true,
  "timeZone": "GMT",
  "telemetry": {
    "enabledCli": true,
    "enabledIngestion": false
  },
  "datasetUrnNameCasing": false,
  "retention": "true",
  "datahub": {
    "serverType": "prod"
  },
  "noCode": "true"
}

You may not have built the full project- but based on the stack trace it might be that you’ve added an aspect that isn’t fully supported

I am using Kubernetes to deploy my project and in the pod of gms in Kubernetes under /etc/datahub/plugins, I can see the models folder but it is not reflecting in when I am running

<http://localhost:8080/config>

Hi, is this resolved as of your message in the other thread?

No, it is not resolved. I could build successfully but the end result is that I should be able to get models successfully which does not happen yet.

Hi @billions-baker-82097, What was the solution?, as I am also facing the same issue

Hi @little-hospital-40270 you have to make the index explicitly, lets say you have named your custom entity as customdashboard then make customdashboardindex_v2 using below cmd: curl -X PUT "127.0.0.1:9200/customdashboardindex_v2" -H 'Content-Type: application/json'

@billions-baker-82097, when I run the curl command I get an empty model when I set the ENTITY_REGISTRY_PLUGIN_PATH. My yaml file looks like this: extraEnvs: - name: ENTITY_REGISTRY_PLUGIN_PATH value: /etc/datahub/plugins/models/mycompany-dq-model/0.0.1/entity-registry.yaml extraVolumes: - name: custom-model configMap: name: custom-model ## should match configmap name above extraVolumeMounts: - name: custom-model mountPath: /etc/datahub/plugins/models/mycompany-dq-model/0.0.1 I see you got the custom-meta-model working. Can you tell how you got it working? Thanks