IntelliJ IDEA 2019.3 EAP5: MongoDB Support, and More

A new IntelliJ IDEA 2019.3 EAP build is here and it comes with highly anticipated improvements. Continuing the trend of eliminating pain-points and resolving issues that affected lots of users, this new EAP build addresses the issues that have received more than 400 votes in total.

Download and try the freshly released new EAP build from our website, or update to it via the Toolbox App.

As usual, the EAP builds for IntelliJ IDEA Ultimate are free to use but expire within 30 days of the build date.

MongoDB support

At last, it’s here! The upcoming IntelliJ IDEA 2019.3 will provide initial support for MongoDB.

Already in this EAP build, you can view collections and fields in the database explorer.

database_view

You can also open any collection or observe the query result. It’s also possible to sort by columns or filter the values.

data_view

What’s more, you can now run queries. Select one and run it by pressing Ctrl/Cmd+Enter or by clicking the Play button on the toolbar.

query

Please keep in mind that this is still a work in progress. There are some known limitations: no coding assistance for now, and no integration with MongoDB shell so only a limited number of MongoDB functions that can be executed. Rest assured though that we will extend this functionality in our future releases.

Improved Command Line Inspector

With IntelliJ IDEA you can launch code inspections from the command line. V2019.3 will enhance this feature so that the IDE can detect the JDK automatically. You will be able to run it on a CI server with no system-wide IntelliJ IDEA configuration.

We’ve also added a new option, “-changes”, to inspect only uncommitted changes and to report only newly introduced problems.

Another recent addition is support for reporting the inspection results as JSON, in addition to the previously available plain text and XML formats.

Other improvements

We have also updated JBR 11 (default) to v11.0.4+10-b517.1, to integrate the following changes:

  • Fixed the issue with project opening on macOS 10.15 Catalina: JBR-1721.
  • Repaired the symbols in the Evaluate Expression dialog: JBR-1879.

For the full list of changes, please refer to the IDE release notes and the JBR11 release notes.

Your feedback is highly appreciated here in the comments or directly in our issue tracker.

For the latest news around IntelliJ IDEA, follow us on Twitter.

Happy developing!

About Zlata Kalyuzhnaya

IntelliJ IDEA Marketing Manager at JetBrains. twitter: @ZlataKalyuzhnay ‏
This entry was posted in EAP Releases and tagged , . Bookmark the permalink.

17 Responses to IntelliJ IDEA 2019.3 EAP5: MongoDB Support, and More

  1. Joachim Beckers says:

    Those are the release notes for EAP 4 you’re linking to.

  2. ADEV says:

    YES!!!!! Thanks for MongoDB support, i use it in one of my projects!! this is perfect, thanks!

  3. Andrey says:

    Hope old regressions will be fixed too :)
    Not working popups are very annoying https://youtrack.jetbrains.com/issue/IDEA-201369

    • Dmitry Jemerov says:

      We’re sorry for the inconvenience you’re experiencing, but at this time it doesn’t seem like there are many (if any at all) other users experiencing the same problem. Please understand that we have to prioritize issues affecting a large number of users (and the JetBrains Runtime team has many such high-priority issues at this time).

  4. zgq says:

    When Intellij IDEA supports redis?

  5. Sanjay says:

    This build throws below exception most of the time (while opening some files) :
    com.intellij.diagnostic.PluginException: com.intellij.psi.codeStyle.CodeStyleManager requested as a service, but it is a component – convert it to a service or change call to project.getComponent()
    at com.intellij.ide.plugins.PluginManagerCore.createPluginException(PluginManagerCore.java:382)
    at com.intellij.diagnostic.PluginProblemReporterImpl.createPluginExceptionByClass(PluginProblemReporterImpl.java:12)
    at com.intellij.diagnostic.PluginException.createByClass(PluginException.java:58)
    at com.intellij.diagnostic.PluginException.logPluginError(PluginException.java:75)
    at com.intellij.serviceContainer.PlatformComponentManagerImpl.getService(PlatformComponentManagerImpl.kt:302)
    at com.intellij.openapi.components.ServiceManager.getService(ServiceManager.java:22)
    at com.intellij.psi.codeStyle.CodeStyleManager.getInstance(CodeStyleManager.java:40)
    at com.intellij.refactoring.extractMethod.ExtractMethodProcessor.(ExtractMethodProcessor.java:162)
    at com.intellij.refactoring.extractMethod.ExtractMethodHandler.getProcessor(ExtractMethodHandler.java:245)
    at com.intellij.refactoring.extractMethod.ExtractMethodHandler.getProcessor(ExtractMethodHandler.java:279)
    at com.jetbrains.clones.languagescope.java.ExtractDuplicatedJavaMethodFix$Companion.isExtractable(ExtractDuplicatedJavaMethodFix.kt:36)
    at com.jetbrains.clones.languagescope.java.ExtractDuplicatedJavaMethodFix$Companion.createFix(ExtractDuplicatedJavaMethodFix.kt:28)
    at com.jetbrains.clones.languagescope.java.JavaDuplicateScope.createQuickFixes(JavaDuplicateScope.kt:163)
    at com.jetbrains.clones.DuplicateInspection.a(DuplicateInspection.kt:92)
    at com.jetbrains.clones.DuplicateInspection.checkFile(DuplicateInspection.kt:78)
    at com.intellij.codeInspection.LocalInspectionTool$1.visitFile(LocalInspectionTool.java:143)
    at com.intellij.psi.impl.source.PsiJavaFileBaseImpl.accept(PsiJavaFileBaseImpl.java:520)
    at com.intellij.codeInspection.InspectionEngine.acceptElements(InspectionEngine.java:77)
    at com.intellij.codeInsight.daemon.impl.LocalInspectionsPass.lambda$null$6(LocalInspectionsPass.java:332)
    at com.intellij.util.AstLoadingFilter.lambda$toComputable$2(AstLoadingFilter.java:167)
    at com.intellij.util.AstLoadingFilter.disallowTreeLoading(AstLoadingFilter.java:125)
    at com.intellij.util.AstLoadingFilter.disallowTreeLoading(AstLoadingFilter.java:114)
    at com.intellij.util.AstLoadingFilter.disallowTreeLoading(AstLoadingFilter.java:109)
    at com.intellij.codeInsight.daemon.impl.LocalInspectionsPass.lambda$visitRestElementsAndCleanup$7(LocalInspectionsPass.java:331)
    at com.intellij.concurrency.ApplierCompleter.execAndForkSubTasks(ApplierCompleter.java:148)
    at com.intellij.openapi.application.impl.ApplicationImpl.tryRunReadAction(ApplicationImpl.java:997)
    at com.intellij.concurrency.ApplierCompleter.lambda$wrapInReadActionAndIndicator$1(ApplierCompleter.java:105)
    at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:585)
    at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:531)
    at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:59)
    at com.intellij.concurrency.ApplierCompleter.wrapInReadActionAndIndicator(ApplierCompleter.java:116)
    at com.intellij.concurrency.ApplierCompleter.lambda$compute$0(ApplierCompleter.java:96)
    at com.intellij.openapi.application.impl.ReadMostlyRWLock.executeByImpatientReader(ReadMostlyRWLock.java:167)
    at com.intellij.openapi.application.impl.ApplicationImpl.executeByImpatientReader(ApplicationImpl.java:157)
    at com.intellij.concurrency.ApplierCompleter.compute(ApplierCompleter.java:96)
    at java.base/java.util.concurrent.CountedCompleter.exec(CountedCompleter.java:746)
    at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290)
    at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1020)
    at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1656)
    at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1594)
    at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:177)

    • Dmitry Jemerov says:

      This problem is caused by either a corrupted installation or a third-party plugin. It does not occur in a clean installation.

      • Sanjay says:

        Thank you very much for the information.
        I couldn’t have though that this was due to corrupt installation.

        Actually I was facing other issues also – like font contrast was too bright and some other frequent exceptions also.

        I did clean installation and everything is fine now. :)

  6. Serg says:

    Is there any plans to introduce support of Elasticsearch?

  7. opticyclic says:

    Just waiting (8 years so far!) for the threshold to drop to 200 votes 😀
    https://youtrack.jetbrains.com/issue/IDEA-68854

Leave a Reply

Your email address will not be published. Required fields are marked *